Why Songs Sound Louder or Quieter on Your Phone — and How to Fix It

On your computer the library sounded fine. On your phone, one track whispers and the next one blasts. Two different things can cause that — the files themselves genuinely differ, and your phone’s player may (or may not) be compensating — and the right fix depends on which. This guide separates the two causes and walks through both fixes.

Cause 1: the files really are uneven

MP3s ripped, bought, and downloaded across the years were mastered to wildly different levels. Nothing about copying a file to a phone changes that — the phone faithfully plays a quiet file quietly. If your desktop player has been quietly compensating all along (many do, via ReplayGain), the phone is simply the first place you have heard your library unprotected. The unevenness was always there; the phone exposed it.

Cause 2: player normalization — present, absent, or app-dependent

Unlike desktop players, phones have no single normalization standard:

• iPhone: the Music app has Sound Check (Settings → Music → Sound Check). When on, it evens out playback using volume information stored with your tracks. If your MP3s were synced from a computer library that never calculated that information, Sound Check may have little to work with on exactly the files that need it most.
• Android: there is no system-wide equivalent. Whether local files get levelled depends entirely on the player app — full-featured players such as Poweramp read ReplayGain tags and offer their own normalization; many bundled players do nothing at all.
• Streaming apps normalize their own catalogues on their own terms, but that says nothing about the local MP3 files sitting next to them in a different app.

So route one is: try the switch your player already has. If Sound Check or your Android player’s ReplayGain support covers your library, you may be done in a minute. The catch is coverage — tag-based systems only level files whose tags carry the right data, and only inside players that read them.

Route 2: fix the files themselves with MP3Gain

The heavy-duty fix is to make the files level before they ever reach the phone. MP3Gain adjusts the gain inside each MP3 frame — the audio data itself — rather than annotating tags. A file fixed this way plays at the right volume in every app on the phone: the stock player, a third-party player, the car via Bluetooth, everything. No tag support required, no per-app settings, no exceptions for files synced years ago.

The process is the standard one: on your PC, load the library (or the phone-bound subset), run Track Analysis, apply Track Gain at the default 89.0 dB target, then copy the processed files to the phone. Our step-by-step guide covers the workflow, and the batch guide covers doing a whole library safely.

First, a two-minute diagnosis

Before changing anything, pin down which cause you have. Pick the pair of songs that clash worst and play them in your desktop player with any normalization it has switched off. If they clash there too, the files are uneven — cause 1, and route 2 below is your fix. If they play level on the desktop but clash on the phone, your desktop player was compensating via tags and the phone is not — cause 2, and you can choose either route: enable the phone-side equivalent if your app has one, or fix the files so no compensation is needed anywhere. Two more tells: if every song from one album is uniformly offset but internally consistent, that album was probably mastered (or previously gained) to a different level as a unit; and if the jumps only happen between apps — music fine, a different app loud — that is per-app output difference, not your files at all.

Getting processed files onto the phone

Process first, copy second: the phone should receive finished files. On Android that is usually a USB cable or a file-manager copy into the Music folder, after which most players rescan automatically (if yours does not, its settings will have a rescan or refresh option). On iPhone, sync through Finder or the Apple Music app on your computer as you normally would — the files transfer as they are, gain included. Either way, afterwards make sure the phone is not still holding the old copies in a second location: a library with the original Downloads folder and the new Music folder side by side will happily play you one of each, and the “fix that didn’t work” turns out to be a duplicate. Delete or overwrite the originals once the processed set checks out — after confirming on the phone itself, with your worst pair of songs, that the clash is gone.

One trap: don’t double-process

If you fix the files with MP3Gain and leave your phone player’s normalization switched on, the two systems stack. The player reads its tag data and adjusts files that are already level — at best redundant, at worst it re-introduces unevenness between files whose tags are inconsistent. Pick one layer: file-level gain with MP3Gain (player normalization off), or tag-based leveling (files untouched). For a mixed, long-lived MP3 library, the file-level route is the one that keeps working when you change phones or apps.

Which route should you pick?

That last row is the honest boundary of this whole topic: MP3Gain works on MP3 files you possess. Cached or DRM-protected streaming audio is not editable, and no desktop tool changes that — the streaming service’s normalization toggle is the only lever there. For everything that is actually yours, though, the fix is permanent, portable, and — as with everything MP3Gain does — reversible if you ever change your mind. Driving with the same library? The car USB guide covers the head-unit side.

How to Normalize MP3s for Your Car Stereo (USB)

The car is where uneven MP3 volume is most annoying — and most dangerous to fix by hand, one knob-grab per song at 70 mph. It is also where the usual computer-side tricks quietly fail. This guide explains why tag-based normalization does nothing in most cars, and how to prepare a USB stick whose files are level by construction.

Why your car’s volume jumps around

Most in-car head units — factory and aftermarket alike — are simple players. They decode the MP3 audio and play it at the level stored in the file. What they almost never do is read ReplayGain tags: the loudness notes that desktop tools like foobar2000 write into files and that smart players use to even things out. Normalizing a library “with tags” on your PC and copying it to a USB stick therefore changes nothing in the car. The tags ride along; the head unit ignores them; the quiet songs stay quiet.

