Boost MP3 Volume

Make an MP3 louder or quieter in your browser. Presets for +50%, +100% and -50%, or an exact decibel value. Free, private, no upload, no watermark.

🌐 Español

Drop your file here (.mp3)

πŸ”’ Private by design: your files are processed locally in your browser and never uploaded to any server.

Gain is a multiplication, and the ceiling does not move

Everything on this page comes down to one operation: every audio sample in the file is multiplied by the same number. Pick +50% and each sample is scaled by 1.5. Pick +100% and it is scaled by 2. Pick -50% and it is halved. The custom field does the same thing expressed in decibels instead of a percentage, which is just a logarithmic way of writing the same multiplier.

Digital audio has a hard maximum, and multiplication does not respect it. If a sample was already sitting near full scale, doubling it produces a value that cannot be represented, and the encoder writes the loudest value it has instead. That flattening is clipping, it sounds like crackle or grit on transients, and it is permanent in the output file because the peak information is gone rather than merely reduced.

There is no limiter on this page and no peak detection. That is a deliberate limitation rather than an oversight: the tool does precisely and only what you ask, which makes it predictable, and it puts the responsibility for listening back on you. A whisper-quiet phone memo will usually survive +100% untouched. A track mastered anywhere near modern levels will distort at the same setting.

Reading the presets as numbers

The decibel scale trips people up because two different rules of thumb float around. A doubling of amplitude, which is what the +100% preset does, is about +6 dB, since 20 times the base-10 logarithm of 2 is 6.02. Perceived loudness is a different question and roughly needs closer to +10 dB before most listeners call something twice as loud. So +100% is a large change on the meter and a solid but not dramatic change to the ear, and the two facts are not in conflict.

That is why the custom field exists and why its range stops at 20 dB in each direction. A repeatable +3 dB across a set of interview files is a normal, sane request that no percentage preset expresses well. The presets cover the common cases; the decibel field covers the specific ones.

Lifting a quiet voice memo

  1. Drop your MP3 onto the box above, or use Choose a file. Only .mp3 is accepted here.
  2. Pick from Volume change: +50% louder for a moderate lift, +100% louder (double) when the recording is really buried, -50% quieter to bring something down, or Custom (set dB below) for an exact figure.
  3. If you chose Custom, put a value between -20 and 20 into the decibel field. Positive is louder, negative is quieter.
  4. Click Boost MP3 Volume and wait for the progress bar.
  5. Download the result and, before you rely on it, actually listen to the loudest section. If you hear grit, run the original again at a smaller setting.

That last step is the whole quality-control process. Converting the same file twice at two settings and comparing them takes less time than a single upload to a server-based tool would, so there is no reason to guess.

Every run is a fresh 192 kbps encode

Changing volume is not a metadata edit. Every sample has to be decoded, multiplied and written back out, so the result is always re-encoded with the MP3 encoder at a constant 192 kbps. That has three consequences worth knowing. The output is a lossy re-encode of an already lossy file, so a chain of repeated boosts is not free. The bitrate is fixed rather than matched to your source, so the file size can move in either direction. And the whole file is processed rather than a region, so length and structure are untouched.

If size is the concern after boosting, Compress MP3 re-encodes to lower targets and keeps the original bytes whenever the compressed version would not actually be smaller, which is a guarantee this page does not make.

Louder is a different request from level

If what you want is consistent loudness across several recordings rather than a fixed multiplier on one, this is the wrong tool and Normalize Audio is the right one. It measures the file’s actual loudness first and then applies the correction that recording needs to reach a target, with a true-peak ceiling below full scale, which is exactly the clipping protection missing here. It also accepts MP3, WAV, M4A, OGG and FLAC.

Two neighbours cover the requests that sound similar but are not. If the file is a video rather than an audio track, the Video Volume Booster offers the same presets and custom decibel field, adds an opt-in clipping-safe limiter, and copies the video stream through untouched so the picture is not re-encoded. And if the complaint is that a track sounds thin rather than quiet, that is an equaliser job: the Bass Booster lifts a chosen low-frequency band and keeps its limiter switched on by default, because a bass boost on real music clips almost by construction.

The MP3 never leaves your device for any of this. FFmpeg is compiled to WebAssembly and runs inside the tab, so a private voice memo, an unreleased demo or a family recording stays exactly as private as it was before the page loaded.

See it in action

Screenshot of the Boost MP3 Volume tool with sysfenix-sample.mp3 (72 KB) loaded, Volume change set to +50% louder, Custom volume change in dB (used with "Custom") set to 6
Boost MP3 Volume mid-process: sysfenix-sample.mp3 (72 KB) loaded, Volume change set to +50% louder, Custom volume change in dB (used with "Custom") set to 6.
Screenshot of the Boost MP3 Volume result screen showing sysfenix-sample-boosted.mp3 ready to download (72 KB)
The finished result: sysfenix-sample-boosted.mp3 ready to download (72 KB). The download link is a local blob URL β€” the file never leaves your device.

Frequently asked questions

Can the boosted file come out bigger than the original?

Yes, and often it does. The output is always encoded at a constant 192 kbps regardless of what the input was. A 320 kbps album rip therefore comes back smaller, while a 64 kbps voice memo comes back around three times larger for the same audio and the same length. There is no never-larger safeguard on this page, so the size line the tool prints after the run can legitimately say the result grew.

I chose Custom and nothing sounded different. What happened?

A typed 0 dB is the usual cause. It builds a filter that multiplies every sample by one, so the file is still decoded and re-encoded and you get a new download that sounds exactly like the old one. Clearing the box does not do that, because an empty field counts as no value given and falls back to the +6 dB the page starts with. Type a number between -20 and 20 into the field before running it.

Can I type a bigger number than 20 dB to push it further?

No. Anything beyond the ends of the range is pulled back to -20 or +20 dB before the command is built. That is not an arbitrary cap. Twenty decibels already multiplies the waveform by ten, which will drive almost any real recording hard into the ceiling and turn quiet passages of noise into loud passages of noise. If +20 dB is not enough, the source is likely too quiet to rescue by gain alone.

Can I run a folder of files through it at once?

No, the dropzone takes one MP3 per run. The useful detail for a batch is that your volume setting survives between runs. Clear the finished file with the button offered after the download, drop the next MP3 in, and the preset or custom decibel value you picked is still selected, so applying a consistent change across a set of recordings is a matter of repeated drops rather than repeated setup.

What does Cancel do while it is working?

It shuts down the FFmpeg worker and clears the dropzone completely. There is no half-finished file kept behind and nothing to resume, so cancelling means adding the MP3 again from scratch. It is there for the case where you realise you picked the wrong setting on a long file, which on a single-threaded WebAssembly build can otherwise take a while.

Why does this page only take .mp3 when other audio tools here accept more formats?

Because it is wired to the MP3 encoder from end to end, so the dropzone rejects anything else and tells you what it does accept. If your file is a WAV, M4A, OGG or FLAC, the loudness normalizer on this site takes all of those, although it does a different job, since it measures the recording and moves it to a target loudness instead of applying the fixed multiplication you choose here.

Related tools