About ImgCruncher
Free, private, browser-based image tools. No uploads, no sign-ups, no watermarks.
ImgCruncher is a free suite of 23 image tools that run entirely in your browser: compression, resizing, conversion, cropping, watermarking, metadata inspection and more. Every tool works the same way. Your image is processed on your own device, and it never touches a server.
ImgCruncher started from a simple frustration. Shrinking a photo or converting a format usually means uploading your file to a stranger's server, waiting in a queue, and getting a watermarked or size-limited result unless you pay. Most of these tasks never needed a server in the first place. Browsers have been able to decode, resize and re-encode images natively for years. So we built ImgCruncher to do that work where it belongs, on your device, and to be straight with people about what the tools can and cannot do.
The first version went live in spring 2026 with a handful of tools. The suite has grown steadily since, and the guides grew alongside it, because a tool without an explanation of when to use it is only half useful.
ImgCruncher at a glance
The facts, including the ones most sites leave out.
| What it is | A suite of 23 free image tools plus a library of tested guides |
|---|---|
| Launched | Spring 2026, actively developed since |
| Where processing happens | In your browser, on your own device. No image is uploaded |
| Accounts | None. There is nothing to sign up for |
| Cost | Free, with no paid tier, no trial and no feature held back |
| File size limits | No fixed cap. The practical limit is your own device memory |
| Watermarks | Never added to your output |
| How it is funded | Advertising only. We do not sell data, and we have none of your images to sell |
| Published guides | 59, each one tested rather than summarised |
| Who runs it | An independent team that builds, tests and maintains everything in-house |
Our principles
Three rules every tool on this site follows, no exceptions.
Private by design
Every tool runs in your browser. Your images never touch a server, so there is nothing to store, log or leak.
Honest about limits
Where a tool has a real weakness, its page says so. We would rather undersell than surprise you with a bad result.
Free, with no gates
No accounts, no daily caps, no watermarks, no paid tier. The site is funded by unobtrusive ads and nothing else.
What you get
The short version of what lives here.
- 23 image tools: compress, resize, convert, crop, watermark, inspect and more
- Chain steps into one pass: resize, convert and compress in a single download
- Exact size targets, like compress this to 100 KB, found automatically
- Batches with a single ZIP download, processed one by one on your device
- Installable like an app, and once a page is open the processing keeps working even if your connection drops
- A library of guides where every claim is tested for real, with actual measured numbers
How it works under the hood
Every tool here runs in your browser using standard web platform features: the FileReader API to read the file you chose, the HTML5 Canvas API to decode, transform and re-encode it, and Blob URLs to hand the result back to you as a download. A few tools load a specialist library for a format the browser cannot handle natively, such as HEIC decoding or PDF rendering, and those libraries also run inside your browser rather than on a server.
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 you have to take on trust. It is structural. If the processing happens in your browser, there is nothing for the site to store, log or leak.
You do not have to believe us. Open your browser's network tab while you use a tool and watch: your image never goes out. We also built a page that runs that check for you and reports what it finds, on how image privacy works here.
The practical trade-off is honest to state. Because the work happens on your device, a very large batch is limited by your own memory and processor rather than by our hardware, and a slow phone will take longer than a fast laptop. We think that is the right trade for never handing your files to anyone.
How we build and test
Tools are written and tested against real files, not sample data. Before a tool page goes live we run the tool ourselves on genuine images and record what actually happened: input size, output size, the settings used and the result. The numbers you see on a tool page or in a guide are measurements, not estimates, and where a number would change with different inputs we say so.
The same standard applies to the writing. We do not publish a guide about a tool we have not run, and we do not describe a result we have not seen. When a test produces an unflattering result, that result gets published too, because a guide that only reports wins is not a guide. The full standard is written up in our editorial policy.
Every tool is checked on a phone as well as a desktop before it ships, because most people who need to shrink a photo are holding the photo on a phone.
How we decide what to build next
Three things drive the roadmap, in this order. First, gaps people actually hit: if several people ask for the same missing operation, it moves up. Second, work that removes friction from something already here, which is where the chained pipeline came from, since resizing then converting then compressing used to mean three separate visits. Third, formats and platform requirements as they change, which is why the guides carry current dimensions rather than numbers copied from an older article.
What we deliberately do not do is add tools for the sake of a longer list. A tool earns its place by doing one job properly and by being honest on its own page about where it falls short. Every release is logged with a date on the changelog.
How ImgCruncher is funded
Advertising, and nothing else. There is no paid plan, no upsell and no premium tier holding back a feature you actually need. We state this plainly because the funding model of a free tool is a fair question, and because the usual answer for free image sites is worth knowing: many of them monetise the files themselves, or the account you had to create, or the queue you had to wait in.
We cannot do any of that. Your images never reach us, so there is nothing on our side to mine, resell or train on. The only thing advertising asks of you is that the ads load, and we keep those unobtrusive rather than letting them take over the page. Cookies and third-party advertising vendors are documented in the cookie policy and the privacy policy.
Accessibility
We want the tools usable by everyone, including people who do not use a mouse or who rely on a screen reader. We aim to meet WCAG 2.1 Level AA, and we check the site against that standard rather than assuming.
- Text and interface colours are checked for contrast, with a 4.5:1 minimum for body text and 3:1 for large text and controls.
- Every tool is operable by keyboard alone, and the focus outline is visible rather than removed.
- Controls carry real labels, and results announce themselves to screen readers rather than changing silently.
- Tap targets on phones are sized for fingers, and the layout is checked down to a 320 pixel wide screen.
- Animation respects the reduced motion setting in your operating system.
- Charts and diagrams carry a caption, and the numbers behind them appear in the text so nothing is only available visually.
Accessibility is never finished. If you hit something on this site that you cannot use, please tell us, describe what happened and what you were using, and we will treat it as a bug rather than a suggestion.
Security and reporting problems
Because there are no accounts and no uploads, the usual reasons a site gets breached do not apply here: there is no user database to steal and no library of your files to expose. The connection is served over HTTPS with HSTS so what you load cannot be tampered with in transit. If you believe you have found a security issue, our security page explains how to report it and what to expect back. We would rather hear about a problem from you than read about it later.
What is working, and what isn't
The compression, resizing, conversion and cropping tools are solid, fast and in daily use. The honest picture includes 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, whatever the marketing on other sites suggests. Optical character recognition is accurate on clean, straight text and degrades on handwriting and heavy skew.
Where a tool has a real limit, its own page says so rather than overpromise. If you find a case where a page oversells what the tool does, that is a bug worth reporting, and we will fix the wording.
Who we are, and how to reach us
ImgCruncher is an independent product, focused entirely on free, private image tools rather than on running your files through someone else's servers. We build, test and maintain every tool in-house. We are deliberately a small operation, which is why the site does well at doing a narrow thing properly and does not pretend to be an all-purpose creative suite.
Every message sent through the contact page is read by the people who build the tools, not by an outsourced desk. We aim to reply to genuine questions and bug reports within a few working days, and good bug reports regularly turn into fixes within the same week. Feedback shapes what gets built next more than anything else does. If you want to see what changed recently, the changelog is dated and specific.
Found a bug, or missing a tool?
We read every message, and good bug reports often turn into fixes within days.