Some newer head units bury a “volume leveling” or similarly named option in their audio settings, but implementations vary wildly and many apply only to radio or Bluetooth sources, not USB files. You cannot rely on it — and you do not need to.

The fix that works: change the files, not the tags

MP3Gain takes the other route. Instead of annotating files, it adjusts the gain value inside each MP3 frame — the actual playback level of the audio data. Every decoder on Earth applies frame gain, including the cheapest factory head unit, because it is not metadata: it is the music itself. A stick of MP3Gain-processed files plays level in the car, on a phone, on a smart speaker, everywhere, with no support required from the player. That is the entire reason this workflow exists.

The workflow

1. Work on a copy, not the stick. Copy the music you want in the car into a working folder on your PC, and keep your master library untouched. If the stick’s files are your only copies, back them up first — the batch safety routine applies at any scale.
2. Load the folder into MP3Gain and run Track Analysis. For driving, Track mode is the right choice almost always: you shuffle singles and playlists, not album sequences, and every song should stand at the same level on its own. The full workflow guide walks through the clicks.
3. Keep the target at 89.0 dB and clipping protection on. Road and engine noise eat quiet detail, which tempts people to crank the target up — resist it. A much louder target mostly buys clipping on modern tracks; your head unit’s own volume knob adds overall loudness without distortion, and 89 dB files turned up at the amp sound better than 95 dB files clipping at the source. The settings guide has the reasoning.
4. Apply Track Gain, then copy the processed files to the stick. Copy the files, not the working folder’s leftovers, and eject the stick cleanly.
5. Test in the actual car. Play the previously quietest and loudest songs back to back, engine on. That thirty-second check beats any amount of desktop verification.

Real-world car USB pitfalls (that are not volume)

• Format the stick FAT32. It is the one filesystem virtually every head unit reads. A stick formatted NTFS or exFAT may simply not appear — a formatting problem, not a music problem.
• Mind folder depth and file counts. Many units cap how many folders or files they will index, and deep nesting (Artist/Album/Disc/…) can push tracks past the limit. For car sticks, a shallow structure — one folder per artist or even per playlist — is more reliable than your library’s full hierarchy.
• Playback order surprises. Plenty of head units play files in the order they were written to the stick rather than by track-number tags. If order matters, copy files in the sequence you want, or accept shuffle as the car’s natural state.
• Odd filenames. Very long names and exotic characters trip up simpler units. If one specific track never appears, shorten its filename before suspecting the audio.
• A file that will not play at all is an encoding problem, not a volume problem — no gain tool fixes a file the decoder cannot read. Re-rip or re-download that track from its source instead.

Still uneven in the car? A four-point checklist

• Did the processed copies actually reach the stick? The classic failure: you normalized a working folder, then copied the original folder to the USB stick out of habit. Check one file: load it into MP3Gain at home — if its stored analysis is missing, the car is holding unprocessed files.
• Is the head unit’s own leveling fighting you? If your unit has a volume-leveling, “sound check”, or speed-dependent volume feature switched on, it may be re-adjusting already-level files based on guesses. With file-level gain done properly, switch the unit’s feature off and compare.
• Did an album sneak through on Album Gain? One record will sound internally varied — quiet intros, loud finales — while everything else sits level. That is Album Gain doing its job in the wrong place; re-run that folder with Track Gain.
• Is it only one source that sounds off? If USB files are level but radio or Bluetooth is not (or the reverse), the files are fine — each source has its own level in most head units, and many offer a per-source offset in the audio settings. Set it once and stop blaming the stick.

Phone in the car instead?

If your “car stereo” is really your phone through Bluetooth, CarPlay, or Android Auto, the head unit is just passing through what the phone sends — and the phone’s own player settings enter the picture. Fix the files the same way (file-level gain works there too), then check the phone side with our phone guide, which covers Sound Check, player normalization switches, and the double-processing trap to avoid when both are on.

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.

How to Undo MP3Gain Changes and Remove MP3Gain Tags

MP3Gain was designed so that nothing it does is permanent. Every gain change is written into the MP3 frames together with an undo record stored in the file’s tags, and that record lets you restore the original volume exactly — no backup required, as long as the record survives. This guide covers the undo itself, the separate question of removing MP3Gain’s tag data, and the one order of operations you must not get backwards.

What MP3Gain actually stored in your files

When MP3Gain applies gain, it does two things. First, it changes the gain value in every MP3 frame — that is the volume change itself. Second, it writes a small set of fields into the file’s tag (an APEv2 tag by default): the analysis results, the ReplayGain values, and a field called MP3GAIN_UNDO that records exactly how to reverse the frame changes, channel by channel. Undo is not an estimate or a re-normalization to some guessed level; it is the stored inverse of the change that was made, which is why the restored file matches the original.

This design has one dependency: the undo record lives in the tag. Anything that strips or rewrites the tag between the gain change and the undo — another tag editor, a library tool that “cleans” APE tags — can take the undo information with it. Keep that in mind before running tag-cleanup tools over a processed library.

