Image tools that never upload your files
Seven tools that run entirely inside your browser, using your own device's processor. Full resolution, no watermark, no account, no daily limit — because we are not paying to process anything. You are.
The things people most often arrive for
Each is already set up on its own page, so there is nothing to configure.
- Convert HEIC to JPG
iPhone photos that Windows refuses to open, or a form refuses to accept. Converted here on your own device, with the colours kept right.
- How to open a HEIC file
The file is not damaged. Here is what is actually happening, and the three ways out.
- Convert WebP to JPG
The file your browser saved when you right-clicked a picture on a website. Converted here, with an honest note about transparency.
- How to open a WEBP file
Not a virus, not damaged — an ordinary web image. Where it came from, and what to do with it.
Why "no upload" actually matters
Most free image tools send your file to a server, process it there, and send it back. That costs them money for every single image, which is why they cap your resolution, stamp a watermark on it, or ask you to subscribe once you have processed a handful of files.
This site does the processing on your own device instead. Your files are never transmitted, never stored, and there is nothing for us to look at. It also means there is no reason to limit you — the full-resolution download is free because it costs us nothing to give you.
The privacy here is a consequence of the design rather than a promise you have to take on trust. You can verify it yourself: open your browser's network tab, process an image, and watch that no request carrying your file is ever made. The site also ships a Content Security Policy telling your browser to refuse any connection to another address, so the promise is enforced rather than merely stated.
PNG files actually get smaller here
Every browser can write a PNG, and every browser writes a bad one: it does not choose a compression filter per row of pixels, and it writes four full colour channels even for a logo with twelve colours in it. Nearly every free image tool hands that job straight to the browser, which is why a "compressor" so often returns a PNG larger than the one you gave it.
This site does not use the browser's PNG writer. It picks the filter for every row, drops the channels an image does not use, and packs the palette down to one, two or four bits per pixel when it fits. Same file in, no pixel changed:
| File | Original | Browser's PNG writer | Here |
|---|---|---|---|
| Phone screenshot | 16.8 KB | 104.9 KB | 16.9 KB |
| Interface screenshot | 19.7 KB | 46.5 KB | 10.0 KB |
| Logo with transparency | 4.0 KB | 10.0 KB | 2.4 KB |
Lossless, and checked rather than assumed: each result is decoded again and compared with the original pixel by pixel, and the difference is zero.
You can see what compression did before you download it
A number like −78% does not answer the only question that matters — does it still look right? Press Compare on any result and your original sits exactly underneath the compressed version with a divider you can drag across it. View 1:1 shows real pixels rather than a copy shrunk to fit the screen, which is the only size where compression damage is visible at all.
Removing metadata does not cost you any quality
Almost every tool that strips EXIF does it the lazy way: decode the photo, draw it into a blank image, save the whole thing again. The GPS goes, and so does a little of the picture, every time. That is not necessary — the metadata sits in its own block and can simply be cut out, leaving the compressed picture data untouched. That is what happens here, and the file even comes out slightly smaller.
One number is deliberately written back: the orientation flag, in a 32-byte block containing no location, no camera, no date. Without it a phone photo lies on its side in every other program, which is the most common complaint about tools like this. Here you get the clean file and the upright photo.
It works with no connection
Visit once and the site installs itself on your device — all seven tools, the iPhone HEIC decoder, the PDF engine. After that it works on a plane, on the underground, or anywhere the signal has given up. A tool that sends your files to a server cannot do this, no matter how well it is built.
Your colours survive
iPhone photos are taken in Display P3, a wider range of colour than most software expects. Converters that ignore this hand back a picture that is visibly duller than the original. This one reads the colour space your file declares and translates it properly — verified against a reference colour engine, accurate to within a level or two out of 255.
What it can open
JPG, PNG, WebP, AVIF, GIF, BMP, and the HEIC and HEIF formats that iPhones save photos in. Orientation recorded by phone cameras is read and applied, so portrait photos stay upright rather than arriving on their side.
Everything here strips metadata by default
Because each tool re-saves your image from raw pixels, the hidden EXIF block — GPS coordinates, camera model, date taken — is never written into the output. That happens whether you asked for it or not, on every tool. The metadata viewer exists so you can see what was in there before it went, and it reads JPG, iPhone HEIC, PNG and WebP — including the coordinates inside a photo taken straight off an iPhone, without converting it first.
Paste a screenshot straight in
The most common reason anyone opens an image tool has nothing to do with files: take a screenshot, then make it small enough for the form that just rejected it. Press Ctrl+V on any tool page here and the screenshot goes straight in — no saving it to disk, hunting for it, and deleting it afterwards.
The actual limits, measured
Most sites in this category say “unlimited” and leave you to find the wall yourself. Here are the numbers we measured, on a deliberately slow two-core machine.
| What | Measured |
|---|---|
| Batch, held in memory | 120 photos at 12 megapixels each, no failures |
| Batch, saved straight to a folder | Bounded by your free disk space, not memory |
| Single image | Works to about 190 megapixels; browsers cannot make a canvas past roughly 268 megapixels |
| ZIP download | Starts to fail near 900 MB total — this is a browser limit, which is why folder saving exists |
A faster machine will beat these comfortably. An old phone will not. If a batch stalls, split it — or use the folder option, which never holds your results in memory in the first place.
What it cannot do
Being honest about the trade-off: since everything runs on your device, very large batches on an older phone will be slow, and a browser can run out of memory where a desktop program would not. If a batch stalls, split it into smaller groups.
Animated GIFs lose their animation — only the first frame is kept. Some browsers cannot create WebP or AVIF files; where that is the case, the option is disabled rather than silently producing a broken file. And there is no OCR: this site moves pixels around, it does not read the text inside them.
Guides
Plain answers to the problems that bring people here in the first place — written to be read once and not needed again.
- How to Compress an Image to an Exact File Size
Upload forms rarely explain their limits. Here is how the 200 KB and 2 MB caps actually work, and how to land under one.
- Why Your iPhone Photos Won't Open on Windows
The file is not corrupted and your phone is not broken. It is a format standoff that has lasted nine years.
- The GPS Coordinates Hidden in Your Photos
Most phone photos carry the exact spot they were taken, accurate to a few metres. Including the ones taken at home.
- Passport Photo Size Requirements: Pixels, Format and 240 KB
600×600 to 1200×1200 pixels, square, JPEG, 240 KB or less. What each rule means and how to meet all four at once.
Bahasa Indonesia
The same tools, written in Indonesian rather than translated into it, with pages for the file size limits that Indonesian registration systems actually impose: Alat gambar tanpa unggah.