Image Compressor: I built it for the “your file is too large” moment

One surprisingly common online task is also one of the most annoying:

You have an image that looks fine, but the place you’re trying to upload it says the file is too large.

Maybe it’s a blog CMS, an ecommerce product page, a form, an email attachment, or a social graphic.

You don’t really want an “image optimization workflow.” You just want the file to be smaller so you can continue what you were doing.

That’s the problem I wanted ToolkitLoop’s Image Compressor to solve.

You can add JPG, PNG, or WebP images, compress a small batch, and download the results. Processing happens in the browser rather than uploading the images to ToolkitLoop.

The product decision I’m trying to stick to with ToolkitLoop is simple: one annoying task, as few steps as possible, no account wall.

I’d be interested to know: when you compress images, what’s usually the reason — page speed, an upload limit, email, or something else?