The undo: step by step

1. Add the files back into MP3Gain. Use Add File(s) or Add Folder, exactly as you did originally. If the files still carry their MP3Gain tags, the columns populate with the stored analysis right away — confirmation that the undo record is present.
2. Select the files you want to restore. Click a row, or select the whole list to undo an entire folder or batch at once.
3. Choose Modify Gain → Undo Gain changes from the menu. MP3Gain reads each file’s undo record, reverses the frame gain changes, and reports the restored state in the list.
4. Verify. The Volume values should now read as they did before processing, and playing a track should match your memory of the original — because it is the original level again.

Undo works whether you applied Track Gain or Album Gain, and it works on one file or ten thousand. It is the same mechanism that makes experimentation safe in the first place: if a batch comes out wrong — wrong target, wrong mode — undo the folder and run it again properly, as described in the batch guide.

Removing MP3Gain’s tags is a different operation

Undo restores volume; it is not the same as removing the tag data MP3Gain wrote. You might want the tags gone if you are handing files to a strict workflow, moving to a different normalizer, or tidying a library for good. Three facts keep this safe:

• Deleting the tags does not change the volume. The gain lives in the audio frames, not the tag. Strip the tags from a gained file and it stays at its new volume — it just loses the ability to be undone and the record of what was done.
• Therefore: undo first, strip second. If you want files back at their original volume and free of MP3Gain data, the order is undo → then remove tags. Strip first and you have deleted your only map back.
• Use a tag editor for the removal. A tool like Mp3tag can display and remove the APE tag fields MP3Gain writes — the same inspection steps in our tags-not-working guide show where these fields live and how other tools can clash with them. Within MP3Gain itself, the Tags options (covered in best settings) can be set to “Ignore” so the program stops reading and writing tag data going forward — but that prevents future tags; it does not clean existing ones.

When undo can’t help

Three situations defeat the built-in undo, and all three have the same fallback:

• The tags were stripped or rewritten by another tool after processing. The undo record is gone, and with it the exact inverse. (The volume change itself is still in the frames — a known change can be countered manually with an opposite Constant Gain, but treat that as approximation, not restoration.)
• The files were re-encoded — converted to another format and back, or run through an editor that re-saves the audio. Frame-level history does not survive re-encoding.
• The files were processed by a different “MP3Gain” product. Name-alike tools that re-encode — the subject of our MP3Gain Pro clarification — do not write this undo record at all.

In each case the answer is the backup you made before processing. This is why the backup step appears in every workflow on this site, including the main normalization guide: undo covers mistakes, backups cover history.

Does undo restore the file exactly?

The audio, yes: undo applies the stored inverse change to the frames, returning them to their original gain values, and since MP3Gain never decoded or re-encoded anything, there is no generational loss to accumulate — gain up, gain down, and the sound data is where it started. Two honest footnotes. First, the file’s tag area may still contain MP3Gain’s fields afterwards; undo reverses the volume, it does not pretend the program was never there — removing those fields is the separate tag step described above. Second, undo restores the volume, not every byte of history: if another tool edited the files in between (retagged, trimmed, re-saved), undo cannot rewind that tool’s work. Within MP3Gain’s own changes, though, the round trip is exact — which is precisely what makes its workflow safe to experiment with in the main guide.

Leaving MP3Gain entirely?

If you are uninstalling the program as part of this cleanup, undo (or deliberately keep) your gain changes first, decide whether the tag data stays or goes, and only then remove the software — the full sequence is in our uninstall guide. Files keep whatever state you leave them in; no player needs MP3Gain installed to play them.

Track Analysis, Track Gain, Album Analysis, Album Gain: MP3Gain’s Four Buttons, Explained

New users stare at MP3Gain’s four operations and ask the same question: which one do I actually click? The short answer is that there are really two buttons — Analysis and Gain — and each has a pull-down menu with a Track mode and an Album mode. This page explains what each of the four does, mechanically, so you can click the right pair every time. For the full beginner walkthrough, start with how to use MP3Gain.

The pattern: analyze first, gain second

Every MP3Gain job is two passes over the same files:

• Analysis = measuring. MP3Gain decodes each file, measures how loud it sounds (the ReplayGain method), and writes the results into the columns. Analysis never modifies your audio.
• Gain = applying. MP3Gain takes the numbers from the analysis and rewrites the gain value in each MP3 frame. This is the only step that changes files — losslessly, and reversibly via the undo record it stores in the tags.

Track and Album are simply the two ways of grouping that work: per song, or per set. Combine the two passes with the two groupings and you get the famous four.

Track Analysis: measure each song on its own

Where: the Analysis button’s main click (its pull-down also offers Album Analysis and Clear Analysis).

Track Analysis measures every file independently and fills in two columns: the file’s current Volume and its Track Gain — the exact adjustment that would bring that one song to the Target “Normal” Volume (89.0 dB by default). It also flags any file that would clip if raised all the way. Run it on a mixed folder of downloads and you will see wildly different Track Gain values row by row: +8.5 for a quiet old rip, −6.0 for a loud modern master. That spread is your volume problem, made visible.

