What Is ReplayGain? The Standard Behind MP3Gain

ReplayGain is a method for measuring how loud a piece of audio sounds to a human listener — rather than how high its peaks are — and expressing that measurement as a single gain adjustment relative to a reference loudness of 89 dB SPL. It was proposed by audio engineer David Robinson in 2001, in a document titled “Replay Gain — A Proposed Specification.” It is the algorithm inside MP3Gain and foobar2000, the reason every ReplayGain tool targets the same 89 dB, and still the standard way to make a personal music library play at one consistent volume.

The problem it was built to solve

By 2001, anyone with a folder of MP3s from different CDs had the same daily irritation: every album played at a different volume, because every mastering engineer had chosen a different level — and the trend, the “loudness war,” was toward ever hotter masters. The obvious fix of the time, peak normalization, barely helped: it equalized the loudest instant of each track while leaving perceived loudness all over the place, since a single drum hit says nothing about how loud a song feels. Robinson’s proposal started from psychoacoustics instead: measure the loudness the way ears experience it, and normalize that.

How the measurement works

A ReplayGain analysis runs through three ideas. First, the audio passes through an equal-loudness filter that mimics human hearing — we are most sensitive to midrange frequencies and relatively deaf to deep bass at low levels, so the measurement weights frequencies the way an ear does. Second, the filtered signal’s energy (RMS level) is sampled in short blocks across the whole track. Third, instead of averaging those blocks — which silence and quiet passages would drag down — the specification takes a value near the top of the distribution (the 95th percentile), representing the level the track sustains when it is actually playing. That figure is compared against the reference, and the difference is the ReplayGain adjustment: “this track needs −6.3 dB.”

The specification defines two modes, which MP3Gain users know well: Track Gain (originally “Radio Gain”), where every song is brought to the reference independently, and Album Gain (“Audiophile Gain”), where one shared adjustment preserves an album’s internal dynamics. Their differences and uses are covered in Track Gain vs Album Gain.

Where the 89 dB came from

ReplayGain needed a fixed point, and Robinson borrowed one from the film industry. The SMPTE calibration standard for cinema sound says a pink-noise test signal at −20 dB relative to full scale should play back at 83 dB SPL (sound pressure level) in the theatre. The original proposal worked from that 83 dB reference — but implementations quickly settled on playing the reference 6 dB hotter, equivalent to pink noise at −14 dBFS, which on the same calibrated scale is 89 dB SPL. Robinson endorsed the change, and 89 dB became the de facto reference for every ReplayGain tool — it is the “Target Normal Volume” you see in MP3Gain, whose full story is in the 89 dB explainer. The point of any reference is not the number itself; it is that everyone uses the same one, so an analysis made in one program means the same thing in another.

A measurement, not a change: tags and players

ReplayGain itself only defines the measurement and the values. In its most common form, those values are written into a file’s metadata tags (for MP3s, typically APEv2 or ID3v2 tags), and a supporting player applies the adjustment during playback — the audio data is never modified. foobar2000 is the best-known player that both scans and applies ReplayGain this way, and FLAC and Vorbis files carry ReplayGain fields as part of their format conventions.

MP3Gain is the famous exception, and the reason it exists as a separate program: instead of relying on players to honor tags, it applies the ReplayGain adjustment directly to the MP3 frames’ gain values, so the correction works in every player and device ever made — at the price of working only on MP3s. That mechanism is detailed in Is MP3Gain Lossless? and the MP3Gain overview.

Support in practice: broad, but not universal

On the desktop, ReplayGain support is deep: foobar2000 scans and applies it natively, as do MusicBee, MediaMonkey, and most Linux players, and tag editors can write the values without playing a note. The picture thins out as you move away from computers. Many hardware players, car head units, and smart speakers ignore ReplayGain tags completely, and Apple’s ecosystem uses its own Sound Check system instead — similar in spirit (a per-track loudness value stored in metadata) but not interchangeable with ReplayGain values. This patchiness is not a footnote to the ReplayGain story; it is the direct reason MP3Gain’s file-level variant matters. A gain change written into the MP3 frames needs no support from anyone, which is why a tag-based standard ended up with a tag-free flagship tool.

ReplayGain today

ReplayGain was a proposal, never an ISO standard — it spread because it worked and because the specification was public. Two decades on, it remains the native loudness system of the file-based music world: players, taggers, and formats still support it, while the streaming and broadcast industries standardized on the younger, absolute LUFS scale (ITU-R BS.1770). A community revision, ReplayGain 2.0, later adopted BS.1770-style measurement under the ReplayGain name, bringing the two systems closer; the three-way comparison explains how they relate. Its values also became a shared vocabulary: when experienced users say a master “measures about 97 dB,” everyone in the conversation knows which ruler produced the number and what it implies. For the original job — a hard drive full of music that should play at one volume — the 2001 design, and MP3Gain with it, never needed replacing.

Why MP3Gain Changes Volume in 1.5 dB Steps

MP3Gain changes volume in 1.5 dB steps because that is the finest adjustment the MP3 format itself allows without re-encoding. Every MP3 frame stores a gain value, and that value can only move in fixed increments: each step multiplies the signal by 2^1/4 (about 1.19×), which works out to 1.5 dB. So MP3Gain rounds each track’s ideal adjustment to the nearest available step, landing at most 0.75 dB — half a step — from the exact target. Finer steps exist only on the other side of a decode-and-re-encode, which is precisely what MP3Gain refuses to do.

Inside an MP3 frame

An MP3 file is not one continuous stream of sound; it is a chain of thousands of frames. Each frame contains 1,152 samples of compressed audio — roughly 26 milliseconds at CD sample rates — plus a small block of “side information” telling the decoder how to reconstruct that slice: which compression tables to use, and at what level to play it. That playback level is the global gain field, and it is the only volume control the format exposes without touching the audio data itself. MP3Gain’s entire lossless method, explained in Is MP3Gain Lossless?, consists of rewriting this one field, frame by frame.

