What MP3 Deletes Permanently: Lossy vs Lossless Audio Explained | Rohan
Rohan explains how MP3 encoding permanently deletes audio frequencies based on an auditory masking model, why 128 kbps and 320 kbps differ, and why re-encoding an MP3 repeatedly causes cumulative, irreversible generation loss.
An MP3 is not a smaller copy of your song. Rohan explains that it is a different song entirely, one where an algorithm decided which parts you would not miss and then deleted them permanently.
The 16 kHz cutoff at 128 kbps
Rohan demonstrates this directly with white noise, a signal that contains every frequency at equal energy. Encoded at 128 kilobits and examined again, everything above 16 kilohertz is simply gone, not quieter, gone. Measured directly, at 17 kilohertz the encoded file sits 13 decibels down from the original. That shelf is the first thing every MP3 encoder discards.
Why the encoder targets what your ear cannot hear
The 16 kilohertz cutoff is not arbitrary. The encoder is not trying to preserve the raw signal at all; it is modeling your ear. When a loud sound and a quiet sound sit close together in frequency, you physically cannot hear the quiet one, the loud one masks it. This is auditory masking, and it is the entire trick behind MP3 compression: the encoder finds every masked sound in the signal and spends zero bits encoding it, deleting exactly what you were never going to perceive in the first place.
How bitrate controls the aggressiveness of deletion
The bitrate you choose decides how aggressive that deletion gets. At 128 kilobits, the resulting file is roughly eleven times smaller than the original, and the frequency cliff sits at 16 kilohertz. At 320 kilobits, the file is only about four and a half times smaller, and the audio survives intact all the way up to 19 kilohertz. Same song, same encoder, the only difference is how much the algorithm was permitted to discard.
The hidden cost of re-encoding: generation loss
Here is the part that catches most people off guard. Every re-encode starts the deletion process over from scratch. Rohan took a 128 kilobit file and ran it through ten more rounds of encoding. After those ten passes, the 12 kilohertz band had lost seven decibels. Each pass throws away a little more of the signal, and none of what is discarded ever comes back. Editing an MP3 file and re-exporting it is not a neutral operation, it compounds loss with every round.
When lossy compression is fine, and when it is a mistake
Lossy compression is genuinely fine for listening, streaming, or sharing a rough mix. A well-encoded 320 kilobit file is transparent for almost everyone in these contexts. It becomes a mistake for archiving, mastering, anything you plan to edit later, or anything you intend to feed into a model. The right practice is to keep a lossless master at all times and export a lossy version only at the very end, exactly once. Never work from a file that has already been thinned by a previous round of compression.
Key takeaways
- An MP3 is not a compressed copy of the original audio, it is a permanently altered version with specific frequencies deleted entirely.
- At 128 kbps, everything above roughly 16 kHz is removed; at 320 kbps, audio survives intact up to about 19 kHz.
- MP3 encoders exploit auditory masking, discarding quiet sounds that sit near louder sounds in frequency because the ear cannot perceive them anyway.
- Higher bitrate means less aggressive deletion: 128 kbps shrinks a file about elevenfold, 320 kbps only about four and a half times.
- Re-encoding an already-compressed MP3 causes cumulative generation loss, ten re-encodes of a 128 kbps file lost seven decibels in the 12 kHz band, and none of it returns.
Who this is for
Anyone recording, editing, or archiving audio who needs to understand why working from an MP3 instead of a lossless master causes permanent, compounding quality loss, and when lossy compression is actually the right tool to use.
Chapters
Full transcript(auto-generated, with timestamps)
MP3 compression is permanent deletion
[0:00]Hi, I'm Rohan for Humanitarian's AI. An MP3 is not a smaller copy of your song. It's a different song, one where an algorithm decided which parts you wouldn't miss, and then deleted them permanently. By the end of this, you'll know exactly
The 16 kHz cutoff at 128 kbps
[0:16]What gets thrown away and when that matters. Here's white noise, every frequency equal energy. Now encoded at 128 kilobits and look again. Everything above 16 kilohertz is gone. Not quieter, gone. I measured this on my own machine.
Auditory masking: How encoders think
[0:32]At 17 kilohertz, the encoded file is 13 decibels down. That shelf is the first thing every encoder throws away. Why 16 kilohertz? Because the encoder is not trying to preserve the signal. It's modeling your ear. When a loud sound and a quiet sound sit close together in
128 kbps vs 320 kbps bitrates
[0:50]Frequency, you physically cannot hear the quiet one. The loud one masks it. The encoder finds every masked sound and spends no bits on it. That's the whole trick. It deletes what you were never going to hear. So, the bitrate decides how aggressive that deletion is. At 128 kilobits, the file is 11 times smaller than the original and the cliff sits at
Re-encoding test: The cost of generation loss
[1:12]16 kilohertz. At 320, it's about four and a half times smaller and the audio survives intact all the way to 19. Same song, same encoder. The only difference is how much the algorithm was allowed to discard. Here's the part that catches people. Every re-encode starts the
When to use lossy vs lossless masters
[1:30]Deletion over. I took 128 kilobit file and encoded it 10 more times. The 12 kilohertz band lost seven decibels. Each pass throws away a little more and none of it comes back. Editing an MP3 and re-exporting it is not a neutral operation. So, when is lossy fine? Listening, streaming, sharing a rough mix, a well-encoded 320 file is genuinely transparent for almost everyone. When is it malpractice? Archiving, mastering, anything you'll edit later or feed to a model. Keep a lossless master and export lossy at the very end once. Never work from the thing that has already been thinned. An MP3 isn't compressed, it's edited by an algorithm on your behalf permanently. I'm Rohan Vijayakumar for Humanitarian's AI.
More from HAI
2:00Rohan's Weekly Update: Unblocking the Team with Guides & Suno Tutorials
3:09Suno AI Tutorial Part 2: Advanced Mode & Custom Lyrics
3:15How to Read an Audio Spectrogram (And What It Hides) | Rohan
3:57Suno AI Tutorial Part 1: Make Your First Song (No Music Background)
3:05Nyquist Limit, Sample Rate & Aliasing Explained | Rohan
3:29