iTunes Sound Check vs MP3Gain: Tag-Based vs File-Based Volume Fixes

Both promise the same thing — no more lunging for the volume knob between songs — but they are built on opposite mechanics, and using them together on the same library is a classic way to make things worse. Sound Check stores a volume adjustment in each file’s metadata and lets Apple’s software apply it during playback. MP3Gain rewrites the gain fields inside the MP3 itself, so every player on earth plays it at the corrected level. Which one you should use depends entirely on where your listening happens.

How Sound Check actually works

When you enable Sound Check in iTunes or the Apple Music app, the software analyzes each track once and writes the result into the file’s tags — in MP3, AAC, AIFF, and Apple Lossless files this is the iTunNORM value. The audio data itself is not modified in any way. At playback, Apple software reads the stored adjustment and turns the track up or down to what it calculated as the common level. Turn Sound Check off, use a different player, or copy the file to a device that doesn’t speak Apple’s metadata, and the adjustment simply doesn’t exist — the file plays at its original volume everywhere else.

Two limitations follow from that design. First, Sound Check is track-by-track only: there is no album mode, so a quiet intro track gets leveled as aggressively as a single, dissolving the loudness relationships an album was mastered with. Second, Apple’s analysis is its own, simpler loudness estimate — long criticized by audio communities as cruder than ReplayGain, particularly on very dynamic material. The leveling you get is convenient, automatic, and entirely rented from Apple’s ecosystem rather than owned by your files.

How MP3Gain differs, in one table

The file-level mechanism is the same one examined in Is MP3Gain Lossless? — decoders have always applied the frame gain field as part of playback, so no cooperation from the player is required.

The trap: never run both systems on the same files

Here is the failure mode that fills forum threads. A user levels their MP3s with MP3Gain, then plays them in iTunes with Sound Check still on. Sound Check now applies its own stored adjustment on top of audio that was already corrected — tracks end up double-adjusted, some too quiet, some oddly loud, and the user concludes one of the tools is broken. Neither is; they simply stacked. Worse, the stored iTunNORM values were computed from the files’ original loudness, so after MP3Gain changes the audio they no longer describe the files at all until the library is re-analyzed. The rule is simple: pick one system per library. If you process files with MP3Gain, leave Sound Check off for them. If your listening is 100% inside Apple Music and iTunes, Sound Check alone is the zero-effort option and MP3Gain adds nothing — Apple devices will ignore your frame gains’ intent only in the sense that they don’t need them, since playback there is already leveled by the tag system. The moment files leave that garden — a car USB stick, a DJ laptop, an Android phone — file-based leveling is the only kind that survives the trip.

Checking which system your library is actually using

Untangling a mixed library starts with looking, not processing. In iTunes or the Music app, selecting a track and opening its info window shows the Sound Check adjustment Apple computed — a plain decibel figure on the file’s summary — which confirms the file carries an iTunNORM value and tells you how large a correction Apple thinks it needs. A file that was leveled with MP3Gain but still shows a hefty Sound Check adjustment is a file the two systems will fight over. The clean-up procedure is boring by design: decide the winning system for that library, then neutralize the other. To retire Sound Check, simply switch it off in playback settings on the computer and on each device — the tags become inert weight, harmless if ignored. To retire MP3Gain’s changes instead, use its undo (the gain information stored in the file makes reversal exact, as the lossless explainer covers) and let Apple’s analysis stand. What not to do is “fix” the fight by processing a second time with the other tool: whichever ran second computed its values from files the first had already changed, and the result pleases neither system.

One more practical caveat for the Apple-only household: the tag values travel with the files during sync, but the Sound Check setting does not — it has to be switched on in the playback preferences of the computer and separately on each iPhone, iPad, or iPod that plays the library. A library can be perfectly tagged and still play unleveled on the one device where the toggle was never touched, which is the most common reason Sound Check “doesn’t work” in an otherwise all-Apple setup.

The middle path for Apple loyalists: iVolume

One tool deserves mention for listeners who stay inside Apple’s world but distrust Sound Check’s math: iVolume, a long-running commercial utility from mani.de, whose site and user guide are still online. iVolume analyzes your Music/iTunes library with the ReplayGain algorithm — the same measurement MP3Gain uses — and then writes the results into the very same Sound Check field Apple uses, replacing Apple’s rougher values with better ones. You keep the tag-based convenience (nothing in the audio changes, Sound Check stays the playback mechanism, and it must remain switched on for the effect to appear) while upgrading the analysis underneath it. It is the right answer to a narrow question — “Sound Check, but accurate” — and the wrong one if your files ever need to carry their leveling outside Apple’s apps.

For everything outside that garden, the format support overview maps the file-level and tag-based options for MP3, AAC, FLAC, WAV, OGG and more.