Why exactly 1.5 dB?

The global gain is a counter, not a dial. Increasing it by one does not add a fixed amount of amplitude — it multiplies the decoded signal by the fourth root of two (≈1.189). In decibel terms, that multiplication is 20 × log₁₀(1.189) ≈ 1.51 dB — which everyone rounds to 1.5 dB. The MP3 designers chose this exponential scale deliberately: it gives a wide range of adjustment (the field spans far more range than any normalizer needs) while keeping the side information small. But it hard-codes the granularity. There is no setting, in any tool, that makes a frame-level gain change of 0.5 dB or 1.0 dB, because the format has no way to write it down.

What “within 0.75 dB of target” means in practice

Say analysis decides a track needs −5.2 dB to reach the 89 dB target. MP3Gain cannot apply −5.2. It applies −4.5 dB (three steps) or −6.0 dB (four steps) — whichever is nearer, here −4.5, leaving the track 0.7 dB hotter than the ideal. The worst possible case is a requirement falling exactly between two steps: an error of 0.75 dB, half a step.

Is that audible? A level difference of about 1 dB is roughly the smallest most listeners can detect in a direct, instant A/B comparison of the same recording — and MP3Gain’s worst-case error is below that, applied uniformly to a whole track, in a library where every track carries a similar small rounding. In real listening across different songs, a ≤0.75 dB residue is not a difference anyone can hear as a volume jump. It is also worth noting what the step does not disturb: in Album Gain mode, the same number of steps is applied to every track, so the carefully preserved level differences within an album remain exact.

The alternative MP3Gain refuses

Any tool can change volume in 0.1 dB increments — by decoding the MP3 to raw audio, scaling it precisely, and encoding a new MP3. The cost is a second generation of lossy compression: artifacts compound, and the change can never be undone. MP3Gain’s designers made the opposite trade in 2001 and it remains the right one for library work: accept a rounding of at most 0.75 dB, in exchange for changes that are lossless, reversible, and honored by every player ever made. If a track absolutely must sit at an exact level for professional delivery, that is an editing job with different tools and different costs — not a normalization job.

So the 1.5 dB step is not a limitation of MP3Gain the program. It is a property of the MP3 bitstream, and MP3Gain is simply the tool honest enough to work within it rather than quietly re-encode your music.

You can watch the steps at work in MP3Gain itself. Apply Track Gain, then nudge the target volume up by half a decibel and apply again: most tracks do not move at all, because their nearest available step has not changed. Move the target by a full 1.5 dB and every applied value shifts by exactly one step. The “Track Gain” figures MP3Gain reports are always whole multiples of 1.5 dB — the frame format’s fingerprint, visible right in the interface once you know to look for it.

Why not just store a precise value in a tag?

A fair question: ReplayGain tags store adjustments at full precision — “−5.23 dB,” not a rounded step. If precision were the only goal, tagging would win. But a tag is only an instruction, and it works only where a player chooses to read and obey it. Plenty of players, car stereos, and hardware devices ignore ReplayGain tags entirely, and on those devices a precisely tagged file plays at its original, uneven volume. MP3Gain’s founders chose the opposite trade: write the change into the frames, where every decoder must obey it, and accept the format’s 1.5 dB granularity as the price. Precision you can’t hear, traded for compatibility you use every day.

Steps do not accumulate

One more worry worth retiring: processing a file twice does not double the rounding error. MP3Gain re-analyzes the track’s loudness on each pass and adjusts the gain field to the value the current target requires — it does not blindly stack another rounded change on top of the last one, and the undo data in the tag always remembers the original state. An MP3Gain-processed file can be re-targeted next year, or restored entirely, with the same ≤0.75 dB rounding it had on day one. Compare that with repeated re-encoding, where every generation permanently discards more of the audio. The step size is a fixed property of the container; unlike encoding loss, it never compounds.

Is MP3Gain Lossless? How It Changes Volume Without Re-Encoding

Yes — MP3Gain is lossless in the sense that matters: it never decodes or re-encodes your audio. Every MP3 frame carries a built-in “global gain” value that the decoder applies during playback. MP3Gain rewrites that value, in fixed steps of 1.5 dB, and stores the original values plus its analysis in an undo tag inside the file. The compressed audio data — the part that actually holds the music — is not touched, so a change can be reversed exactly, back to the original file, at any time. No second round of MP3 compression ever happens.

First, an honest definition

“Lossless” needs one qualification, and this site will not hide it: the MP3 format itself is lossy. When a song was first encoded to MP3, some audio information was discarded permanently — that happened long before MP3Gain existed, and nothing can undo it. What “lossless” means for MP3Gain is narrower and completely true: the program adds no further loss. After MP3Gain processes a file, the audio data inside it is bit-for-bit identical to before; only gain instructions and tag data changed. Compare that with running the same file through an editor to normalize it: the editor must decode the MP3 to raw audio, change the level, and encode a brand-new MP3 — a second lossy generation that discards a little more quality, even at a high bitrate.

How the trick works: the global gain field

An MP3 file is a stream of small frames, each holding a fraction of a second of compressed audio plus the instructions a decoder needs to play it. One of those instructions is a gain value: essentially, “play this frame this loud.” The MP3 designers included it so decoders could adjust level cheaply, and it is the lever MP3Gain uses. To make a track 3 dB quieter, MP3Gain subtracts two steps from the gain value in every frame — two steps being 3 dB, because the field can only move in steps of 1.5 dB (the subject of its own explainer). The compressed audio payload in each frame stays exactly as it was.

It is also why MP3Gain processing is fast: applying a change means rewriting one small field per frame, with no re-encoding pass, so even a library of thousands of files is processed in minutes rather than hours. Because the change lives in the frames themselves, it works everywhere: car stereos, cheap hardware players, DJ software, phones — no player needs to “support” anything. This is the crucial difference from tag-based ReplayGain, where the adjustment is written into metadata and only cooperating players apply it. MP3Gain’s approach is why its results follow the file to any device, as the program overview describes.

