How to Compress JPG Online Free

A JPG is already a lossy, compressed photo. It does not store every pixel exactly; it stores a clever approximation that the eye reads as the original. So compressing a JPG is not about squeezing untouched data. It is about re-encoding the picture with a slightly rougher approximation that takes fewer bytes.

That distinction matters, because every JPG you save has a quality factor baked in, and lowering it throws away real detail for good. Done gently, the loss is invisible and the file drops a lot. Done hard, edges break into blocks. This guide explains the actual machinery of JPEG compression, shows exactly which knob controls the trade-off, and marks where the line sits between an invisibly smaller file and a visibly broken one.

JPG is already compressed

When a camera or an export first writes a JPG, it runs the picture through the JPEG algorithm standardized as ISO/IEC 10918, first published in 1992 by the Joint Photographic Experts Group.^[1] That process splits the image into small blocks, converts each block into frequency patterns, and throws away the fine detail the eye is least likely to notice. It also stores color at lower resolution than brightness, a step called chroma subsampling, because human vision resolves changes in color far less sharply than changes in light and dark. All of that already happened before you ever opened the file.

Compressing it again simply repeats the discarding step more aggressively. There is no lossless "just pack it tighter" mode hiding inside a standard JPG, so any real size reduction comes from letting a little more detail go. The file on disk that ends in .jpg is usually wrapped in the JPEG File Interchange Format (JFIF), a simple container that carries the compressed image data plus basic metadata such as resolution and an optional thumbnail.^[2]

How JPEG compression really works

To compress a JPG well, it helps to know what the encoder is doing under the hood. JPEG compression is a pipeline of four main stages, and every one of them shapes the final file.

First, the encoder converts the image from RGB to a luminance-chrominance color space, usually called YCbCr. It separates the brightness of each pixel (the Y channel) from its color (the Cb and Cr channels). This split is what makes the later color-reduction step possible, because brightness and color can then be treated differently.

Second, the image is broken into 8-by-8 pixel blocks, and each block is run through a mathematical operation called the discrete cosine transform, or DCT. The DCT does not change the pixels; it re-expresses each block as a sum of frequency patterns, from the flat average tone of the block up through progressively finer waves of detail. A block of clear blue sky ends up described almost entirely by its low-frequency terms, while a block full of texture spreads energy into the high-frequency terms. Crucially, no information is lost at this stage: the DCT is reversible.

Third comes quantization, the one genuinely lossy step, where the encoder divides each frequency coefficient by a value from a quantization table and rounds to the nearest whole number. High-frequency detail, which the eye barely registers, is divided by large numbers and frequently rounds all the way to zero. This is where bytes are actually saved and where quality is actually lost.

Fourth, the now mostly-zero coefficients are packed with lossless entropy coding (Huffman coding in a baseline JPG), which stores long runs of zeros compactly. This final stage adds no further loss; it just packs the already-reduced data efficiently.

Quantization: the step that discards detail

Quantization is the heart of JPEG and the reason a "quality" number exists at all. The quality factor you choose does not tune some abstract slider; it scales the quantization table. A high quality factor uses small divisors, so most coefficients survive and detail is preserved at the cost of size. A low quality factor uses large divisors, so more coefficients round to zero, the file shrinks, and detail is lost for good.

This is also the origin of the classic JPEG artifacts. Because compression happens block by block, pushing quality too low makes the boundaries between 8-by-8 blocks visible as a faint grid, an effect called blocking. Around sharp high-contrast edges, aggressive quantization produces faint ripples or halos, an effect called ringing. Both come directly from throwing away the high-frequency coefficients that described those fine transitions. Knowing this tells you exactly where to look when judging a compressed JPG: the block edges and the sharp lines are always the first things to break.

Chroma subsampling and color loss

The second lever hidden inside JPEG is chroma subsampling. After the color space split, the encoder can store the two color channels at half or quarter resolution while keeping brightness at full resolution. This is written in ratios like 4:4:4 (no subsampling, full color), 4:2:2 (color halved horizontally), and the very common 4:2:0 (color halved in both directions). Because the eye is far more sensitive to brightness than to color, 4:2:0 discards three quarters of the color samples while looking almost identical on photographs, which is why it is the default for most cameras and web exports.

The catch is that subsampling hurts exactly the images that are not photographs. Red text on a dark background, sharp colored lines, and saturated graphics can look smeared or fringed under 4:2:0, because their crisp color edges get blurred. If a JPG contains fine colored detail rather than photographic gradients, choosing full-resolution color (4:4:4) preserves it, at the cost of a slightly larger file. For a plain photo, 4:2:0 is essentially free size savings.

What the quality factor really controls

The quality slider, usually shown from 0 to 100, sets how aggressively the quantization table divides those frequency coefficients. It is not a linear dial: the top of the range costs a lot of bytes for changes almost nobody can see, while the middle holds up remarkably well. The exact numbers are also not standardized between tools, so quality 80 in one encoder is not guaranteed to match quality 80 in another, which is why previewing matters.

Compress a JPG, step by step

1. Open the tool and add your JPG

   Open the FileFormer image converter and drop your photo in. It runs on your device, so the image is never uploaded.

2. Set the quality factor

   Start around 80 and adjust. Most photos survive a drop to 75 with no visible change while getting noticeably smaller.

3. Preview at full zoom

   Look closely at edges and flat areas. If you see blocky squares or halos, raise the quality a few points and try again.

4. Export, or try a modern format

   Download the smaller JPG. If you want the same look for even fewer bytes, convert to WebP or AVIF instead.

Right settings for real situations

The best setting is never a single number; it depends on the picture and where it will be seen. A few common cases show how the levers combine.

The recurring lesson is that resizing the pixel dimensions almost always saves more than lowering quality, and it does so without the blocking that hard quality cuts introduce. If a photo will be shown 800 pixels wide, storing it at 4000 pixels wide and then crushing the quality to hit a size target is the worst of both worlds. Shrink the dimensions to what the destination actually needs, and only then trim quality.

Generation loss and repeated saves

Because JPG discards detail every time it is written, saving a JPG over and over slowly degrades it, a problem called generation loss. Each pass runs the picture through quantization again, and each pass rounds away a little more, adding blocking that never comes back. Editing a JPG, saving, reopening, editing, and saving again is the classic way to quietly ruin an image. Always compress from the highest-quality original you have, not from a copy you already squeezed, and keep that original safe.

A subtle detail helps here: re-saving a JPG at the exact same quality with the same encoder settings still causes some loss, because the block boundaries and rounding rarely line up perfectly with the previous pass. The only truly lossless JPG operations are specific ones like rotating by 90 degrees or cropping on block boundaries, which some tools perform without re-encoding at all. For anything that touches the pixels, treat every save as a fresh, permanent quality decision.

When a modern format beats re-compressing

There is a bigger lever than the quality slider. Newer image formats use more advanced compression than JPEG's 8-by-8 DCT, so at a matching level of visible quality they produce a smaller file. Converting to WebP usually saves a solid chunk over an equivalent JPG, and AVIF, which is built on modern video-codec technology, often saves more again while handling gradients with far less banding. If the destination supports them, they generally beat re-compressing the JPG.

The honest caveat is compatibility and generation loss. Converting an existing JPG to WebP or AVIF still starts from lossy data, so you inherit whatever the JPG already discarded; you cannot recover detail that is gone. And a handful of old email clients and legacy tools still do not display the newer formats. For maximum reach, JPG remains the safest choice; for the smallest file at a given quality on a modern site, a newer format wins. When you have the lossless original, encoding straight to WebP or AVIF from that master, rather than from the JPG, gives the cleanest possible result.