A volume changer is a tool that multiplies the decoded sample amplitude of an audio file by a chosen factor, expressed as a percentage from 0% to 400%, and then exports the modified signal as a new audio file without re-encoding the source. In a browser-based implementation, every finite sample is read as a floating-point value, and each value is multiplied by the linear gain: at 100% the amplitude is unchanged, at 50% it is halved, at 200% it is doubled, and at 0% the file becomes a silent WAV with the original duration and sample rate preserved. The result is then clipped to the supported full-scale range, written into a 16-bit PCM WAVE container, and handed back to you as a downloadable file. The whole pipeline, including decode, gain, clip, encode, preview, and download, runs in the current browser tab, so the original audio never leaves your device. That architecture is the reason the percentage behaves as a precise multiplier rather than as a vague "louder" knob, and it is also why the tool can report exactly how many samples were clipped during processing.
What a Volume Changer Actually Does
A volume changer works on samples, not on perceived loudness. After the source file is decoded into a buffer of floating-point channel samples, the tool applies one multiplication per sample and rewrites the audio with the modified amplitudes. The percentages you select correspond directly to those multipliers: 50% means every sample is multiplied by 0.5, 200% means every sample is multiplied by 2, and so on through the 0% to 400% range that Volume Changer exposes in its slider.
Because the percentage is applied to amplitude rather than to perceived loudness, the relationship between the slider value and how the file sounds depends on the source recording. A 200% boost can leave a heavily limited track sounding nearly identical to the original, while the same 200% applied to a quiet field recording can lift dialogue into a usable range. The volume changer cannot raise the dynamic range of a file that has already been compressed; it can only rescale what is already there.
Why the Percentage Is a Multiplier, Not a Decibel Control
A common misconception is that 200% means "add 200 decibels" or "make the file twice as loud." Neither is correct. The standard formula for amplitude in decibels is dB = 20 × log10(multiplier). For 200%, that gives 20 × log10(2.00) = 20 × 0.30103 ≈ 6.02 dB, so doubling amplitude produces a 6.02 dB amplitude increase rather than a 6 dB or a 200 dB change. The 6.02 dB figure is a constant: doubling amplitude is always about 6.02 dB, quadrupling is about 12.04 dB, and halving is about −6.02 dB. Volume Changer does not apply a dB-based gain curve, run a limiter, or compute LUFS. It performs the straight multiplication, which is exactly why it can expose clipping as a counted value rather than as a smoothed loudness metric. The reference values for the slider appear in the table below.
| Percentage | Linear Gain | Approximate Amplitude Change |
|---|---|---|
| 0% | ×0.00 | Silence (all samples become zero) |
| 50% | ×0.50 | Roughly −6.02 dB |
| 100% | ×1.00 | 0 dB (no change) |
| 200% | ×2.00 | Roughly +6.02 dB |
| 400% | ×4.00 | Roughly +12.04 dB |
For a clearer walkthrough of the formula, the linear gain accuracy guide explains the same idea with worked examples and shows where the boundary between amplitude and perceived loudness actually sits.
How the Browser Pipeline Produces a WAV
Volume Changer uses the browser's Web Audio decoder, defined in the W3C Web Audio API 1.1 specification, to turn the entire encoded file into a floating-point channel buffer before any gain is applied. That single decode step is why format support depends on your browser, operating system, and codec build rather than on a fixed server-side list. MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC are all candidates, but a file extension is not proof that decoding will succeed. If decoding fails, the tool stops and shows an error rather than producing an empty file.
Once the buffer is in memory, Volume Changer multiplies every finite sample by the selected gain. Values above +1 or below −1 are clipped to digital full scale, and the engine counts how many samples crossed that boundary. The clipped count and the resulting peak after clipping are surfaced in the preview so you can see whether the chosen percentage introduced audible distortion. The AudioContext used for the decode is closed after processing, the previous result's object URL is revoked, and a job identifier prevents an older asynchronous decode from overwriting newer settings. That is why changing the percentage or the file always invalidates the previous download.
Changing Audio Volume in Three Steps
- Choose a supported audio file no larger than 50 MiB from your device and wait for the file name to appear in the input area. Volume Changer accepts MP3, WAV, M4A, AAC, Ogg, WebM, or FLAC, provided your browser can decode the file.
- Set the linear output volume between 0% and 400% on the slider, then select Change volume. The tool will decode the file, multiply every finite sample by your gain, clip the result to ±1, and prepare a WAV preview.
- Listen to the full preview through suitable headphones or speakers, inspect the peak value and the clipped-sample count in the report, and only then download the resulting -volume-adjusted.wav file. If the clipped-sample count is nonzero or the peak sits at full scale, reduce the percentage and process the file again.
Reading the Clipped-Sample Report
The clipped-sample counter exists because linear gain has a hard ceiling. Every sample in the decoded buffer is a floating-point number that lives between −1 and +1 in the Web Audio representation. Once you multiply by a gain above 100%, samples whose amplitude was already near the top of the range will exceed +1 or fall below −1. Volume Changer clamps those samples to ±1 because the PCM16 format cannot store anything outside that window: −32768 maps to the negative full scale and 32767 maps to the positive full scale, following the WAVE PCM structure documented by Microsoft.
A nonzero clipped-sample count is strong evidence that the gain you selected has introduced audible distortion, especially if the peak reported after clipping sits at full scale. Zero clipping does not guarantee an ideal perceived loudness; it only means no sample had to be limited. For an actual mastering pass with loudness targets, use a separate measured audio workflow rather than a linear-gain tool.
Why the Output Is WAV Instead of MP3 or AAC
PCM16 WAV is the output even when the source is a compressed format because it can be encoded locally without introducing a second lossy codec. MP3 and AAC encoding in the browser typically rely on a JavaScript encoder that adds another dependency and another opportunity for quantization error. WAV exposes the exact multiplied samples with no further round-trip, which is why the preview, the clipped-sample report, and the downloaded file all describe the same data. The trade-off is file size: a five-minute stereo WAV at 44.1 kHz is roughly 53 MB, considerably larger than a 192 kbps MP3 of the same content.
File Limits, Decoded Limits, and What Gets Discarded
Volume Changer applies two sets of limits. On the encoded side, the input file must be a browser-decodable audio file no larger than 50 MiB. On the decoded side, the tool rejects decoded buffers that exceed five minutes of duration, more than eight channels, or more than 30 million total channel samples. A small compressed file can still fail the decoded limits, because decoding expands the data substantially before any gain is applied.
The exported file keeps the sample rate, the channel count, and the duration of the decoded signal. Tags, chapters, loop points, cue markers, encoder metadata, and album art from the source are not preserved. If you need that metadata to survive, reattach it after the download rather than expecting the WAV to carry it forward. Keep the original file too, because the operation cannot restore information already clipped in the source and repeated PCM conversions can complicate version control.
When to Reach for Volume Changer
Reach for Volume Changer when you want to boost a quiet recording, attenuate an overcooked source, or generate a silent placeholder WAV of a fixed length. Skip it when you need perceived-loudness normalization, broadcast compliance, true-peak limiting, LUFS targeting, or any workflow that requires measured loudness. Those tasks are loudness-metering jobs, not linear-gain jobs, and they need a tool that can describe what "loud enough" means in a measured unit rather than in a multiplier. For everything that genuinely reduces to "scale every sample by the same number," Volume Changer is the simpler path.
If you're weighing options, Audio Pitch Changer Without an App: Browser Workflow covers this in detail.