The undo tag: reversibility is built in

When MP3Gain analyzes and adjusts a file, it writes an APEv2 tag recording the analysis results and the gain it applied. MP3Gain’s “Undo Gain changes” feature reads that record and restores every frame’s original gain values — not approximately, but exactly, returning the file to its pre-MP3Gain state. You can process a library, live with it for a year, change your mind about the target volume, undo everything, and start again with zero quality consequence. Very few audio tools can make that promise.

One practical warning follows from the design: the undo record lives in the tag. If some other program strips or rewrites the file’s tags carelessly — aggressive “tag cleaners” are the usual culprit — the undo information can be lost. The gain change itself still stands (it is in the frames, not the tag), but it can no longer be reversed automatically. Keep backups of a large library before batch work, as you should before any bulk file operation.

What MP3Gain does not do

• It does not improve a bad MP3. A 128 kbps file with encoding artifacts stays exactly that file, played at a better-matched volume.
• It does not repair clipping or distortion already baked into a recording. It can avoid adding clipping (see the clipping explainer), nothing more.
• It does not hit the target with infinite precision. The 1.5 dB step means a track lands within 0.75 dB of the ideal value — inaudible in real listening, and the honest price of never re-encoding.
• It does not work on other formats. The frame-gain mechanism is an MP3 feature. FLAC, AAC, and OGG need their own (tag-based) ReplayGain routes.

So the short answer stands: for the job it does — changing how loud an MP3 plays — MP3Gain is lossless, reversible, and exact about what it touches. That combination is the entire reason a program last updated years ago is still the standard recommendation.

Does it change the bitrate or file size?

No — and this is a good self-check if you ever doubt what a tool did to a file. A track that was 192 kbps before MP3Gain is 192 kbps after; the frames hold the same compressed audio at the same rate. The file size is essentially unchanged too, apart from a small tag (typically a few hundred bytes) that MP3Gain adds to store the analysis and undo information. If you run a file through a process and it comes out a different size, a different bitrate, or a different length, something decoded and re-encoded it — that is exactly the fingerprint MP3Gain never leaves.

The same logic answers a question users ask after their first batch: “If nothing was re-encoded, why did my player show a different volume immediately, even an old one?” Because the player was never doing anything clever. Decoders have always read the per-frame gain field as part of normal playback; MP3Gain simply wrote different values into a field every decoder already obeys. There is no compatibility layer, no plug-in, and no metadata negotiation — which is precisely why the method has survived every player generation since 2001.

ReplayGain vs LUFS vs Peak Normalization: Three Ways to Measure Loudness

Peak normalization, ReplayGain, and LUFS answer three different questions. Peak normalization asks: “How close is the loudest instant to the maximum the format can store?” ReplayGain asks: “How loud does this track sound, compared to a reference of 89 dB SPL?” LUFS — the scale defined by the ITU-R BS.1770 standard — asks: “How loud does this sound, in absolute terms, integrated over the whole track?” Streaming services normalize with LUFS; MP3Gain uses ReplayGain, because it was built for personal music libraries in 2001, a decade before BS.1770 loudness became the broadcast and streaming norm.

The three systems side by side

Peak normalization: the loudest instant wins

Peak normalization is the oldest and crudest method: find the highest sample in the file, then scale the whole file so that peak touches a set level, usually 0 dBFS. Every audio editor’s “Normalize” button historically did exactly this. Its flaw is fundamental — a peak is an instant, not an impression. A track with one loud drum hit and an otherwise quiet performance peak-normalizes to the same value as a wall of compressed sound, yet the second sounds dramatically louder. Two songs can both sit at 0 dBFS peak and differ by 10 dB or more in perceived loudness. Peak levels still matter as a safety check (clipping is a peak problem), but as a loudness measure, peak normalization answers the wrong question.

ReplayGain: loudness relative to 89 dB

ReplayGain measures how the audio actually sounds: the signal is filtered to mimic the ear’s frequency sensitivity, its energy is averaged in short blocks, and a high percentile of those blocks — rather than a single peak — becomes the track’s loudness. The result is expressed as a gain adjustment relative to the shared 89 dB reference. That relative design is why ReplayGain values travel so well between tools: MP3Gain, foobar2000, and supporting players all measure from the same fixed point, so a track analyzed once is understood everywhere. The full story is in What Is ReplayGain?

LUFS: the absolute scale the industry moved to

LUFS (loudness units relative to full scale; the identical scale is also written LKFS) comes from ITU-R BS.1770, a standard built for broadcasters who needed different networks and countries to agree on loudness. It uses K-weighting — a defined frequency weighting — plus gating that excludes silence and quiet passages from the integrated measurement, and it reports an absolute number: a track is −14 LUFS, full stop, no reference point to know. Regulation and platforms adopted it: European broadcast targets −23 LUFS (EBU R128), and streaming services normalize playback to their own targets, commonly around −14 LUFS for Spotify and YouTube and −16 LUFS for Apple Music.

A later development, ReplayGain 2.0, adopted BS.1770-style measurement inside the ReplayGain framework, and a documented conversion between the two scales exists — the two worlds are cousins now, not strangers. But classic MP3Gain implements the original 2001 algorithm, and for balancing a music library that remains entirely fit for purpose — for the MP3 files that dominate older collections, its readings are still the practical common language between tools.

Which one should you care about?

• Making your own library play evenly: ReplayGain, via MP3Gain. It is the only one of the three designed for exactly this, and it works at the file level, in every player.
• Publishing music or video to streaming platforms: LUFS. Master to the platform’s target (around −14 LUFS for music streaming) so their normalization doesn’t make the decision for you.
• Checking technical headroom: peak levels. A peak readout tells you how close you are to clipping — a safety gauge, never a loudness target.
• Podcasts and spoken word for distribution: LUFS again — podcast platforms publish loudness targets (commonly −16 LUFS for stereo podcasts), and meeting them keeps episodes consistent across apps in a way no peak setting can.

