MP3Gain for Android: No Official App — What Actually Works

Search Google Play for “MP3Gain” and you will find volume boosters, equalizers and apps borrowing the name — but not MP3Gain. There is no official MP3Gain app for Android, and there never has been: MP3Gain is a Windows desktop program by Glen Sawyer, distributed through SourceForge. This page covers the one historical port you may have heard of, why it is no longer a real option, and the two routes that genuinely work today.

The DroidGain story: a real port that time left behind

In the early 2010s an unofficial Android port called DroidGain did exist. By all surviving accounts it copied the desktop program’s workflow: point it at MP3 files, let it analyze loudness, and apply the same lossless frame-gain adjustment in bulk. For a while it was the answer to “MP3Gain for Android.”

It is not the answer anymore. DroidGain has been unmaintained for years and, as of October 2026, it has no Google Play listing — searching the store turns up only unrelated booster apps, and the remaining mentions of DroidGain live on auto-generated “alternatives” pages describing it in a present tense that is long out of date. Copies of the APK still float around third-party download mirrors, and we do not recommend installing them: the app predates modern Android storage rules, so it is unlikely to handle a current phone’s library correctly, and sideloading an ancient, unverifiable binary whose one job is to rewrite your music files is a poor trade. If DroidGain is still installed on an old device of yours, it will probably still run — just don’t hunt down a copy for a new phone.

Route 1 (recommended): level the files on a computer, then sync

The most reliable way to get MP3Gain results on Android is to do the processing where MP3Gain actually lives — on a Windows PC — and then copy the finished files to your phone. This works because of how MP3Gain applies gain: it changes the gain value inside the MP3 frames themselves, in 1.5 dB steps, rather than asking the player to compensate. Once a file is processed, every Android player plays it at the corrected volume — the stock player, a streaming app’s local-file mode, your car stereo over Bluetooth. No tag support, no special settings, nothing to configure on the phone.

1. Process the library on your PC. Run MP3Gain (or follow the full workflow in our guide to making all MP3s the same volume). Track Gain suits mixed folders and playlists; Album Gain keeps an album’s internal dynamics intact.
2. Copy the processed files to the phone by USB, cloud drive or your usual sync tool. Processed files replace the originals on the phone; keep the PC copies as your master library.
3. Play them anywhere. Because the gain lives in the audio data, the leveling survives every player and every future phone upgrade.

The changes also stay reversible: MP3Gain stores an undo record in each file’s tags, so if you change your mind, the desktop program can restore the original volume exactly — see how undo works. And if your real complaint is that songs jump in volume specifically on your phone, our phone volume guide separates the file problem from the player problem before you process anything.

Route 2: keep files untouched and use a ReplayGain-aware player

The alternative is to leave the MP3s alone and let the player even things out at playback time using ReplayGain values stored in tags. Tools like foobar2000 — or MP3Gain itself in its analyze-only mode — can write those values without touching the audio. The catch is that this only works in players that read the tags, and on Android the honest shortlist is:

• AIMP for Android — actively maintained, and its Play Store listing explicitly advertises “volume normalization using replay gain or peak-based normalization.” Point it at a tagged library, enable the normalization, and track-to-track jumps mostly disappear.
• Poweramp — its Play listing includes replay gain among its features, and it reads ReplayGain values written to ID3v2 tags.
• foobar2000 mobile — from the same team as the desktop scanner, so tags it writes itself are tags it reads.

Two caveats before you commit to this route. First, tag formats matter: MP3Gain stores its data in APEv2 tags by default, which not every Android player reads; ID3v2 ReplayGain fields have the widest support. Second, tag-based leveling exists only inside that one player — send the same files to a car stereo or a different app and you are back to uneven volume. That is why Route 1 is the recommendation whenever a computer is available: it fixes the files, not one app’s playback.

One trap: don’t level the same files twice

Whichever route you choose, pick one system and stick to it. If you level the audio data with MP3Gain on your PC (Route 1) and then also enable replay-gain normalization in a tag-aware Android player (Route 2), the player may apply a second correction on top of the first — especially if the files still carry ReplayGain values suggesting a change that has, in effect, already been made. The usual symptom is a library that sounds too uniform in one app and oddly flat or quiet in another. The file-based route needs no player help at all: if you go with Route 1, leave player normalization off. If you go with Route 2, leave the files untouched and let the tags do the work. Our phone volume guide walks through diagnosing which of the two is already active on your device.

What about the “MP3 volume booster” apps on Play?

Most of them fall into two groups, and neither is MP3Gain. Playback boosters add gain or compression inside the player, which raises quiet songs but also loud ones, and does nothing outside the app. File-processing boosters typically decode and re-encode your MP3s through an FFmpeg-style pipeline at a higher level — that works, but re-encoding an MP3 costs audible quality, is not reversible, and throws away the one thing MP3Gain exists to protect. If a file is simply too quiet and you don’t care about re-encoding, that is a legitimate choice; just make it knowingly, and keep the original.