Every time you save a JPEG, rip an MP3, or zip a folder, you’re making a decision — often without realizing it — about whether it’s okay to permanently throw away some of your data to save space. That decision has a name: lossy vs lossless compression. Nearly every format comparison you’ll read (WebP vs PNG, MP3 vs FLAC, H.264 vs ProRes) is really a version of this one underlying question. Understanding it once means every other format decision gets a lot easier.
The Core Idea, in One Sentence
Lossless compression shrinks a file by finding and removing statistical redundancy, in a way that can be perfectly reversed — decompress it and you get back the exact original data, bit for bit. Lossy compression shrinks a file by deciding some of the data doesn’t matter much and throwing it away permanently — decompress it and you get something close to the original, but not identical, and you can never get the discarded part back.
That’s the whole distinction. Everything else in this article is what follows from it.
How Lossless Compression Actually Works
Lossless compression exploits patterns and repetition in data. A simple example: if a file contains the sequence “AAAAAAAAAA” (ten A’s), a lossless compressor can store that as “10×A” instead — far fewer bytes, and completely reconstructable back to the original ten A’s with zero ambiguity. Real lossless algorithms (like the DEFLATE algorithm behind ZIP and PNG) are far more sophisticated than this, but the principle is the same: find redundancy, encode it more efficiently, guarantee perfect reconstruction.
Because lossless compression can only remove redundancy — not information — its compression ratio is fundamentally limited. Highly repetitive data (a screenshot with large flat color areas, a text document) compresses a lot. Data that’s already dense and non-repetitive (a photograph, a piece of music) compresses only modestly, because there isn’t much redundancy left to squeeze out.
How Lossy Compression Actually Works
Lossy compression takes a fundamentally different approach: instead of only removing redundancy, it identifies information a human is unlikely to notice missing and discards it outright. This is why lossy compression can achieve dramatically higher compression ratios than lossless — it isn’t limited to redundancy, it’s allowed to throw away real data, as long as the loss is calculated to be perceptually minor.
A few concrete examples of what actually gets discarded:
- JPEG discards fine color detail more aggressively than fine brightness detail, because human vision is far more sensitive to brightness changes than color — a trick borrowed directly from how the eye works
- MP3 and AAC discard audio frequencies that psychoacoustic modeling predicts are masked by louder nearby frequencies — sounds your ears technically receive but effectively can’t distinguish
- H.264 and H.265 discard subtle pixel-level detail in video frames, more aggressively in fast-moving or complex scenes where the eye has less time to notice
This is why lossy formats hit compression ratios of 10:1, 20:1, or more, while lossless formats typically top out around 2:1 or 3:1 on the same content. The gap isn’t better engineering — it’s a structural consequence of being allowed to discard information instead of only re-encoding it.
Real-World Examples of Each
| Type | Lossy | Lossless |
|---|---|---|
| Images | JPEG | PNG, TIFF (in its compressed mode), BMP (uncompressed, not the same thing — see note below) |
| Audio | MP3, AAC, Opus (at typical settings) | FLAC, ALAC, WAV (uncompressed, not the same thing) |
| Video | H.264, H.265, AV1, VP9 | Rare in practice — nearly all delivered video is lossy; lossless video codecs exist but produce huge files and are used almost exclusively for archival masters |
| General files | — (general-purpose lossy compression is rare) | ZIP, RAR, 7z, gzip |
A note on “uncompressed” vs “lossless”: these aren’t the same thing, and it’s a common mix-up. WAV and BMP are typically stored uncompressed — no compression applied at all, lossy or lossless. FLAC and PNG are losslessly compressed — smaller than the uncompressed original, with zero data discarded. Both WAV and FLAC preserve 100% of the original audio; FLAC is just smaller because it applies real (reversible) compression on top.
When Quality Loss Is Genuinely Imperceptible
Lossy compression has a well-earned bad reputation from over-compressed JPEGs and crunchy low-bitrate MP3s, but at a reasonable setting, the loss is often genuinely inaudible or invisible:
- A JPEG saved at quality 80–90 is visually indistinguishable from the original for the vast majority of viewers, on the vast majority of screens, at normal viewing distance — while being a fraction of the file size of a lossless PNG of the same photo
- An MP3 or AAC file encoded at 256–320 Kbps is commonly described as “near-transparent,” meaning trained listeners struggle to reliably distinguish it from the lossless source in blind tests
- A well-encoded H.264 or H.265 video at an appropriate bitrate for its resolution looks clean and artifact-free on a typical screen — see our guide on what bitrate actually measures for why bitrate, not the codec name alone, is what actually determines this
For anything that’s a final, one-time delivery — a photo posted to social media, a song streamed to a phone, a video uploaded to YouTube — lossy compression at a sane quality setting is very often the objectively correct choice: smaller files, faster loading, and no meaningfully perceptible downside.
When It Genuinely Matters
Quality loss stops being irrelevant in a few specific, recurring situations:
- You’re going to edit the file again. Every re-save of a lossy file throws away more data on top of what was already discarded — generational loss, and it compounds with each round trip. A photo repeatedly opened, edited, and re-saved as JPEG visibly degrades after enough cycles, even if each individual save looks fine. Working files that will be edited multiple times belong in a lossless (or uncompressed) format until the final export
- You need pixel-perfect or sample-perfect accuracy. Medical imaging, scientific data, screenshots with sharp text, and any archival master you might need reproduced exactly later all call for lossless formats — artifacts invisible on a photo become obvious on a line-art diagram or a block of text
- You’re stacking heavy compounding effects. Aggressive color grading, extreme zoom/crop, or repeated re-encoding through multiple pipeline steps (common in professional video workflows) exposes artifacts that were invisible in the original file, because the manipulation amplifies what was already a small, hidden loss
- Transparency and flat color need to stay exact. PNG’s lossless compression is why it remains the standard for logos, icons, and UI graphics with hard edges — lossy compression tends to introduce visible smudging right around sharp edges, exactly where flat graphics have the most of them
A Practical Decision Framework
| If this is true of your file… | Use |
|---|---|
| It’s a final version being delivered, shared, or published | Lossy (JPEG, MP3/AAC, H.264/H.265) — smaller, faster, no meaningful quality cost |
| You’ll edit or re-export it again later | Lossless or uncompressed (PNG, FLAC/WAV, ProRes/DNx for video) until the final export |
| It has sharp edges, flat colors, or text (logos, screenshots, diagrams) | Lossless (PNG) — lossy compression artifacts are most visible exactly here |
| It’s a photographic image, natural audio recording, or natural video with lots of visual/audio complexity | Lossy is usually fine and often preferable — there’s more redundancy for perceptual compression to safely exploit |
| It’s an archival master you might need exactly reproduced later | Lossless, even though it costs far more storage — you can always make a lossy copy from a lossless master, but never the reverse |
| Storage or bandwidth is the binding constraint and quality tolerance is high | Lossy, tuned to the lowest quality setting that still looks/sounds acceptable for the use case |
The one-line version: lossless when the file might get worked on again or needs to be exact; lossy when it’s a finished product going out the door.
Where This Shows Up Across Formats
This lossy/lossless split is the backbone of nearly every specific format comparison:
- Images: see our WebP vs JPEG vs PNG comparison for how PNG’s lossless approach and JPEG/WebP’s lossy modes trade off in practice
- Audio: see what FLAC actually is for a deep dive on lossless audio specifically, including when it’s genuinely worth the larger file size over MP3
- Video: see our H.264 vs H.265 comparison for how two lossy codecs differ in compression efficiency, and our explainer on what bitrate actually measures for the setting that determines how aggressive that loss actually is
If you’re compressing your own images or video and want the lossy approach without guessing at settings, AllMediaTools Image Compressor and AllMediaTools Video Compressor both use quality-targeted lossy compression by default, tuned to stay in the “imperceptible loss” range described above rather than requiring you to pick a raw quality number yourself.
Frequently Asked Questions
Is lossless always better quality than lossy?
Technically yes — lossless preserves 100% of the original data, while lossy discards some. But “better quality” only matters if the discarded data was ever going to be perceptible, and at reasonable lossy settings it usually isn’t. Lossless quality superiority is real but often not meaningfully visible or audible in normal use.
Why are lossy files so much smaller than lossless files of the same content?
Because lossy compression is allowed to permanently discard information judged to be perceptually unimportant, not just remove redundancy the way lossless compression does. That structural difference — discarding data vs. only re-encoding it more efficiently — is why lossy formats routinely achieve 5–10× better compression ratios than lossless ones on the same photo, song, or video.
Can I convert a lossy file back to lossless and get the quality back?
No. Once data is discarded during lossy compression, it’s gone — converting a JPEG to PNG, or an MP3 to FLAC, doesn’t restore anything; it just wraps the already-degraded data in a lossless container. The only way to get lossless quality is to start from a source that was never lossy-compressed in the first place.
Should I always save my working files as lossless?
For anything you’ll edit again — photos mid-retouch, audio mid-mix, video mid-edit — yes, this avoids compounding generational loss across multiple saves. For a final, one-time export meant for delivery or publishing, lossy at a sensible quality setting is usually the better practical choice.
Does lossy compression always look or sound obviously worse?
Not at reasonable settings. Over-compressed lossy files (very low-quality JPEGs, low-bitrate MP3s) do look and sound obviously worse, but that’s a settings problem, not an inherent property of lossy compression — a JPEG at quality 85 or an AAC file at 256 Kbps is very difficult for most people to distinguish from the lossless original.