The mistake to avoid is mixing the scales: an MP3Gain reading of “91.5 dB” and a meter reading of “−11 LUFS” describe the same song through different rulers, and neither number can be typed into the other system.

Frequently asked questions

Is LUFS better than ReplayGain?

For broadcasters and streaming platforms, LUFS is the better tool: it is an absolute, regulated standard with gating that handles mixed content like speech and adverts. For leveling a personal MP3 library, ReplayGain is equally accurate in practice and is what the available tools implement. “Better” depends on the job.

Why does MP3Gain show dB instead of LUFS?

Because MP3Gain implements the original ReplayGain specification from 2001, which expresses results as a gain relative to the 89 dB SPL reference. BS.1770 and LUFS did not exist yet. The program’s design predates the scale, and its results remain compatible with every other ReplayGain tool.

Can I convert a ReplayGain value to LUFS?

Approximately. ReplayGain 2.0, which adopted BS.1770 measurement, defines a bridge between the scales (roughly, an integrated loudness of −18 LUFS corresponds to a ReplayGain value of 0 dB). Classic MP3Gain’s 1.0 analysis can differ by a dB or so on some material, so treat any conversion as an estimate, not an exact translation.

Clipping in MP3Gain: What the Red Text Means and How to Avoid It

In MP3Gain, clipping warnings — the red “Y” in the “clip” column and red-highlighted values after analysis — mean that if the track were raised by the full amount needed to reach the target volume (89 dB by default), its loudest peaks would exceed 0 dBFS, the maximum value the audio can store, and would be flattened into distortion. The warning is not damage MP3Gain has done: it appears after analysis, before you apply anything. MP3Gain’s “Don’t clip” option exists precisely to act on this warning automatically, by capping the applied gain at the highest level that stays clean — even when that leaves the track a little below target.

What clipping is, in ten seconds

Every digital audio format has a ceiling. A waveform peak that tries to go above it has nowhere to go, so the top is sliced flat — and a sliced waveform is distortion: harsh, crackly, and permanently baked into the sound. Tracks only clip when they are made louder. Turning a loud track down to reach the target can never clip it, which is why clipping in MP3Gain is almost always a story about quiet tracks being raised.

Where MP3Gain shows it

After Track Analysis or Album Analysis, look at the “clip” column. A red Y means: at the current target volume, applying this track’s full suggested gain would push its peaks past the ceiling. MP3Gain also calculates, for each track, the maximum gain that could be applied without clipping — the headroom the file actually has. Nothing has been changed at this point; analysis only measures. The clipping happens (or doesn’t) at the moment you press a Gain button, and it depends on one setting.

The “Don’t clip” option: the automatic fix

Under Options, MP3Gain offers “Don’t clip when doing Track Gain” (and the equivalent for Album Gain). With it enabled, MP3Gain compares each track’s suggested gain with its no-clip maximum, and applies the smaller of the two. The track may finish slightly below the target volume, but its peaks stay intact. With the option disabled, MP3Gain applies the full suggested gain and the red-Y tracks genuinely clip — audibly, if the overshoot is more than a brief transient.

Our standing advice, echoed in the recommended settings, is to leave “Don’t clip” on. A track that ends 1 dB under target is a non-event; a clipped track is damaged until you undo and redo it.

Why dynamic tracks are “left quieter” — and why that’s correct

The tracks most often flagged are the ones with the widest dynamic range: classical recordings, acoustic sessions, film-score albums. Their average loudness is low, so the analysis asks for a big boost — but their rare loud peaks are already near the ceiling, so almost no boost is actually available. Average and peak are simply far apart in this kind of music, and no tool can raise the average without either squashing the dynamics (compression, a different and destructive process) or clipping the peaks.

So when a symphony movement finishes at 86 dB instead of 89, MP3Gain has not failed. It has told you the truth about the recording: this is as loud as it gets without distortion. In Album Gain mode the same logic applies to the whole album at once — one hot peak on one track can cap the shared gain for all of them, which is also correct, because the album’s internal balance is the thing being protected. The 89 dB explainer covers why the target itself is set where it is.

Your options when a track would clip

• Accept the cap (recommended). Leave “Don’t clip” on and let the track sit slightly under target. In a full library you will not notice a 1–2 dB shortfall on one album.
• Lower the target volume. Dropping the target from 89 to, say, 87 dB reduces every boost, so fewer tracks hit the ceiling. You trade overall level for headroom across the whole library.
• Override deliberately, per track. A few experienced users disable “Don’t clip” for a track whose overshoot is a single inaudible click or transient. This is a judgement call about specific audio, not a general setting — and since MP3Gain changes are reversible, you can listen, and undo if you hear distortion.
• Never “fix” it by re-encoding. Running the file through an editor’s normalize or limiter changes the audio permanently and costs quality. MP3Gain’s whole point is that it doesn’t.

Finally, a boundary worth knowing: MP3Gain can only prevent new clipping. A file that was already clipped when it was mastered arrives damaged, and no gain setting repairs it — turning it down hides nothing. That is an editing problem, not a gain problem.

One subtlety: MP3Gain judges the decoded signal

MP3Gain’s clipping prediction is more trustworthy than a simple look at the file’s numbers, because its analysis works on the audio as decoded — the same signal your player will produce. This matters because MP3 decoding itself can reconstruct peaks slightly higher than the ones in the original recording; a track whose studio master peaked just under the ceiling can decode with peaks a fraction of a dB over it. That is also why an occasional track shows a clipping warning even before any gain is applied at all: the file, as decoded, is already that close to the edge. In that situation MP3Gain has nothing to fix and nothing to apologize for — lowering the track’s gain slightly is the only clean response, and the analysis has shown you exactly how much room you have.