Album Analysis: measure the set as one album

Where: the Analysis button’s pull-down menu.

Album Analysis measures the same files but answers a different question: “if everything in the list is one album, how loud is the album as a whole?” It fills the Album Gain column with a single shared value — the adjustment that brings the album’s overall level to the target while leaving the differences between its tracks untouched. The quiet intro stays quieter than the finale, exactly as the artist sequenced it. The catch: Album Analysis believes everything in the list belongs together. Run it on a folder of unrelated singles and the “album” it computes is meaningless.

Track Gain: apply each song’s own correction

Where: the Gain button’s main click.

Track Gain applies every file’s individual Track Gain value. Each song lands on the target loudness regardless of its neighbours, which is precisely what you want for shuffle play, mixed playlists, DJ folders, and downloads accumulated from a dozen sources. Because the adjustment happens in the file’s frames — in 1.5 dB steps — the correction is as close to the calculated value as the MP3 format allows, and it travels with the file to every player.

Album Gain: apply one correction to the whole set

Where: the Gain button’s pull-down menu.

Album Gain applies the single Album Gain value to every file in the list — all of them up (or down) by the same amount. The album’s internal balance is preserved; only its overall level changes, like turning the volume knob once for the whole record. Use it for complete albums, classical recordings, and live sets. The Gain pull-down also hides a third option, Constant Gain, which applies a fixed dB change you type in yourself, ignoring analysis entirely — a specialist tool, mostly useful for manual corrections and for reversing a known change.

Which pair do I click?

Match the analysis to the gain you intend to apply — Album Gain needs Album Analysis numbers behind it, and Track Gain needs Track Analysis. If you analyzed one way and changed your mind, just run the other analysis; it costs a minute and overwrites nothing but figures.

The two classic misclicks

• “I clicked Analysis and nothing changed.” Correct — analysis is a measurement, not a fix. Nothing changes until a Gain button applies the numbers.
• “One song on the album is still quiet.” After Album Gain, that is by design: the album’s internal differences are preserved. If you truly want every song equally loud, that folder needed Track Gain instead — re-run it with Track Analysis and Track Gain, and see our undo guide if you want a clean slate first.

One last piece of the interface worth knowing: because MP3Gain stores its analysis in each file’s tags, reopening a processed folder shows the old numbers instantly. The buttons are how you work; the columns are how you check. Master those, and the program has no mysteries left — the remaining choices are about settings, not buttons.

The pull-down extras, for completeness

Two more entries live in those menus and are worth recognizing so they never surprise you. Clear Analysis (Analysis pull-down) wipes the calculated figures from the list — and from consideration for the next gain pass — without touching the audio; use it when you have changed the target volume and want a visibly fresh start. And the status line at the bottom of the window narrates every pass: which file is being measured, which is being written, and when the job is done. On a long batch it is your progress bar and your error log in one — if a file cannot be read or written, that is where MP3Gain says so, and the troubleshooting hub is where those messages lead.

How to Batch-Normalize Thousands of MP3s Safely

Normalizing a folder is a two-minute job. Normalizing 8,000 files is the same job multiplied by every way it can go wrong: one wrong setting, applied ten thousand times, while you are making coffee. This guide is the safety routine for big libraries — back up, pilot, work in batches, keep a log, and verify as you go — so the one-click part of MP3Gain never turns into a one-click disaster.

First, decide what “the library” means

Before loading a single file, settle the mode question, because it changes how you batch:

• Track Gain for a mixed library. If your collection is singles, downloads, and rips from many sources, Track Gain — every file independently to the same target — is the correct default, and you can safely process folders in any order.
• Album Gain only works album by album. Album mode treats everything in the list as one album and applies a single shared adjustment. Add your whole library at once and MP3Gain will dutifully treat 8,000 unrelated songs as one giant album. If you want Album Gain’s within-album dynamics preserved, the batch unit is the album folder — one album per run.

Unsure which pair of buttons does what? The four-buttons guide explains the mechanics; the step-by-step workflow covers a normal single-folder job.

Step 1: Back up the entire library before batch one

MP3Gain’s changes are reversible — it stores an undo record in every file it touches. So why insist on a backup? Because reversibility protects you from MP3Gain, not from everything else: a drive failure mid-job, a folder you did not mean to load, a target volume typed as 98 instead of 89. A pre-job copy of the library turns every scenario into an inconvenience instead of a loss.

The practical standard is one full copy on a different device than the originals: an external drive, a NAS, or cloud storage. A library you spent years building deserves the buy-once version of this insurance — our download page lists pCloud as one option for exactly that reason. Whatever you choose, make the copy before the first batch, and do not let your sync tool overwrite it with the processed files until the whole job is verified.

Step 2: Run a pilot batch

Pick one representative folder — a few dozen files spanning quiet old rips and loud modern ones. Run the full loop: analyze, apply, re-analyze, listen. Test the results where you actually listen: your phone, your car, your speakers. The pilot answers the only two questions that matter before scale: is 89.0 dB the right target for your ears and devices, and does anything in your chain misbehave with processed files? Two minutes here can save a re-run of ten thousand files.

