MP3Gain Best Settings: Target Volume, Clipping and Tag Options

MP3Gain’s defaults are well chosen — most users should change nothing, ever. But three settings genuinely matter, and each is a trade-off rather than a “best value”: the Target “Normal” Volume, the don’t-clip protection, and the tag options. This page explains what each one does, what the defaults protect you from, and the specific situations where deviating actually makes sense. If you have not run the program yet, the beginner’s guide covers the basic loop first.

Setting 1: Target “Normal” Volume — keep 89.0 dB

The target is the loudness every file is adjusted toward, and 89.0 dB is not an arbitrary default: it is the reference level of the ReplayGain system itself, chosen with headroom in mind. A great deal of music — especially older and more dynamic recordings — sits well below the digital maximum. A target of 89 dB leaves room to raise those files substantially before any of them run out of headroom and clip.

Why not louder? Set 93 or 95 dB and two things happen. Loud modern files, mastered with peaks already at the ceiling, cannot be raised at all without distortion — MP3Gain flags them for clipping and, with protection on, simply leaves them below your target, defeating the point. And quiet files that can be raised get pushed closer to their peaks. You end up with a library that is nominally “louder” but less consistent — the opposite of the goal. Your player has a volume knob for absolute loudness; the target’s job is consistency.

When a different target is defensible:

• A slightly lower target (87–88 dB) for a library of very dynamic material — classical, live recordings — where you would rather every file fit without clipping compromises.
• Whatever target you choose, choose it once. Consistency across the whole library is what makes the library feel level. Files normalized at 89 and files normalized at 92 will clash by exactly 3 dB forever. If you change target, the clean move is to re-run the affected folders — or undo and start them fresh.

Setting 2: “Don’t clip when doing Track Gain” — leave it on

Clipping is what happens when audio is pushed past the maximum level the format can represent: the tops of waveforms are cut off, and the result is audible crackle and harshness baked permanently into the sound. When MP3Gain’s analysis says a file would clip if raised fully to the target, this option caps that file’s gain at the highest level that stays clean. The file ends up a little quieter than the target — typically by a decibel or two — and intact.

Turning the option off does not make the warning go away; it makes MP3Gain apply the full gain anyway and accept the distortion. There is no listening scenario where that trade is worth it for a whole library. The single legitimate exception is a deliberate, one-file experiment where you will listen to the result immediately and undo it if it crackles — and even then, lowering the target for that file achieves nearly the same loudness without the damage.

Worth knowing: files that arrive already clipped from the original mastering cannot be un-clipped by any setting here. MP3Gain prevents new clipping; it does not repair old damage. A track that crackles at its original volume will crackle at 89 dB too, just more consistently.

Setting 3: Tag options — APE by default, and why

Under Options → Tags, MP3Gain offers three ways to store its analysis data:

The APE default surprises people occasionally: some tag editors show the APE fields prominently, and a few players have historically been confused by APE tags on MP3s. Those are display quirks, not damage — your title, artist, and album tags are untouched. Switch to ID3v2 only if you have a concrete tool in your chain that misbehaves, and if tags ever seem to vanish or duplicate, the troubleshooting guide for tags works through it.

Already processed files with different settings?

This page would be incomplete without the rescue case: you processed half your library last year at one target, some folders with a different tag option, and you are not sure what state anything is in. Do not start over blindly. Re-add a folder and read the columns — MP3Gain shows the stored analysis, which tells you the level each file currently sits at. If a folder’s files are uniformly a few decibels off your chosen target, simply re-applying gain at the correct target brings them onto the standard, because gain is calculated from the measured current volume, not from what you did last time. If a folder’s history is genuinely murky — mixed modes, borrowed files, tag experiments — the clean reset is to undo its changes back to the original levels and process it once, properly, with the settings below. Either way, from today forward every new batch uses identical settings and gets a line in the log, as the batch routine prescribes — a library converges to consistency one verified folder at a time.

Recommended settings, by library

Notice how boring that table is. That is the point: MP3Gain’s settings reward leaving them alone. Set them once, process everything the same way (in batches, with a log, if the library is big), and the consistency you hear afterward is the settings discipline paying off. Something misbehaving anyway? The troubleshooting hub separates settings problems from installation problems.