The red text, in other words, is a measurement, not an accusation. Treat the “clip” column the way you would treat a fuel gauge: it is there so that the one decision that matters — how much gain to apply — is made with the facts on screen.

What Is 89 dB in MP3Gain? Target Volume, Explained

89 dB is MP3Gain’s default “Target Normal Volume” — the reference loudness every track is adjusted toward. It comes from ReplayGain, the system MP3Gain implements: loudness is measured against a reference defined as playback at 89 dB SPL (sound pressure level) on a calibrated system. It is a shared yardstick, not a promise about how loud your speakers will be. Because most modern music is mastered louder than this reference, MP3Gain turns most tracks down to reach it — which is why a freshly processed library often sounds quieter until you turn your volume control up.

What the number actually refers to

The 89 dB is not measured in your room, and MP3Gain never knows how loud your speakers actually play. The number is a reference point inside the math. ReplayGain borrowed its calibration from cinema sound: the film industry (SMPTE) defines a standard test signal — pink noise at −20 dB relative to full scale — as playing back at 83 dB SPL on a calibrated system. ReplayGain’s original 2001 proposal used that reference, and implementations soon settled on a reference 6 dB higher, equivalent to pink noise at −14 dBFS: 89 dB SPL. That is the 89 you see in MP3Gain, and in essentially every other ReplayGain tool, which is what makes their results interchangeable.

When MP3Gain’s analysis shows a track “volume” of 94.2 dB, it means: this track’s perceived loudness sits 5.2 dB above the 89 dB reference, so a gain of about −5.2 dB (rounded to a 1.5 dB step) will bring it to target. A track showing 84 dB needs roughly +5 dB. The target is simply the fixed point everyone measures from.

Why everything sounds quieter afterwards

Two decades of the “loudness war” left most commercial masters far hotter than 89 dB on the ReplayGain scale — heavily compressed pop and rock tracks commonly analyze in the mid-to-high 90s. Bringing a whole library to a common 89 dB therefore means most files are attenuated, some by 8–10 dB. Your library is not damaged and nothing was lost: the files now agree with each other, and your amplifier’s volume knob has plenty of range to give the level back. What you gained is that the knob can now stay in one place.

There is one genuine exception to be aware of. Quiet, dynamic recordings — classical, acoustic, older jazz — may analyze below 89 dB and need a boost. If boosting would push their loudest peaks into clipping, MP3Gain’s “Don’t clip” option holds them below target instead. Those albums legitimately end up a little quieter than the rest, by design; the settings guide explains the option in context.

Can I set 92 or 95 dB instead?

Yes — the target is just a number in the “Target Normal Volume” field, and nothing stops you typing 92, 95, or any other value. Some listeners do, because they want the library to sit louder. But understand what the extra dB cost:

• Headroom disappears. A track can only be raised until its loudest peak hits the maximum the format can store. The higher the target, the more tracks hit that ceiling — and either clip (distort) or, with “Don’t clip” enabled, stop short of the target anyway.
• Loud tracks can’t get louder. A master already analyzing at 99 dB gains nothing from a 95 dB target; it is already above it. Raising the target mostly drags the quiet material up toward the ceiling, which is exactly where clipping lives.
• You leave the shared standard. 89 dB is what other ReplayGain tools, players, and two decades of forum advice assume. A private target makes your numbers incomparable with anyone else’s.

The honest summary: a higher target buys a few dB of level for quiet tracks and pays for it in clipping risk. 89 dB became the default because it leaves enough headroom for almost everything to reach it cleanly.

Is 89 dB the same as the −14 LUFS streaming target?

No — they are different measurements that happen to live in similar territory. 89 dB is a relative ReplayGain reference (how far a track sits from the shared reference point), while LUFS is an absolute loudness scale defined by the ITU-R BS.1770 standard, where streaming services publish targets like −14 LUFS. The two numbers for the same song are not interchangeable, and converting between them is approximate. The ReplayGain vs LUFS comparison lays out the three measurement systems side by side.

Frequently asked questions

Does processing at 89 dB reduce sound quality?

No. MP3Gain changes only the gain value stored in each MP3 frame — it never re-encodes the audio — and the change is fully reversible. Turning files down to 89 dB costs no quality at all; you simply use a bit more of your volume control.

One album is still quieter than the rest after processing. Why?

Usually one of two reasons: you used Album Gain, which deliberately preserves the album’s internal quiet tracks; or the album is very dynamic and the “Don’t clip” option limited its boost. Both are the program working as intended, not a failed analysis.

What target should I use for audiobooks and podcasts?

89 dB works fine and keeps speech consistent from episode to episode. Speech has a lower crest factor than music, so clipping is rarely an issue; consistency between episodes matters more than the exact number.

If I re-analyze with a different target later, do I start over?

No. MP3Gain’s changes are reversible and the analysis is stored in the file’s tag. You can undo the gain and re-apply at a new target without touching the audio — one more reason experimenting with 89 first is the low-risk option.

Track Gain vs Album Gain: What’s the Difference and Which Should You Use?

Track Gain adjusts every song independently so that each one matches MP3Gain’s target volume (89 dB by default) on its own. Album Gain analyzes a whole album, works out a single adjustment for the group, and applies that same adjustment to every track — so the quiet songs on the album stay quiet relative to the loud ones. Use Track Gain for shuffled, mixed listening; use Album Gain when you play albums in order, especially classical music, live recordings, and concept albums where the volume differences between tracks are part of the work.

The difference in one table

Both modes come from the ReplayGain system, where they were originally nicknamed “Radio Gain” (every song equal, like a radio station) and “Audiophile Gain” (the album preserved as the artist sequenced it). MP3Gain simply gives them plainer names.

What Track Gain actually does

