Why I built this
The story behind ImgCruncher, in plain terms.
I am Keyur Moradiya, a web developer. ImgCruncher is mine: I designed it, wrote the code, and keep it running. There is no company behind it and no team, just one person who got tired of the same problem and decided to fix it.
The problem I kept running into
Every time I needed to shrink a photo or convert a format, the first page of Google was a wall of tools that all wanted the same thing: upload your file to their server, wait in a queue, then watch them stamp a watermark on the result or cap you at three images a day unless you paid. For a quick job that should take two seconds, that is a lot of friction, and you are handing your image to a stranger to get it.
The part that bothered me most was the upload. Most of these tasks do not need a server at all. Your browser is perfectly capable of resizing, compressing and converting an image on its own. So I built the version I wanted to use.
How it works under the hood
Every tool here runs in your browser using the HTML5 Canvas API and the FileReader API. When you drop in an image, it loads into your browser's memory, gets processed on your own device, and the result is handed straight back to you. The file never travels to a server, because there is no server in the loop for the actual work.
That is not a privacy promise I am asking you to trust. It is structural. If the processing happens in your browser, there is nothing for me to store, log or leak, even if I wanted to. You can open your browser's network tab while you use a tool and watch: your image never goes out.
What is working, and what isn't
The compression, resizing, conversion and cropping tools are solid. They are fast, the output is clean, and I use them myself most weeks.
I will be honest about the weaker spots too. The background remover handles plain, high-contrast backgrounds well but struggles with busy ones and fine hair, because doing that properly needs a heavy AI model that cannot run comfortably in a browser yet. The upscaler sharpens and enlarges with good interpolation, but it cannot invent detail that was never captured. Where a tool has a real limit, I try to say so on its own page rather than overpromise.
What is coming
I add tools as I hit a need for them or enough people ask. Recent additions were an AVIF converter and bulk processing. Next on my list are a proper from-WEBP converter and smarter handling for large batches. The site is actively worked on, not parked.
Get in touch
If you find a bug, want a tool that is not here, or just have feedback, I genuinely want to hear it. Use the contact page or email support@imgcruncher.com. I read everything.
Keyur Moradiya