Step 3: Work in batches, and keep a log

Process the library in slices you can verify — an artist at a time, a genre folder at a time, a few hundred files per session. After each batch, write one line in a plain text file or spreadsheet:

Thirty seconds per line, and it buys you three things: you always know what is done and what is not (no double-processing, no skipped folders), you can find the exact batch a problem track came from, and future-you can repeat the identical settings on new arrivals. Your log plus MP3Gain’s own records complement each other — re-adding a folder instantly shows its stored analysis in the columns, so the program itself can confirm which folders have been through the process.

Step 4: Let batches finish

Analysis is real work — every file is decoded and measured — so a few thousand files is a job you start and leave running, not one you watch. Keep the machine awake and plugged in, and resist tidying up “just one folder” in another program while a batch is mid-write. If you must stop, stop between batches; files already finished keep their changes and undo records, and your log tells you exactly where to resume.

Step 5: Spot-check, then roll back surgically if needed

After each batch, sample like an auditor: the quietest album, the loudest single, one track you know by heart. Play them where you listen most. Problems, when they happen, are almost always one of these:

• A folder sounds flat or uniform — it was probably Album material run through Track Gain, or vice versa. Re-do that folder the other way; applying a fresh analysis and gain pass is safe.
• One track distorts — it clipped. Re-run it with clipping protection on, or accept a slightly lower level for that file; the settings guide explains the trade-off.
• Everything in a batch is wrong — wrong target typed, wrong mode. Select the whole folder and undo the changes in one pass, then re-run it correctly. This is the moment the undo record earns its keep; the backup from step 1 is your second line if tags were damaged by another tool in between.

Only when the whole library passes spot-checks is the job done — and only then should the backup copy be refreshed to match, so your safety copy and your working library agree again.

Keeping it level: new music joins the routine

A normalized library starts drifting the day you add to it — new rips and downloads arrive at their original, unmatched levels. The cheap fix is to fold newcomers into the same routine instead of letting them accumulate: keep a small “inbox” folder for new arrivals, and once a month (or per shopping trip) run that folder through the identical settings — same mode, same 89.0 dB target — log one line, and file the files away. Because the target never changes, month fourteen’s arrivals land at exactly the loudness of month one’s. The libraries that stay level for years are not the ones processed by the most careful one-off marathon; they are the ones whose owners made the settings boring and the routine small.

The routine, on one card

1. Decide the mode: Track for mixed libraries, Album folder-by-folder.
2. Copy the entire library somewhere else. Verify the copy opens.
3. Pilot one folder. Listen on your real devices.
4. Batch by folder or artist. Log every batch: date, path, mode, target, file count.
5. Spot-check each batch. Undo or re-run the failures only.
6. When everything passes, refresh the backup to match the finished library.

How to Use MP3Gain: A Beginner’s Step-by-Step Guide

MP3Gain’s window looks like it survived from 2005 because it did — but everything a beginner needs is on that one screen. This guide tours the window control by control, then runs one complete job from adding files to checking the result. If you have not installed the program yet, start on the download page; if it refuses to install or open, the won’t-install guide and the troubleshooting hub will get you unstuck.

The main window, in 30 seconds

The window has four working parts:

• The file list fills most of the window. Every MP3 you load gets a row; every measurement MP3Gain makes gets a column.
• The Target “Normal” Volume field at the top holds the loudness you are aiming for — 89.0 dB by default.
• The buttons — Add File(s), Add Folder, Track Analysis, and Track Gain. The two right-hand buttons have small pull-down arrows that hide their Album and extra modes.
• The status area at the bottom reports what the program is doing while it works.

That is genuinely all of it. Now the workflow, one pass from empty window to finished files.

Step 1: Add your music

Click Add Folder and point MP3Gain at a music folder — it loads every MP3 inside, including subfolders. Click Add File(s) when you only want specific songs; the file picker also accepts M3U playlists if you keep your music organized that way. Or skip the buttons: dragging files and folders from Explorer straight into the window works as well.

Beginner advice: start with one album or one folder, not your whole collection. You can repeat the process as often as you like, and a small first run teaches you the whole loop in two minutes. (When you are ready for the full library, the batch guide adds the safety steps a big job deserves.)

Step 2: Learn to read the columns

Before you analyze anything, the list shows mostly names and empty columns. After analysis, each row carries the numbers that matter:

Two things surprise first-timers. The Volume numbers rarely match the “loudness” you would guess from a waveform, because ReplayGain models hearing rather than peaks. And adjustments always land on 1.5 dB steps, because that is the smallest step the MP3 format allows when gain is changed without re-encoding — a fraction of a decibel of rounding that no listener can detect.

Step 3: Set the target volume

Leave the Target “Normal” Volume at 89.0 dB for your first jobs — and probably forever. It is the reference level the whole ReplayGain system is calibrated around, and it leaves enough headroom for quiet songs to be raised without clipping. The dedicated settings guide covers the exceptions; beginners should change exactly nothing here.

