Free Online JPEG Compression Level Checker

Last reviewed: 2026-06-25

Upload a JPEG to read the quality level it was saved at - useful for photographers, designers, and web developers who need to know a file's compression headroom before the next save or compress pass. No install, no account required.

Need to act on the result? Once you know the quality level, pair this check with compress image to shrink further, insights image optimizer to see PageSpeed-facing gains, or open the full image tools hub for resize, crop, and format-swap options - all routed through our fast HTTPS processing service.

Not sure what target level to compress to? This reader tells you where a JPG stands today; Compress JPEG without losing quality: quality vs size picks the target level for your next save by task - web upload, archive, social, or email.

Reading the quality first

The reading separates delivery copies from archive copies. A JPG already flagged at quality 50 should not be re-saved at 70 - artefacts get baked in by every subsequent save, and if 80 is the delivery target the archive copy belongs above that, not at the same level. Reading the quality first prevents the silent quality-floor problem where every later save runs at or below an already-low starting point, and the original detail you can no longer recover.

How the reading works

The reading takes a single upload through the HTTPS processing service: the JPG header is parsed server-side to read the recorded quality marker, the value is returned to the page, and the upload copy is rotated out after the retention window. The tool reads the marker only - it does not change or re-save the file - so the next decision (keep, re-compress for delivery, or hand off to a compress tool) gets made on real numbers instead of a screen-side guess.

The accepted inputs are .jpeg and .jpg only: PNG, GIF, WebP, HEIC, and AVIF do not store a single quality scalar in the JPEG sense, so both the upload filter and the server-side service reject any non-JPEG extension before the read is attempted. PNG and GIF use lossless representations; HEIC, AVIF, and WebP have no equivalent scalar - a reader arriving with a non-JPEG file should convert to JPG first.

Reading the quality bands

Once the recorded quality number is back, each band maps to a meaning and a next step - knowing whether the value is 50, 70, or 90 informs the next save in a way no screen-side visual check can match. A high band (around 85 and above) is the source for further work: keep it as the archive, re-save from it for new delivery targets, and take it into compress image to hit a smaller target with predictable loss. A mid band (roughly 65 to 85) has already been re-saved and is best treated as a delivery copy: branch the next save from a separate higher-quality original rather than from the JPG you just read, and do not feed it back through compress unless you have a higher-band archive. A low band (below 65) is at the bottom of its quality budget: stop re-compressing and go back to the original capture for a fresh master.

When you have two .jpg files - a source and a delivered copy, or two versions of the same image you are choosing between - upload each separately and note the two quality numbers: the difference between the recorded markers is a direct before-and-after comparison that tells you how much quality the second save discarded - a more concrete answer than a screen-side visual check on a single device.

A useful follow-up: after re-saving a JPG through a separate compress tool, read the output back here as a second upload. The second reading reports the quality marker recorded by the compressor, making the round-trip auditable in two numbers - input quality and output quality - rather than a screen-side guess.