Add a photo, press “Compress”, and it comes back as a JPG of 500 KB or less. Pick 100 to 1,000 KB with one tap or type your own size; the quality is kept as high as that size allows. Photos are compressed inside your browser and are not sent anywhere.
The result is always a JPG. Transparent parts become white. A re-saved photo does not carry the camera details of the original, such as where it was taken.
How the compression worksHow this works
Your photos stay on your device
The photos you add are opened and saved again by this page inside your browser. This tool has no upload step and no server route; each smaller JPG is made in your device's memory and saved straight to your downloads.
You can check this yourself. Open the page, switch off Wi‑Fi or mobile data, and compress a photo: it still works. The line under the result also counts the network requests made while compressing.
How the size is reached
Each photo is first saved as a JPG at quality 92%. If that is already under the target, it is done. If not, it is tried at 40%. When 40% fits, the page halves the gap between the two six times, keeping the best try that fitted, so the quality ends within about one point of the highest that fits.
Only when even 40% is over the target is the picture made smaller, and then the quality search runs again. Each step cuts at least 15% off the sides, more when the try was far off, and stops at 100 pixels on the longer side. If a photo is still over the target at that point, its row says so in red instead of pretending.
What 500 KB means here
One KB is counted as 1,000 bytes, so 500 KB means at most 500,000 bytes. Some sites count 1,024 bytes to a KB; a file that passes the smaller count passes theirs too. Sizes on this page are rounded up, never down.
A JPG that is already at or under the target, and within the longest-side limit if you set one, is handed back exactly as it is, with its own name. PNG, WebP and HEIC photos are always turned into JPG, because that is what forms ask for, and transparent parts become white.
Phone photos, names and limits
Phone photos keep their way up: the browser turns each photo by the note the camera stored before it is saved again. A photo over 16 million pixels is reduced to that first, because some phones refuse larger canvases. HEIC, the iPhone format, opens in every browser; where the browser cannot read it, the page reads it with libheif, on this device.
The re-saved JPG holds pixels only, so camera details from the original, such as where it was taken, are not copied into it. Files are named like photo_500KB.jpg, and several photos can be saved together as one ZIP. The page cannot make PNG or WebP files or crop to an exact pixel size; the optional longest-side box only sets a maximum.
No. This page opens the photo and saves the smaller JPG inside your browser, and there is no server step for this tool. You can test it: open the page, switch off your internet connection, then compress. It still works. The line under the result also counts the network requests made while compressing.
Will the file really pass a 500 KB limit?
A photo that reached the target is at most 500,000 bytes, which is under 500 KB whether a site counts 1,000 or 1,024 bytes to a KB. The size shown is the size of the saved file itself, rounded up. A photo that could not reach the target even at 100 pixels on its longer side is marked in red, not passed off as done.
What happens to PNG and iPhone HEIC photos?
Both are saved as JPG, because that is what most forms ask for; transparent parts of a PNG become white. HEIC works in any browser: where the browser cannot open it itself, as in Chrome and Edge on Windows, the page loads a HEIC reader the first time one is added. Either way the photo is not uploaded.