How to Compress Images Without Losing Visible Quality

A phone camera photo today routinely lands somewhere between 3 and 8 MB, more for a night shot or a burst frame with a lot of fine detail. That’s no problem for storage, but plenty of upload forms, email providers, and application portals still cap attachments well below that — often 1 MB, sometimes less. Shrinking a photo enough to clear one of those limits without turning it into a blotchy, blocky mess isn’t about finding a secret setting. It comes down to understanding what’s actually taking up the space in a photo file, and picking the right tool for the specific problem in front of you: file size, pixel dimensions, or file format.

What actually takes up space in a photo

A photo’s file size comes down to two things: how many pixels it holds, and how much of the fine detail in those pixels the file actually keeps. A photo shot at a phone’s full resolution starts out large no matter what, simply because there’s more raw picture information to store before any compression happens. Compression works on the second half of that equation — formats like JPEG discard detail a viewer is unlikely to notice, such as subtle color gradients or fine texture, in exchange for a smaller file. Push that too far and the loss becomes visible: blocky patches near hard edges, smudged texture, or banding across a smooth sky or shadow. Compressing an image without visible quality loss means stopping well before that point, not skipping compression altogether.

Shrinking a photo, step by step

Compress Image handles the re-encoding locally, inside your browser tab, so the photos you drop in never get uploaded anywhere.

1. Choose or drop your JPG, PNG, or WebP photos. Up to 20 fit in one batch.
2. Pick a target size. Balanced, around 1 MB, suits most uploads; drop to Small or Tiny only if a portal enforces a strict cap.
3. Set a smaller maximum width or height too, if the form also cares about pixel dimensions and not just file size.
4. Click Compress images, then download each result and check its new size against what you actually needed.

Each photo can be up to 50 MB going in, and the whole batch processes in your browser’s own memory, so a stack of high-resolution originals takes a little longer on an older phone or laptop.

Choosing a target size that won’t show

Start with Balanced before reaching for a smaller setting — it’s built to hold onto enough detail for screens and social posts while still cutting the file down meaningfully. If a portal’s limit is unusually strict, Small or Tiny gets you further, at the cost of some sharpness that becomes noticeable if someone prints the photo or zooms in close. One detail worth knowing: compressing an already-compressed photo a second time barely helps, since most of the easy savings happen on the first pass, and choosing a smaller maximum dimension shrinks a stubborn file more reliably than repeating compression at the same setting. The re-encode also strips EXIF data — camera model, settings, GPS location — which is a side benefit if you’d rather not share where a photo was taken.

When resizing or converting is the real fix

Compress Image is built around file size, not exact pixel dimensions — it only shrinks width or height if you pick a smaller maximum alongside the target size. If a form instead asks for an exact pixel width, like “800px wide,” Resize Image is the more direct tool: choose a percentage or type a custom width, and the file size follows from that choice rather than driving it. The two pair well together — resize to the required dimensions first, then compress the result if the file is still too heavy afterward.

Format matters too. Compress Image accepts JPG, PNG, and WebP, but not HEIC, the format iPhones save photos in by default. Run an HEIC photo through Convert Image first to turn it into a JPG, then compress that JPG normally — dropping the original HEIC straight into the compressor won’t work.

FAQ

Will compressing my photos make them look obviously worse?

Not at moderate settings — Balanced keeps most photos sharp enough for screens, social posts, and typical uploads. Quality loss becomes visible mainly at the smallest target sizes on photos with a lot of fine detail, so if a result looks rough, try a slightly larger target instead of the smallest one.

What’s the real difference between Compress Image and Resize Image?

Compress Image starts from a target file size and re-encodes the photo to hit it, only touching pixel dimensions if you also pick a smaller maximum. Resize Image works the other way around — you set the exact width or a percentage first, and whatever file size results follows from that choice. Use Resize Image when a form needs a specific pixel width; use Compress Image when the goal is simply a smaller file.

Can I compress a HEIC photo straight from my iPhone?

Not directly — Compress Image works with JPG, PNG, and WebP, and HEIC isn’t among them. Convert the photo to JPG with Convert Image first, then run that JPG through Compress Image as a second step.

Takeaway

Getting a photo small enough to clear an upload limit, without it looking obviously compressed, mostly comes down to matching the tool to the actual problem: Compress Image for file size, Resize Image for an exact pixel width, and Convert Image first if the photo arrived as HEIC. Start with a moderate setting like Balanced, and only drop lower if a portal’s limit genuinely requires it.