To get started when you need to use Volume Changer, choose a browser-decodable audio file no larger than 50 MiB, set a linear output level from 0% to 400%, and export the complete result as a 16-bit PCM WAV.
This is a file-based workflow, not a control for Windows' master or per-application Volume Mixer. It multiplies sample amplitudes and encodes the result as a new file; it does not rewrite the source or make an app louder in the operating system's mixer. If you only need to change the playback level right now, use the device or application volume controls instead.
For an actual audio-file adjustment, keep the original, begin near 100%, and listen to the complete output before replacing any production file.
Choose a file the browser can process
Volume Changer accepts browser-decodable MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC files. A listed extension does not guarantee that the selected file will decode successfully because support depends on the browser, operating system, and installed codec builds.
Check the input size and the limits that apply after decoding:
| Check | Supported limit | What it means |
|---|---|---|
| Input file size | 50 MiB maximum | The selected file must not exceed this size. |
| Decoded duration | 5 minutes maximum | Length is measured after the browser decodes the complete file. |
| Channel count | 8 channels maximum | Multichannel files above this limit cannot be processed. |
| Decoded channel samples | 30 million maximum | This total counts samples across the decoded channels. |
| Format | Browser-decodable audio | MP3, WAV, M4A, AAC, Ogg, WebM, or FLAC, subject to browser codec support. |
A compressed file can expand substantially after decoding. That means a source below 50 MiB can still exceed the duration, channel, or decoded-sample limits, so check the decoded figures as well as the file size.
Make your first adjustment
- Choose the source file. Select a supported audio file no larger than 50 MiB, then wait until its file name appears before changing any settings.
- Set the output percentage. Choose a linear volume from 0% through 400%. At 100%, the multiplier is 1 before PCM encoding, which makes it a useful baseline. At 0%, the output becomes silence. Select Change volume when the percentage is set.
- Preview and inspect the result. Listen to the generated WAV from beginning to end. Check the reported peak and clipped-sample count before deciding whether the gain is suitable.
- Regain or download. If the clipped count is nonzero or you hear distortion, reduce the percentage and run the operation again. If the result sounds acceptable, download it. The generated filename ends in -volume-adjusted.wav.
For a more structured review pass, use the guide to checking the result after using a Volume Changer before the file enters a production workflow.
Set gain without ignoring clipping
The percentage is a direct linear amplitude multiplier, not a perceived-loudness control. Before clipping, the calculation is:
output sample = decoded sample × gain, where the gain is the selected percentage divided by 100.
For example, a decoded sample of +0.80 processed at 200% becomes +0.80 × 2 = +1.60. Because the supported full-scale boundary is +1.00, the result is clipped to +1.00 and counted as a clipped sample.
Increasing the percentage does not automatically produce a balanced or natural-sounding recording. A 200% setting doubles linear amplitude, which is approximately a 6.02 dB amplitude increase before clipping—not a 200 dB increase. Perceived loudness also depends on frequency balance, duration, dynamics, speakers, and listening conditions.
Volume Changer is not loudness normalization, mastering, limiting, compression, noise reduction, or a broadcast-compliance tool. It does not calculate LUFS, true peak, replay gain, or platform-specific targets. Use a measured production workflow when you need to meet a formal delivery specification.
Check the result before you download
The peak shown by the tool is measured after clipping. A nonzero clipped-sample count means the gain pushed samples beyond digital full scale, so the increase may have introduced audible distortion. A zero count means no additional crossings were detected, but it does not guarantee ideal perceived loudness.
Preview the entire result through suitable headphones or speakers rather than checking only the first few seconds. Pay particular attention to sections that become harsh, pump, or distort. If the source already contains clipped detail, the tool cannot reconstruct information that was lost before processing.
Changing the selected file or percentage invalidates the previous page result and revokes its temporary download URL. Complete and save the result before starting another operation if you need that exact version. Before replacing production audio, verify the downloaded duration and channel count against the original.
Keep the source file as well. Repeated PCM conversions can complicate version control, and keeping the original gives you a clean reference for comparison or rollback.
Understand the browser-local WAV export
Decoding, gain adjustment, WAV encoding, preview, and download all happen in the current browser tab. The source audio is not uploaded, queued, analyzed by an external service, or retained by Lizely.
The output is always WAV, even when the source is a compressed MP3, AAC, or Ogg file. It contains the complete result as interleaved, 16-bit PCM channels in a little-endian RIFF/WAVE container using format code 1. The exported file retains the original decoded sample rate and number of channels. These fields follow the format described in Microsoft's WAVEFORMATEX reference.
The export does not preserve source tags, album art, chapters, loop points, cue markers, encoder metadata, or the original compression settings. WAV files are also usually much larger than compressed source formats because they store uncompressed PCM audio.
The page's generated download is temporary. Its link disappears when the tab closes or when a new operation replaces it, although a file already downloaded to your device remains under normal file-management controls.
Resolve first-run decode and download issues
If a selected file cannot be decoded, check whether the browser and operating system support its actual codec. The tool uses the browser's Web Audio decoding process described in the W3C Web Audio API documentation for decodeAudioData. Renaming a file or relying on its extension will not make an unsupported codec decodable.
When decoding fails, the tool stops and displays an error instead of producing an empty or partial WAV. If a compressed file is rejected, check the decoded duration, channel count, and total channel-sample limits rather than focusing only on its size on disk.
For missing download links, check whether the tab was closed or whether a newer file or percentage operation replaced the previous temporary result. For operating-system mixer problems, use the system's application-level audio controls; file-based gain does not change those mixer assignments.
If you're weighing options, What Details Matter When I Use an Audio Pitch Changer? covers this in detail.