To change a PDF’s size without losing quality, use a document-specific optimizer; Lizely’s Volume Changer does not resize PDF pages or PDF file size because it changes audio amplitude, not document dimensions or storage. If the intended task is to change the perceived level of an audio file, however, Volume Changer provides a controlled local workflow: it multiplies decoded samples by a linear amount from 0% to 400% and exports the complete result as 16-bit PCM WAV. A 100% setting retains decoded amplitude; 50% applies a 0.5 multiplier, while 200% doubles amplitude. This does not mean every loudness goal is automatically achieved. Raising a signal can push samples beyond digital full scale, where they are clipped and may sound distorted. The tool therefore exposes the post-clipping peak and a clipped-sample count, and its instructions require previewing the entire result before downloading. “Without losing quality” also needs an exact definition here: Volume Changer does not need another lossy codec, but it produces a new PCM WAV and does not restore peaks that were already clipped in the source. For the PDF task, seek a document optimizer instead. For changing the level of supported audio, Volume Changer is the relevant local tool.
The PDF task and the audio task are different
“Size” can refer to a PDF’s page dimensions, its storage size, or the apparent level of an audio recording. A page-size change concerns how a document is laid out. A file-size change concerns how much data is stored or transmitted. An audio-volume change concerns the amplitude of decoded samples. Volume Changer belongs to the third category. It does not open, compress, optimize, or reformat a PDF, and no PDF reduction is performed as part of its workflow.
The useful connection is that the same concern about unwanted quality loss can apply to an audio edit. Volume Changer addresses it by making a linear amplitude change in the current browser tab, reporting whether the result crossed digital full scale, and producing a complete WAV export. The Volume Changer is therefore the solution when the intended object is a supported audio file and the desired change is louder, quieter, or muted audio.
Adjust the volume of a supported audio file
- Open the Volume Changer and choose a file. Select a browser-decodable MP3, WAV, M4A, AAC, Ogg, WebM, or FLAC file no larger than 50 MiB, then wait for the file name to appear. The file type must be decodable by the current browser, operating system, and codec build. A matching filename extension is not proof that the media can be decoded. If decoding fails, the tool stops and shows an error rather than creating an empty or partial output.
- Set the output volume and process the file. Choose a linear volume from 0% through 400%, then select Change volume. At 0%, the output is silent while the decoded duration, sample rate, and channel count remain intact. At 100%, decoded amplitude is retained. At 200%, every finite sample is multiplied by 2. Changing the selected percentage or file replaces the previous result.
- Preview and inspect the result. Listen to the complete WAV preview, then check the displayed peak and clipped-sample count. A nonzero count means multiplied samples crossed the digital full-scale boundary and were limited to the supported range, so audible distortion may have been introduced. Reduce the percentage and process the file again if the result sounds distorted. A zero count does not guarantee ideal perceived loudness.
- Download only after the full preview. Once you have listened to the complete result, download the WAV. The downloaded filename ends in -volume-adjusted.wav. The generated download is temporary and disappears when the tab closes or when a new operation replaces it.
Keeping the original file is important. A gain adjustment cannot recover information that was already clipped, and a new export does not preserve the source file’s original compression settings or metadata.
Linear gain maps percentage to sample amplitude
Volume Changer uses a direct linear amplitude multiplier. The control is not a decibel control, and it is not a loudness-normalization control. The percentage changes the amplitude of the decoded audio; it does not change the length of the recording or the number of channels.
| Setting | Linear result |
|---|---|
| 0% | Writes silence while preserving decoded duration, sample rate, and channel count. |
| 50% | Multiplies every sample by 0.5. |
| 100% | Keeps the decoded amplitude of each sample. |
| 200% | Multiplies every sample by 2, an amplitude increase of approximately 6.02 dB before clipping. |
| 400% | Applies the linear multiplier at the upper end of the control’s range; out-of-range samples are limited to digital full scale. |
The 200% example is easy to misunderstand. It means double linear sample amplitude, not a 200-decibel change. Perceived loudness also depends on frequency balance, duration, dynamics, speakers, and listening conditions. The tool does not calculate LUFS, true peak, replay gain, or a platform-specific loudness target, and it does not perform mastering, limiting, compression, or noise reduction.
Use the clipping report to protect the result
Each finite decoded sample is multiplied by the selected gain. A value above +1 or below -1 is clipped to the supported full-scale range, and the tool counts every sample that crosses that boundary. The peak shown in the result is the peak after clipping, not simply the peak requested in the gain setting.
For one finite source sample with a decoded amplitude of +0.80, the formula is sample amplitude multiplied by the percentage expressed as a decimal. At 125%, +0.80 times 1.25 equals +1.00, so the sample reaches full scale without crossing it. A sample that would land beyond the boundary would be limited to -1 or +1, and that crossing would appear in the clipped-sample count. This is a sample-level amplitude check, not a LUFS measurement or a promise that the audio will meet a particular playback target.
Clipping is a warning to listen carefully. If the waveform is harsh, uneven, or distorted, reduce the percentage and process the source again. Zero clipped samples means the gain did not push decoded samples outside full scale, but it does not mean the recording is mastered, normalized, or perceptually ideal. The original may already contain clipped peaks, and no volume tool can restore information that was lost before the edit.
Understand the WAV export and its size tradeoff
Volume Changer always exports a WAV file, even when the source is a compressed format such as MP3, M4A, AAC, Ogg, WebM, or FLAC. The export uses a RIFF WAVE container with little-endian integer fields, format code 1 for uncompressed PCM, the original decoded sample rate, the original number of channels, and 16 bits per sample. Channel samples are interleaved frame by frame. Negative full scale maps to -32768, while positive full scale maps to 32767, matching the asymmetric range of signed 16-bit audio.
This format is useful because PCM16 WAV is broadly inspectable and does not introduce a new lossy codec or encoder dependency. It is also uncompressed, so the exported file is usually much larger than MP3, AAC, or Ogg. That is an important distinction for a search about making a PDF smaller: Volume Changer is not a file-compression tool, and its WAV output should not be expected to reduce document or audio storage size. It is a deterministic conversion of the adjusted audio into a new PCM representation.
The export does not preserve source tags, album art, chapters, loop points, cue markers, encoder metadata, or the original compression settings. The output is therefore best treated as an adjusted audio file, not as a bit-for-bit copy of the source container. At 100% the decoded amplitude is kept, but the operation still creates a new 16-bit WAV result and may expose clipping or other source limitations.
Check browser support and processing limits
The file is decoded completely in the browser before gain is applied. Supported choices are browser-decodable MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC files. Actual support depends on the browser, operating system, and codec build. The decoded duration, channel count, and sample count matter as well as the encoded file’s apparent size.
| Requirement | Verified limit or behavior |
|---|---|
| Encoded input size | No larger than 50 MiB. |
| Decoded duration | No longer than five minutes. |
| Decoded channel count | No more than eight channels. |
| Total decoded channel samples | No more than 30 million samples. |
A compressed file can expand substantially after decoding, so a file that is below 50 MiB can still be too long or contain too many samples. The tool rejects a duration, channel count, or sample total outside its limits. It also stops with an error if decoding fails rather than producing a misleading file. Selecting a different file or percentage invalidates the prior result and revokes its temporary object URL, so always use the preview and filename associated with the current settings.
Follow a local, repeatable editing routine
Start near 100% when you are making a safe edit, then preview the full output through suitable headphones or speakers. Check the peak and clipped-sample report before saving. If the report shows crossings or the audio sounds distorted, lower the percentage and process the file again. The goal is not simply to make the waveform numerically larger; it is to create a complete result that remains clean for the intended listening conditions.
- Keep the original source as an archive because the operation cannot undo clipping already present in it.
- Listen to the complete WAV before downloading, rather than judging only the first few seconds.
- Verify the downloaded duration and channel count before replacing a production audio file.
- Remember that changing sample amplitude does not turn up a physical speaker or device’s hardware volume.
Decoding, gain adjustment, previewing, and WAV encoding all occur in the current browser tab. The source audio is not uploaded, queued, analyzed by an external service, or retained by Lizely. For professional delivery, use a measured audio workflow, monitor the exported file, and account for the fact that Volume Changer is not a substitute for loudness normalization, limiting, mastering, or broadcast-compliance processing. For the original PDF query, use a document optimizer; for changing the level of supported audio without sending the file to an external service, Volume Changer provides the focused local workflow.