The No Title^® Tech Blog

Optimize Images 2.1.0 brings native WebP support, a generalized format-conversion system, on-demand image inspection with EXIF reporting, and a new in-memory API for working with image bytes directly. It is a focused, fully backwards-compatible step forward for the command-line tool and its public API.

This release represents a significant milestone for both Optimize Images and Optimize Images X, marking a coordinated step forward in modernization, dependency cleanup, and internal architecture improvements across the ecosystem.

I recently stumbled upon a situation where I needed to quickly convert a Base64 string coming from a web api and save it into a file in disk in order to inspect its contents. Sure, I could have spun up a small program in C# or Python. But honestly, that felt like an overkill for what was essentially a one-off task. In the past I had used an online Base64 converter for a similar task, so it crossed my mind, but sharing potentially sensitive data with unknown third-party services didn’t feel right. So, I searched for an alternative. Surely, there had to be an simpler, more direct solution.

This time, we are releasing both Optimize Images and Optimize Images X at the same time. The original CLI version now uses temporary files with in-memory buffers, which prevents unnecessary I/O, and also displays more detailed and more useful version information. Optimize Images X, the GUI version, is now compatible with Python3.7+ and has the ability to open or preview a selected image.

So, just 3 days after the first public beta, here we got the second beta for Optimize Images X. It includes an important hot fix for Windows and Linux, and two new usability features.

Just for fun, this month I set myself to start a new Python project. It’s the same as Optimize Images, but with a big X and a nice graphical user interface. It wants to help you reduce the file size of images, and hopefully make your websites load faster.