Step 4: Click Track Analysis

Click Track Analysis. MP3Gain measures every file and fills in the columns. Analysis is read-only: it cannot harm, change, or move a single file. Notice the button’s pull-down arrow — it also offers Album Analysis (measure the set as one album) and Clear Analysis (wipe the numbers and start over). The four-buttons guide explains when each mode is the right one.

Read the results before going on. Files needing small corrections (±3 dB) are typical. A file needing +12 dB was mastered very quietly; a file flagged red for clipping will be handled gently in the next step rather than forced.

Step 5: Click Track Gain

Click Track Gain. Now MP3Gain does change files: it rewrites the gain value in each MP3 frame and stores its analysis plus an undo record in the file’s tags. The list updates as each file finishes, and the status area narrates progress. A folder of songs takes seconds; go and watch one row complete so you know what “done” looks like.

Changed your mind about a file? Select its row and remove it from the list before applying gain — removal from the list never touches the file on disk. Double-clicking a row plays the file in your default player, handy for checking a suspiciously quiet track before you commit to fixing it.

Step 6: Check the result

Click Track Analysis once more. The Volume column should now read 89.0 dB (or just under, for files that were held back to avoid clipping). Play the first and last songs in your player of choice. Then, if the destination is a specific device, test there: our guides for car stereos and phones cover what to check.

Four beginner mistakes to skip

• Analyzing but never applying. Analysis alone changes nothing — files only change when you click a Gain button.
• Album Gain on a random folder. Album mode treats everything in the list as one album. A “misc downloads” folder is not an album; use Track mode for mixed files.
• Processing the only copy. Changes are reversible, but work on a copy until the workflow is familiar — especially before big jobs.
• Chasing loudness with the target field. Setting 95 dB does not give you “better” normalization, just more clipping warnings. Consistency is the prize.

Frequently asked questions

Do I have to run analysis before applying gain?

Effectively, yes. The Gain buttons apply the values the analysis calculated. If a file already carries analysis data in its tags from an earlier session, MP3Gain can reuse it — which is why re-adding a processed folder shows numbers immediately — but for new files, analysis always comes first.

Does MP3Gain change my files’ names, folders, or tags?

It never renames or moves files. It does write its own analysis, gain, and undo information into the files’ tags (APEv2 by default) — that record is what makes changes reversible — but your title, artist, and album tags are left alone. If a player ever seems confused by those tags, our tags guide explains the fix.

Can I stop MP3Gain in the middle of a job?

You can close it between files safely; files already processed keep their changes and their undo records. Avoid killing the program at the exact moment a file is being written — let the current file finish, then close.

I applied gain and hate the result. Now what?

Use the undo: add the files again and choose Undo Gain changes from the Modify Gain menu. Every change MP3Gain made is reversed from the record stored in the tags. The undo guide walks through it, including how to remove the tag data afterwards if you want completely clean files.

How to Make All Your MP3s the Same Volume (Without Losing Quality)

Every MP3 collection has the same problem: one song whispers, the next one shouts. This guide walks through the complete fix with MP3Gain — back up, add your files, pick the right mode, set the 89 dB target, apply the gain, and verify the result. The process is lossless and reversible: MP3Gain never decodes or re-encodes your audio.

No Brasil? Leia este guia em português →

Why your MP3s are all at different volumes

MP3s come from decades of different sources: CD rips from the quiet 1980s, remasters from the loudness-war 2000s, downloads, recordings, files friends sent you. Each was mastered to a different level, and the MP3 format itself stores no rule that says how loud a file should play. Your player just plays each file at whatever level is baked into it — so you ride the volume knob forever.

Some players offer a “normalize” or “volume leveling” switch, but those features work by reading a loudness note stored in the file’s tags — and most players, car stereos, and cheap speakers ignore that note completely. The fix that works everywhere is to adjust the audio data itself, once, on your PC. That is exactly what MP3Gain does.

What “the same volume” actually means

MP3Gain does not make every file peak at the same maximum sample — that is peak normalization, and it still leaves quiet songs sounding quiet. Instead it uses the ReplayGain method: it analyzes how loud each file actually sounds to human ears and calculates the adjustment needed to bring it to a shared target loudness. Two files at the same ReplayGain level sound equally loud, even if their waveforms look different.

The adjustment itself is surgical. MP3Gain changes the gain value stored in every MP3 frame — the same value your decoder already applies when playing the file — in steps of 1.5 dB. It does not decode the audio and does not re-encode it, so there is no quality loss and no generation loss, ever. It also writes its analysis and an undo record into the file’s tags (APEv2 by default), which makes every change reversible. If you dislike the result, you can undo it completely.

Before you start

• Get the right program. MP3Gain 1.2.5 is the final stable release from the official project. Our download page lists the official SourceForge files and a clearly labelled mirror side by side, and this page explains how to verify what you downloaded. If the program will not install or open, work through the troubleshooting hub first.
• Work on MP3s. MP3Gain handles MP3 files. It does not process FLAC, M4A/AAC, or WAV — those need different tools, which our MP3Gain overview maps out.
• Back up first. The changes are reversible, but a backup is still step one of any library job. Copy the folder you are about to process to another drive before you touch it.