Run Track Analysis and MP3Gain reports, for each file, how far its perceived loudness sits from the target volume. Apply Track Gain and each file is corrected by exactly that amount: a quiet rip from a 1980s CD might come up by 6 dB while a loud modern master is pulled down by 8 dB. Afterwards, any song can follow any other — a ballad after a metal track — without a lunge for the volume knob. That is why Track Gain is the right default for the way most people listen most of the time: shuffled libraries, workout playlists, car USB sticks, and folders of unrelated singles.

The cost is that Track Gain deliberately erases intended contrasts between songs. If an album opens with a whispered intro that is meant to be quiet before the first full track lands, Track Gain will lift that intro to full target loudness and the moment is gone.

What Album Gain actually does

Album Analysis treats the selected files as a single body of music. It measures the loudness of the whole set, calculates one correction that brings the album as a whole to the target, and applies that identical correction to every track. A track that was 4 dB quieter than its neighbour is still 4 dB quieter afterwards — the entire album simply sits at the right overall level next to the rest of your library.

This is the only correct choice for music whose dynamics span tracks: classical works (a hushed adagio movement should not be pumped up to match the finale), live albums, musicals, and any record sequenced as a continuous listen. It also protects gapless albums, where one track flows into the next.

Decision table: which one for your listening?

The mistake to avoid: Album Gain on a random folder

Album Gain is only meaningful when the selected files genuinely form one album. If you select your entire mixed library and click Album Gain, MP3Gain will faithfully compute one shared adjustment for thousands of unrelated songs — which changes almost nothing per song and leaves your loudness problem exactly where it was. The mirror-image mistake is applying Track Gain to a classical album and wondering why the quiet movement now blasts. When in doubt, think about how you will listen, not how the files are stored. The button-by-button guide shows which of MP3Gain’s four Analysis/Gain buttons corresponds to each mode, and the step-by-step tutorial walks a full library through the process.

One more reassurance: whichever you choose, nothing is permanent. MP3Gain stores its analysis and undo data in the file’s tag, so you can undo an Album Gain pass next week and redo the same files with Track Gain if your listening habits change. The two modes are strategies, not commitments.

Frequently asked questions

Can I apply both Track Gain and Album Gain?

Applying one after the other is pointless: the second application overwrites the effect of the first, because both write the file’s gain. Pick the mode that matches how you listen. You can always undo and switch — the change is fully reversible.

Which mode is better for shuffle play?

Track Gain. In shuffle, every song must match the target on its own, which is exactly what Track Gain enforces. Album Gain would leave quiet album tracks quiet even when they land next to loud singles.

Does Album Gain change the order or the gaps between tracks?

No. It changes only each file’s gain value, by the same amount for the whole album. Track order, gaps, and the audio itself are untouched — the adjustment is lossless and reversible.

My album has one very loud track. Will Album Gain still work?

Yes, but the loud track dominates the shared calculation, and if you have the “Don’t clip” option on, its peaks can limit how far the whole album is raised. That is correct behaviour: the album keeps its shape, even if it ends up slightly under the target.

MP3 Gain (MP3Gain): The Free MP3 Volume Normalizer, Explained

Whether you search for it as “mp3 gain,” “mp3gain,” or “mp3gain software,” it is one program: MP3Gain, a free tool that makes all your MP3 files play at the same volume — without re-encoding them and without losing quality. This page is the complete overview: who made it, how it works, what it cannot do, and where the real download lives.

What MP3Gain is

MP3Gain is a desktop program for Windows, written by Glen Sawyer and released as free, open-source software under the LGPL 2.1+. Its official home is the MP3Gain project on SourceForge (mp3gain.sourceforge.net), and the final stable release of the Windows program is version 1.2.5. It solves one problem completely: a music library where every track plays at a different loudness, so you ride the volume knob from song to song. Load files or a whole folder, analyze them, apply the gain — done, in bulk.

Two facts about its status are worth stating plainly, because download sites rarely do. The project has not published news since 2018, so 1.2.5 is not “the latest of many recent updates” — it is the finished program (the version guide explains the 1.3.x/1.5.2 number confusion). And this website, mp3gain.org, is an unofficial community resource: we document, troubleshoot, and mirror the software, but we did not write it and we are not affiliated with its author.

How it works: ReplayGain without re-encoding

MP3Gain implements the ReplayGain algorithm. It analyzes how loud each track actually sounds to human ears — not just its peak sample — and compares it against a target volume, by default 89.0 dB. Then comes the part that made the program famous: instead of decoding the MP3, changing the audio, and re-encoding it (which would cost quality), MP3Gain adjusts the gain value stored inside each MP3 frame, in steps of 1.5 dB. The audio data itself is untouched, so the process is lossless and fully reversible — MP3Gain writes undo information into a tag in the file, and you can roll any change back exactly.

• Track Gain — every song is brought to the same target volume; best for mixed playlists and shuffling.
• Album Gain — a whole album is adjusted together, preserving the intended volume differences between its tracks; best for albums meant to be heard as a work.
• Clipping protection — if raising a track to the target would push it into distortion, MP3Gain reports it and can hold the gain back instead.

What MP3Gain cannot do

Honest boundaries matter more than feature lists. MP3Gain works on MP3 files only — not M4A/AAC (that is the separate AACGain fork’s job), not FLAC, not WAV. It is a Windows program: there is no official Mac version (your real options are in our MP3Gain for Mac guide), and Linux users run the backend through front-ends. It is also not an audio editor: it will not trim silence, remove noise, fade tracks, or convert formats. When your problem goes past volume, that is a different tool’s job — the companion section on our download page points to the right ones. For the format-by-format map — which formats MP3Gain handles natively, which need a sibling tool like AACGain, and which only support tag-based leveling — see What Formats Does MP3Gain Support?

Getting it, safely

The real program is free — no trial, no key, and no “Pro” edition exists, whatever lookalike products claim (see MP3Gain Pro, explained and how to verify the real download). Get it from the official SourceForge project, or from our download page where the official files sit next to a clearly labelled mirror. Prefer not to install anything? The same 1.2.5 ships as an official no-install ZIP, covered in MP3Gain Portable. One modern-Windows warning: on Windows 11 the program’s legacy runtime components can trigger Runtime Error 75 or a missing MSCOMCTL.OCX message — annoying, well understood, and fixable in minutes with our step-by-step fix.

