Compress images online
Shrink JPG, PNG and WebP files in seconds — with a quality slider, before/after compare, and nothing ever uploaded.
Your images
Settings
Generated images
- Nothing uploaded
- Free, no sign-up
- Strips EXIF
- Batch files
Phone photos easily exceed 4 MB — too heavy for email, web forms, websites and messaging apps. LivreImage's compressor uses your own browser's graphics engine to re-encode the image with adjustable quality: in the 80–85 range, files typically shrink by more than 70% with no visible difference.
Tip: for photos, JPG or WebP compress far better than PNG; keep PNG for screenshots and images with transparency. Use the Compare button on each file to check before & after with the sliding lens.
How it works
Two controls do the work on this page: the quality slider and the format bar. Everything else is checking the result before you commit.
Drop the files in
Choose or drag as many as you like, or hit Ctrl+V to paste one straight from the clipboard. Output format opens on Auto, so a JPG comes back a JPG and a PNG comes back a PNG.
Set the quality, or change the format
The slider opens at 82 and runs from 30 to 100. If a photo is still too heavy at 70, the format bar is the bigger lever: JPG and WebP both compress, PNG does not.
Generate, compare, download
Click Generate images. Each result card shows the old size next to the new one, the percentage, the output dimensions and an EXIF stripped tag. Compare opens a full-screen before/after slider. Take the files one at a time, or the whole batch as a .zip.
What the quality slider is actually changing
The number goes straight to your browser's JPEG or WebP encoder, which uses it to decide how much detail to discard block by block. Nothing is resized and nothing is redrawn. The same pixels are simply described with fewer bits.
That is why the first part of the range is nearly free and the last part is brutal. From 100 down to roughly 80 you are mostly discarding information your eye was never going to resolve. Below about 60, flat areas start to band and hard edges pick up a faint fringe. Skies, gradients and lettering go first.
The scale is not portable either. Quality 82 here will not produce the same file another program produces at 82, because every encoder maps that number differently. Judge the result with Compare on the card, not with the number.
The slider and PNG: what actually happens
On Auto, every file keeps its own type, and PNG is lossless. Feed the page a PNG and the slider still moves, but the number is thrown away: the browser's PNG encoder takes no quality argument. Nothing warns you, because on Auto that same slider is still doing real work on the JPGs sitting next to it in the queue.
Click PNG on the format bar and the page stops being quiet about it. The slider grays out, the value reads lossless, and a line appears underneath saying PNG is lossless and photos may get larger.
It can be worse than doing nothing. A PNG re-encoded through the browser sometimes comes out bigger than it went in: the canvas rebuilds it as a full 32-bit RGBA image, so a screenshot that was stored as a compact indexed palette gets rewritten with a far wider color description than it ever needed.
Two ways out. Click JPG or WebP to leave PNG behind, or take pixels off the image instead — that is what Resize image is for.
When compression is the wrong lever
Quality is the second thing to reach for, not the first. Bytes track pixel count, and most images are stored several times larger than anything ever displays them.
- A 4000 px photo that appears in a 900 px column: cut it to 900 px first. That does more than any slider move, and Resize image is the page with that control.
- A screenshot full of text: keep it PNG. JPEG puts a halo around every letter.
- A JPG somebody already squeezed once: re-encoding buys little and costs detail. The second encoder cannot tell the first pass's artifacts from real detail, so it pays to keep both.
- A file you are still editing: compress once, at the end, from the best original you have.
Three things the page decides for you
The queue takes JPG, PNG, WebP, HEIC, GIF, BMP and SVG. A few of those get handled in ways worth knowing before you drop a whole folder in.
- An animated GIF is read as a single frame and saved as a still PNG, and the card labels it GIF to single frame. Nothing on this site produces animated output.
- An SVG is rasterized at whatever pixel size it reports. No control on this page enlarges anything — everything here shrinks or leaves alone — so if the result comes out small, that has to be fixed in the SVG.
- The encoder is your browser's own. There is no switch for progressive versus baseline JPEG, no chroma subsampling control, and the output is written as sRGB. Anything over 10,000 px on the long side is scaled down to fit.
Frequently asked questions
Which quality setting should I pick?
Between 80 and 85 for photos: the file usually shrinks by more than 70% and the difference is imperceptible on screen. Below 60, artefacts start showing in skies and skin tones.
Why does my PNG barely shrink?
PNG is lossless — it discards nothing. For photographs, converting to JPG or WebP saves far more. Keep PNG for screenshots, graphics and transparency.
Does recompressing an already compressed image hurt?
Yes. Every JPG recompression discards more information and the damage accumulates. Start from the original whenever you can.
I need an exact size in KB.
Use the target pages — 50, 100, 200, 500 KB and 1 MB. They search for the highest quality that still fits the limit.
Does reducing width help more than reducing quality?
For large photos, much more. Weight falls quadratically with width: half the width is roughly a quarter of the file, and it looks better.
Two photos, same quality setting, completely different savings. Why?
Because the encoder is compressing content, not file size. Fine detail everywhere — foliage, fabric, grain, crowds — costs bits no matter what you set. Large smooth areas like a studio backdrop or a clear sky cost almost nothing. A number that halves one photo can barely dent another.
Can I compress a file that has already been compressed?
You can, and it usually disappoints. The artifacts from the first pass look like real detail to the second encoder, so you pay to preserve them. If the file genuinely has to get smaller, take pixels off it on Resize image instead of pushing the slider lower.
Can I aim for an exact file size, like under 200 KB?
This page is manual. Move the slider, click Generate again, read the new size on the card — two or three rounds gets you close. Watch Compare as you go, because the last few kilobytes are always the expensive ones.
Do I have to generate again after changing a setting?
Yes. Settings apply when you generate, so the queue is not re-encoded on every nudge of the slider. The button counts the files waiting and switches to Generate again once there are results to replace.