Step 1: Back up the folder you will process

Copy the music folder to an external drive, a second internal drive, or cloud storage. For a first run, do not start with your entire library — pick one folder of a few dozen songs. Once you trust the workflow, the same steps scale to thousands of files; for a whole-library job, follow the safer batch routine in our large-library guide.

Step 2: Add your files

Open MP3Gain and click Add Folder to load a whole folder (including its subfolders) or Add File(s) for individual tracks. Dragging files and folders straight into the window works too. The files appear as rows in the list; nothing has changed yet — MP3Gain never modifies a file until you explicitly apply gain.

Step 3: Set the target volume — 89.0 dB

At the top of the window sits the Target “Normal” Volume field, set to 89.0 dB by default. Leave it there. 89 dB is the ReplayGain reference level, and it is deliberately a few decibels below the loudest modern masters: that headroom is what lets quiet songs be turned up without distorting. Raising the target to 93 or 95 dB feels tempting, but loud files then have nowhere to go and MP3Gain will warn about clipping — the crackly distortion you get when audio is pushed past its maximum. Our settings guide explains the trade-offs in detail; the short version is that consistency, not maximum loudness, is the goal, and your player’s volume knob can always add the rest.

Step 4: Choose Track Gain or Album Gain

This is the one real decision in the process:

For a typical mixed library, Track Gain is the right choice. The four operations hide behind two buttons with pull-down menus — our button guide walks through exactly where each one lives.

Step 5: Run the analysis

Click Track Analysis (or choose Album Analysis from the pull-down if you picked Album mode). MP3Gain measures every file and fills in the list: each file’s current Volume, the Track Gain or Album Gain it proposes, and a clipping warning — shown in red — for any file that would distort if it were raised all the way to the target. Analysis changes nothing; it is a report. Read it: a folder where most files sit between 87 and 93 dB is normal, and a few outliers at 80 or 100 dB are exactly the files that have been ruining your shuffle.

Step 6: Apply the gain

Click Track Gain (or Album Gain from the pull-down). MP3Gain adjusts each file’s frames and updates the list as it goes. Two things to know:

• Clipping protection: with the “Don’t clip when doing Track Gain” option enabled, a file that would clip is raised only as far as it safely can and ends up a little below the target. That is the correct outcome — slightly quieter beats distorted.
• It is fast, but let it finish. A folder takes seconds to minutes. Do not close the program mid-run; a file being written at that moment is the one file the undo record may not cover.

Step 7: Verify the result

Run analysis once more. Every processed file’s Volume should now sit at — or a fraction below — 89.0 dB. Then listen like a skeptic: play the previously quietest song and the previously loudest song back to back, ideally on the device that annoyed you in the first place. If the destination is a car stereo or a phone, test there — those players are the whole reason to prefer file-level gain over tag-based tricks, and they each have their own follow-up guides.

Not happy? Nothing here is a one-way door. Change the target, re-apply, or undo the changes entirely — the undo record MP3Gain wrote into each file’s tags lets you restore the original state in one pass.

A worked example: three songs, one folder

Numbers make the process click. Imagine a folder with three files whose analysis reads: Song A, Volume 84.0 dB (a quiet 1980s rip), Song B, Volume 96.5 dB (a loud modern master), and Song C, Volume 91.5 dB (somewhere in between). Against the 89.0 dB target, MP3Gain proposes Track Gains of +4.5, −7.5, and −3.0 dB — each rounded to the nearest 1.5 dB step the MP3 format allows. Apply Track Gain, and all three land within a fraction of a decibel of 89 dB: A comes up out of the murk, B is reined in, C settles slightly. In Album mode, by contrast, the same folder would get one shared adjustment calculated from the set’s overall level, and A would still sound much quieter than B — correct behaviour for an album, wrong behaviour for a mixed folder. Same files, same program; the mode is the decision.

Frequently asked questions

Is this really lossless? Does normalizing reduce quality?

No quality is lost. MP3Gain edits the gain value inside each MP3 frame instead of decoding and re-encoding the audio, so the sound data itself is never regenerated. The only rounding involved is that frame gain moves in 1.5 dB steps, so a file can land at most a fraction of a decibel from the exact target — far below what anyone can hear.

Why 89 dB? My music sounds quieter afterward

89 dB is the shared reference that makes files comparable. Loud modern tracks are turned down to it, quiet tracks are turned up to it, and the average result can feel quieter than the loudest files you had before — that is the levelling working. Turn your player up once; the win is that you stop touching it after that.

Will the fix work in my car, on my phone, and on my speaker?

Yes — that is the advantage of changing the file instead of its tags. Every decoder applies the frame gain values, including players that ignore ReplayGain tags entirely. Our car and phone guides cover the device-specific details.

Can I undo the changes later?

Yes. MP3Gain stores an undo record in each processed file’s tags. Add the files back, choose Undo Gain changes from the Modify Gain menu, and the original volume is restored. The full walkthrough is in our undo guide.