A short history, because it explains the present

ReplayGain, the algorithm inside MP3Gain, was proposed by David Robinson in 2001, when the MP3 era’s loudness chaos — every rip, encoder, and CD master at a different level — first became unbearable. Glen Sawyer’s implementation turned that proposal into the tool ordinary users actually adopted: free, graphical, batch-capable, and safe because it never re-encoded anything. Front-ends and forks followed — AACGain extended the method to AAC files, wxMP3gain and QMP3Gain carried the engine to other systems, and MP3Gain Express ported it to the Mac. The original’s development wound down as the problem it solved stabilized, with project news ending in 2018. Streaming services later built loudness normalization into themselves, but they only normalize inside their own apps; the files on your drive, your car USB stick, and your DJ laptop still belong to you — which is why a 2001 tool still answers a 2026 question.

The numbers worth remembering

• 89.0 dB — the default target volume, inherited from ReplayGain’s reference level.
• 1.5 dB — the fixed step size of a lossless MP3 gain change; finer steps would require re-encoding.
• 1.2.5 — the final stable version of the Windows program.
• LGPL 2.1+ — the license: free to use, free to share, source available.
• 0 — the quality lost when MP3Gain adjusts a file, and the price of the program itself.

“My player already has a normalize feature — do I still need MP3Gain?”

Sometimes not — and the honest answer depends on where you listen. Player-side features (Apple’s Sound Check, ReplayGain support in desktop players, streaming apps’ built-in loudness normalization) adjust playback using tags, and inside that one app they work well. Their limit is the border of the app: export the file, copy it to a car stereo, a cheap MP3 player, a DJ program, or a friend’s computer, and the adjustment stays behind, because the file itself never changed. MP3Gain’s file-level approach is the complement: the gain travels with the MP3 everywhere, at the cost of being MP3-only and of doing the work once, up front. Libraries that live in one modern app can skip it; libraries that live on drives, sticks, and mixed devices are exactly what it was built for. Plenty of listeners run both — tags for the home player, file-level gain for everything else — and the two do not conflict.

MP3Gain Pro: What It Is — and Why It Isn’t the Official MP3Gain

If you have seen “MP3Gain Pro” for sale and wondered whether you need it: you don’t, because it is not what the name suggests. There is no Pro edition of MP3Gain. The real MP3Gain is a single, free, open-source program — and products sold under “Pro” versions of its name are separate commercial software from unrelated companies that borrowed the name.

The real MP3Gain, in one paragraph

MP3Gain was written by Glen Sawyer and released as free software under the LGPL 2.1+. Its official home is the MP3Gain project on SourceForge (mp3gain.sourceforge.net). The final stable release of the Windows program is version 1.2.5. It has never had a paid tier, a license key, an activation system, or a “Pro” upgrade — in over two decades, every feature has always been in the one free download. Our MP3Gain overview covers what it does and how it works.

So what is “MP3Gain Pro”?

Over the years, third-party publishers have released their own audio tools under names built on MP3Gain’s reputation — “MP3Gain Pro” and year-stamped variants such as “Mp3Gain 2019” appear in software uninstall databases, published by companies that are not Glen Sawyer and not connected to the SourceForge project. These are independent commercial products with their own code, their own pricing, and no relationship to the original. Some may work as basic volume tools; that is beside the point. The point is what they are not: they are not newer, not official, and not an upgrade path for the free program — because there is nothing to upgrade. Everything the real MP3Gain does is already in the free 1.2.5.

How to tell them apart in ten seconds

One rule of thumb covers nearly every case: if it asks for money, it is not MP3Gain. Our safety guide has the full verification checklist, and the version guide explains why 1.2.5 — not a higher number — is the real “latest.”

“I already paid for MP3Gain Pro — what now?”

First, don’t panic: a lookalike product is not automatically malware, it is simply not the software you thought you were buying. Check whether it does what you need; if it does, the money question is between you and that vendor’s refund policy. But know that you never needed to pay to normalize MP3 volume losslessly — the original does it free, including batch processing, Track and Album Gain, and full undo. You can download the genuine 1.2.5 (official SourceForge files, plus our labelled mirror) and compare for yourself. If what you actually want is more than volume — editing, noise reduction, format conversion — that is a legitimate reason to buy software, just buy it under its real name: our download page’s companion section points to established editors for exactly that.

Why does this confusion persist?

Because the original project stopped releasing news in 2018, leaving a vacuum that name-borrowers happily filled, and because “Pro” is a persuasive word. It is also why we write pages like this one: a dormant open-source project cannot defend its own name, so its community has to. The short version to remember and repeat: MP3Gain is free, version 1.2.5, by Glen Sawyer, on SourceForge. Anything else wearing its name is something else.

“But the Pro product I found actually works — does it matter?”

It might be perfectly functional software. Name-borrowing is a marketing sin, not proof of bad code, and we are not claiming every product with “Pro” in its name is a scam. What matters is the decision you make with correct information: you would be buying an unrelated company’s editor or normalizer — not upgrading, unlocking, or supporting MP3Gain. Judge such a product the way you would any unknown audio tool: on its own publisher’s reputation, its own reviews, and whether it does something the free original genuinely does not. Often the honest comparison ends quickly, because the task that sent you searching — making MP3s play at one volume, losslessly, in bulk — is precisely the task the free 1.2.5 already performs.

The wider family of borrowed names

“Pro” is not the only costume. Year-stamped editions (“MP3Gain 2019” and similar) imply annual official releases that never happened; “2026 edition” listings recycle the same implication with a current date; and some portals wrap the genuine free installer in their own paid “premium download” flow, charging for bandwidth rather than software. The pattern to recognize is any suggestion that the real MP3Gain improved, expanded, or went commercial after 1.2.5. It did not. It stayed free, finished, and exactly where its author left it — which is why a community site, rather than a vendor, is the one explaining all this.

