KBKB Target

Everyday image sizing

Compress JPEG to 1 MB

Preset and ready: drop a file and the output lands under 1 MB as JPEG — processed entirely in your browser.

Drop your image here or browse

JPEG, PNG, WebP — everything stays on your device

Why this exact limit matters

A one-megabyte JPEG ceiling is less a compression target and more a normalization rule: most photos already fit, camera originals do not, and the systems that state it want predictability rather than savings. At this budget the encoder’s quality ladder nearly always finishes high — the interesting question becomes whether it hit your ceiling at all, and what that means.

Naming the number you need and letting the encoder search for the best quality underneath it is faster and more predictable than any manual slider session. 1 MB is a high limit that mostly matters for large photos and scans, and this page is preset to exactly that ceiling.

How to compress to 1 MB

  1. Drop your image into the box above — it stays on your device.
  2. Confirm the target: under 1 MB as JPEG.
  3. The MozJPEG encoder searches its quality range so the JPEG output lands just under your limit. Dimensions are left at their original size unless the target demands otherwise.
  4. Preview the result, compare it with the original if you want, and download — the filename carries its actual size.

Tip: When you do not know the exact limit, start from the file size you have and halve it — one or two rounds usually lands in the accepted range.

Measured: when the ceiling barely binds

Our 914 KB portrait test file against a 1 MB JPEG ceiling — a rare case where the source already sits under the line:

Source file

914 KB

1500×1800 JPEG

Output

993.8 KB

just under 1 MB

Quality setting

q93

near-original

Resolution

1500×1800

unchanged

The encoder climbed to quality 93 before the ceiling stopped it — output effectively indistinguishable from the source. Feed the same ceiling a 3.2 MB camera original and the story changes completely: quality 28 to keep all 24 megapixels. One ceiling, two regimes: already-fitting files get freshened and normalized; big originals get genuinely compressed.

Frequently asked questions

My JPEG is already under 1 MB — should I still run it through?

Only for a reason: normalizing format (HEIC or PNG to JPEG), stripping metadata, or unifying a batch to one predictable size. Recompressing an already-small JPEG buys nothing and costs a generation of quality.

What actually pushes photos past 1 MB?

Resolution and detail, mostly — current phones write 3–8 MB at 12–50 MP. Noise, complicated backgrounds and high ISO also inflate files at any given quality, because the encoder spends bytes encoding grain.

Is JPEG still the right format at 1 MB, or time for HEIC/WebP?

For interchange, JPEG — everything opens it. HEIC and WebP buy 25–50% smaller files at equal quality but still meet incompatible tools and strict portals. Use them where you control the viewer; use JPEG where the world does.

Does it work on my phone?

Yes — the whole pipeline runs in the browser, including on mobile. There is no app to install and no upload bandwidth to wait for.

Why JPEG and not another format for my upload?

JPEG is the most universally accepted image format on upload forms and gives the smallest files for photographs. If your destination accepts only "images", JPEG is the safe choice.

Do I need an account or app install?

No account, no install, no watermark. The page you are on is the whole tool.

Related size targets