Does MP3Gain work on FLAC, M4A, or WAV files?

No. MP3Gain is an MP3 tool. The same ReplayGain idea exists for other formats — AAC uses the AACGain variant of the same engine — but each format needs its own tool, and tag-based ReplayGain in a player like foobar2000 covers formats MP3Gain cannot, as long as your player reads the tags.

MP3Gain Portable: The No-Install Version, Explained

“MP3Gain Portable” is not a separate product. It is the same MP3Gain 1.2.5, distributed by the official project as a ZIP file — mp3gain-win-1_2_5.zip — that you unzip and run without installing anything. This page explains when the portable build is the right choice, how to run it on Windows 11, and the one legacy-runtime catch that can stop it from opening.

Portable vs installer: what actually differs

Under the hood both builds run the same code by Glen Sawyer, free and open source under the LGPL 2.1+. If a site presents “Portable” as a special edition, a lighter rewrite, or anything paid, it is mislabeling the official ZIP — see how to verify the real download.

How to run it on Windows 11

1. Download the ZIP: the official file is on our download page (Official SourceForge button), with a clearly labelled site mirror (Terabox) beside it — same labelling as every file there: the mirror is a mirror, not an official direct link.
2. Right-click the ZIP → Extract All, into any folder you control (Documents, a USB drive — avoid Program Files, which needs admin rights for writes).
3. Run MP3GainGUI.exe. Add your files or a whole folder, run Track Analysis, then apply Track Gain or Album Gain at the default 89.0 dB target.
4. Done — to “uninstall,” delete the folder. Nothing was written to the system.

The one catch: missing runtime components

Portable does not mean dependency-free. MP3Gain’s interface is a Visual Basic-era program, and on a clean Windows 11 machine it can refuse to open with an error about MSCOMCTL.OCX being missing or not registered — the same legacy-component problem that hits the installed build, along with its cousin Runtime Error 75. The full installer route is less likely to trip over this because the components get registered during setup. If the portable build will not start, follow our step-by-step fix in the Runtime Error 75 & MSCOMCTL.OCX guide — the register-the-OCX procedure applies to the portable folder exactly as written, and afterwards the portable build runs normally.

When portable is the wrong choice

If MP3Gain will live on one PC permanently, the installer is honestly simpler: it registers the runtime pieces, creates shortcuts, and sidesteps most first-run errors. Portable earns its keep for USB kits, work machines without admin rights, testing before committing, and keeping a known-good copy next to a music archive. Either way you end up with the same program — and if version numbers elsewhere have you confused (1.2.5? 1.5.2?), the version guide sorts out which number belongs to which build.

A practical portable workflow

The setup that makes portable MP3Gain genuinely useful: keep one folder — call it “MP3Gain Kit” — on a USB drive or in cloud storage, containing the unzipped program and nothing else. Plug it into any Windows machine, run the GUI straight from the folder, and point it at that machine’s music folders or at a library stored on the same drive. Because the gain changes live inside the MP3 files themselves (with undo data in the tag), the results travel with the files; there is no database or profile to sync afterwards. When you are done, close the program and take your drive — the host PC keeps nothing of yours, and your leveled library is identical everywhere you play it.

Two habits that keep portable painless

Keep the original ZIP next to the unzipped folder. If the working copy is ever corrupted, deleted, or left behind on a machine you no longer have, the ZIP rebuilds your kit in a minute — re-downloaded fresh from the official project, it also re-verifies your source each time. Fix the runtime once, properly. The MSCOMCTL.OCX registration described in our Error 75 guide is a per-machine step; on your own PC it is a one-time two-minute job, and on a borrowed PC it is usually the sign to use that machine’s installed copy instead. Portable removes installation from the equation — it cannot remove the age of the program’s runtime, and no honest page should pretend otherwise.

Does the portable build change files any differently?

No — and this is worth stating plainly, because “portable” is sometimes marketed as if it were a different technology. The ZIP contains the same program applying the same ReplayGain analysis and the same frame-level gain changes as the installed build, with the same undo tags. A library leveled with the portable build is indistinguishable from one leveled with the installer, and either build can undo the other’s changes. The only differences are packaging: where the program lives, whether it registers components, and whether it needs admin rights to arrive.

Troubleshooting the portable build

• It will not open at all, or flashes and vanishes: almost always the missing-OCX problem — the fix in our Error 75 guide covers it, and it is a machine-level fix, not a file-level one.
• It opens but forgets your folders and settings: you are likely running it from inside the ZIP preview instead of an extracted folder. Extract fully, then run; a program cannot keep its working files inside an archive it cannot write to.
• A security tool eyes it suspiciously: the build is an old, unsigned legacy executable, which some tools treat cautiously on sight. Verify your ZIP came from the official project (or our labelled mirror), scan the extracted folder, and proceed only when the scan is clean — the same routine as any MP3Gain download.
• It works on one PC and not another: that difference is the runtime components again — installed machines carry them, clean ones may not. It is the portable trade in one sentence: you carry the program, the machine still has to carry its era’s plumbing.