Three checks before any money changes hands

1. Publisher check: the official program’s author is Glen Sawyer and its home is a SourceForge project page, not a storefront. A checkout page is already your answer.
2. Version check: if the sales page celebrates a version above 1.2.5, a year edition, or a “new 2026 release” of MP3Gain itself, it is describing a different product — our version guide shows what the real numbers are.
3. Need check: write down the exact job you are paying for. If the job is “make my MP3s one volume, losslessly,” the free original does it. Paying is rational only for jobs outside that sentence — editing, effects, conversion — and then the seller should be a known editor under its own name, not a borrowed one.

None of this requires suspicion of every vendor on earth. It requires only that the word “Pro” stop doing the thinking for you.

Is MP3Gain Safe? How to Verify the Real Download

Yes — MP3Gain itself is safe. It is free, open-source software (LGPL 2.1+) written by Glen Sawyer and distributed through SourceForge for over two decades, with no adware and no account, activation, or payment of any kind. The real risk is not the program; it is the crowd of download sites and lookalike products trading on its name. This guide shows you how to verify that the file in front of you is the genuine one.

The 30-second verification checklist

• Source: the trail leads back to the official project — mp3gain.sourceforge.net or the mp3gain project on SourceForge. Mirrors (including ours) should say they are mirrors and link back to it.
• File name: the stable installer is mp3gain-win-full-1_2_5.exe; the no-install build is mp3gain-win-1_2_5.zip. A differently named “setup” file is a repack by someone — judge it accordingly.
• Version: 1.2.5 is the final stable release. Anything calling itself a newer official version, a “2026 edition,” or an upgrade is not official — see the version guide.
• Price: zero. The moment a page asks for payment, a license key, or a “Pro” upgrade to unlock MP3Gain, you are no longer dealing with MP3Gain — see what “MP3Gain Pro” really is.
• Behavior: the real program works fully offline, shows no ads, and asks for nothing at install beyond the usual folder choice.

Red flags that mean “close the tab”

A paywall or “Pro” tier. Several unrelated commercial products have been sold under names such as “MP3Gain Pro” and “Mp3Gain 2019.” They are not newer versions of Glen Sawyer’s program, they are not endorsed by him, and paying for one buys you nothing the free original does not do. A generic downloader stub — a tiny “setup” file that downloads the real program later, often with bundled offers — is another classic wrapper to avoid. And any site that will not tell you where its file came from, or that labels a cloud-drive mirror as an “official direct link,” is asking for trust it has not earned. On our own download page the Terabox files are labelled exactly what they are — a site mirror — next to the official SourceForge buttons, so you can choose knowingly.

Check any installer yourself in two minutes

You do not have to take any site’s word for it, including ours. After downloading, upload the file to VirusTotal (virustotal.com) — it is scanned by dozens of antivirus engines at once, and the genuine 1.2.5 installer has a long, well-known scan history because the same file has circulated unchanged for years. You can also compare the file’s hash (right-click → Properties → or Get-FileHash in PowerShell) against a hash published by the same official source you downloaded from. One caution: a hash only proves a file matches whatever the publisher shipped — it says nothing by itself about who the publisher is, which is why source verification comes first.

“My antivirus flagged MP3Gain — is it a virus?”

Almost certainly a false positive or a different file. Two honest caveats apply. First, MP3Gain’s installer is old, and some security tools treat any unsigned, rarely-downloaded legacy installer with suspicion. Second, if you downloaded from a random portal, the warning may be about the wrapper, not MP3Gain. The fix in both cases is the same: delete the questionable file, re-download the genuine 1.2.5 from the official project or a labelled mirror, and scan that. What you should not do is whitelist an unknown repack just because a page told you to.

Is it safe for your music files?

Yes, by design. MP3Gain does not decode and re-encode your MP3s; it adjusts the gain value stored in each MP3 frame (in 1.5 dB steps) and writes undo information into a tag, so any change can be reversed completely. Your files are never re-compressed and lose no quality. The full explanation of how MP3Gain works covers the mechanics, including the one format limit that matters: native MP3Gain handles MP3 only.

Frequently asked questions

Is MP3Gain a virus?

No. MP3Gain is open-source software by Glen Sawyer, distributed via SourceForge under the LGPL 2.1+. Antivirus warnings almost always concern third-party repacks or download wrappers, not the genuine 1.2.5 files.

Is MP3Gain free, really?

Yes — completely. There is no trial, no Pro tier, and no license key for the official program. Any page charging for “MP3Gain” is selling something else.

What is the official MP3Gain website?

The official home is the SourceForge project: mp3gain.sourceforge.net, with files hosted in the mp3gain project on sourceforge.net. This site (mp3gain.org) is an unofficial community resource that links to it.

Can MP3Gain damage my MP3 files?

No. It changes only the per-frame gain value and stores undo data in a tag, so changes are fully reversible and the audio is never re-encoded.

Full disclosure: this site’s own mirror

We hold ourselves to the checklist above, so here is exactly how our download page works. The main Windows installer button leads to a copy of our repack hosted on Terabox, and it is labelled on the page as a site mirror — not an official direct link — with the official SourceForge buttons beside it for anyone who prefers the untouched original. The source-code button goes to the official SourceForge project, full stop. If any of that ever changes, the labels change with it; a mirror that hides what it is has failed the only test that matters.

What about “MP3Gain online” tools?

A separate caution for the browser-based “online MP3 normalizers” that appear in the same searches: they are not MP3Gain at all, and most work by decoding and re-encoding your file on a server — the opposite of MP3Gain’s lossless, local, reversible method. They also ask you to upload your music to a stranger’s server. For a one-off file that may be an acceptable trade; as an “MP3Gain” substitute, it is a different product with different costs, and it should be chosen with open eyes.