A browser-based volume changer on Android lets you raise, reduce, or mute an audio file entirely inside Chrome, Firefox, or any modern Android browser without installing an app, granting system permissions, or uploading the recording to a remote server. The Lizely Volume Changer follows this pattern: it accepts MP3, WAV, M4A, AAC, Ogg, WebM, or FLAC files in any format your Android browser can decode, scales every decoded sample by a linear multiplier between 0% and 400%, and exports the result as a 16-bit PCM WAV that you save through the Android download flow. Because the decode, gain, clip, and WAV encode all happen in the current browser tab through the Web Audio API, the source audio stays on the device — nothing is sent to Lizely. The trade-off is that this is a file editor rather than a system volume booster: it changes the loudness of the file itself, not the Android media stream.
Many Android users searching for a volume changer actually want a system-wide booster that makes every app louder. That category of tool exists but typically requires accessibility permissions, audio routing hooks, or root access, and the resulting audio is often distorted because the source already sits near digital full scale. A file-level volume changer takes a different route: you open the audio in a browser, change the loudness of the file, and then play that louder file in any app on the phone or on any other device. That makes it useful for normalizing a quiet voice memo, boosting a low-volume podcast before a commute, or producing a muted copy for editing.
How a browser-based volume changer works on Android
The Volume Changer reads the entire encoded file in the browser, decodes it through the Web Audio API into floating-point channel samples, multiplies each finite sample by the selected gain, clamps values that exceed the supported full-scale range, counts how many samples were clipped, and encodes the result as an interleaved little-endian PCM16 WAVE file. According to the W3C Web Audio API specification, decodeAudioData consumes the complete encoded buffer and resolves with an AudioBuffer containing channel data, so the decoder never streams partially decoded audio to the gain stage. The Android browser's codec support decides which formats actually work; a file extension is not a guarantee. If decoding fails, the tool stops and shows an error rather than producing an empty or partial output.
The percentage you set is a direct linear amplitude multiplier. At 100% the decoded samples are kept exactly as the source presents them. At 50% every sample is multiplied by 0.5. At 200% every sample is multiplied by 2. At 0% the tool writes silence but preserves the decoded duration, sample rate, and channel count.
Linear gain and why percentages are not decibels
The slider is linear, not logarithmic, so doubling the percentage is not the same as adding a fixed decibel amount. A single worked step: a sample with decoded amplitude 0.8 multiplied by the 200% linear gain gives 0.8 × 2 = 1.6, which the encoder then clamps to 1.0 because 1.0 is the supported positive full scale. Doubling linear amplitude corresponds to roughly a 6.02 dB increase in amplitude, not a doubling of perceived loudness, because the decibel scale is logarithmic while the slider is linear. That distinction matters most when you push past 100%: at 200% any source sample above 0.5 will clip, and at 400% almost any non-silent sample gets clipped. The browser exposes this through a clipped-sample counter that increments every time a multiplied sample crosses the supported range.
| Percentage | Linear multiplier | Behavior at digital full scale |
|---|---|---|
| 0% | 0 | Writes silence for the full decoded duration |
| 50% | 0.5 | Half amplitude, no clipping risk |
| 100% | 1 | Original decoded amplitude |
| 200% | 2 | Double amplitude; samples above 0.5 will clip |
| 400% | 4 | Quadruple amplitude; almost all non-silent samples clip |
A safe workflow starts near 100%, previews the full result through headphones or speakers, checks the clipped-sample count, and only then reduces or raises the percentage further.
How to change volume on an Android audio file
- Open the Volume Changer page in Chrome or Firefox on your Android device and wait for the page to fully load.
- Choose a supported audio file no larger than 50 MiB and wait for the file name to appear in the input area. If the name does not appear, your browser cannot decode that format and you should convert or re-export the file first.
- Set the linear output volume anywhere from 0% through 400% using the slider or number field.
- Select Change volume and wait for the preview controls to become available.
- Listen to the preview from start to finish, inspect the reported peak value and clipped-sample count, and only then tap the download button to save the resulting -volume-adjusted.wav file through your Android browser's download flow.
If your file is rejected, the most likely cause is one of the hard limits described later rather than the format itself. For a step-by-step walkthrough of the same flow with extra screenshots of the interface, the Volume Changer beginner guide covers the controls in detail.
Reading the clipping report before downloading
After Change volume runs, the tool shows two numbers: a peak value, which is the largest absolute sample after clipping, and a clipped-sample count. The peak tells you how close the result sits to digital full scale, where 1.0 is the maximum representable value after clipping. The clipped-sample count tells you how many multiplied samples had to be clamped to -1 or +1 because the gain pushed them past the supported range. Zero clipped samples means every multiplied sample fit within the range, but it does not guarantee ideal perceived loudness because volume is not loudness. A nonzero clipped-sample count is evidence that the gain may have introduced audible distortion, especially on transients like drum hits, sibilants, or plosives.
If the count is high, lower the percentage and rerun. The tool revokes any earlier temporary object URL the moment you change the file or percentage, so the previous result is no longer downloadable. A job identifier prevents an older asynchronous decode from overwriting newer settings, and the AudioContext is closed after processing.
Output format, filename, and what the tool does not preserve
The exported file is always a 16-bit PCM WAV, with format code 1 for uncompressed PCM inside a RIFF container, little-endian integer fields, the original decoded sample rate, the original channel count, and 16 bits per sample. That structure matches the WAVEFORMATEX layout Microsoft documents for the WAVE format. Negative full scale maps to -32768 and positive full scale maps to 32767, the asymmetric range of signed 16-bit audio. Channel samples are interleaved frame by frame. The downloaded filename ends in -volume-adjusted.wav.
The tool does not preserve source ID3 tags, album art, chapters, loop points, cue markers, encoder metadata, or the original compression settings. WAV is broadly inspectable and avoids adding a new lossy codec dependency, but it is usually much larger than MP3, AAC, or Ogg. If you need a smaller file, encode the exported WAV with a separate tool after download.
Limits that affect whether the tool can finish the job
| Limit | Value |
|---|---|
| Input file size | 50 MiB |
| Decoded duration | 5 minutes |
| Channel count | 8 |
| Total decoded channel samples | 30,000,000 |
These limits bound memory allocation and main-thread work on ordinary laptops and Android phones. A compressed file can expand substantially after decoding, so the decoded limits matter even when the selected file is small. A five-minute stereo MP3 at 44.1 kHz decodes to roughly 5 × 60 × 44,100 × 2 = 26,460,000 channel samples, which fits, while a longer recording will trip the 30 million ceiling. Keep the original file because the operation cannot restore information already clipped in the source, and repeated PCM conversions can complicate version control. For mastering, limiting, or platform-specific loudness targets, the result of this tool is only a starting point: perceived loudness depends on frequency balance, duration, dynamics, speakers, and listening conditions, and the tool does not calculate LUFS, true peak, replay gain, or broadcast-compliance values.
If you're weighing options, Verify an Audio Pitch Changer Result Step by Step covers this in detail.