Audio output method
Audio loudness and file size: a practical local workflow
Making audio louder, more even, or smaller changes different properties. A numerical setting can guide the operation, but the completed output must still be measured and heard before it is delivered.
On this page
Volume, peak level, and average loudness are not interchangeable
A gain increase raises the signal. Peak protection limits the highest samples to reduce clipping risk. An average-level target describes a different measurement. These controls can work together, but they answer different questions about the same sound.
Aftermath names its decoded peak and unweighted RMS boundaries rather than claiming LUFS mastering. That distinction matters when a user needs a focused local result rather than a broadcast-standard workflow.
Try it with a safe sample
Compare WAV and MP3 file sizes
A quiet three-second test tone provides a safe comparison. The audio converter created the MP3, then the browser decoded it again.
- Download the WAV sample and open the audio converter.
- Choose MP3, 128 kbps, mono, and 44.1 kHz.
- Save the result. Listen at a comfortable volume and compare file sizes.
| Original WAV | 264,644 B |
|---|---|
| Measured MP3 | 48,639 B |
| Decoded MP3 duration | 3.030 s |
| Decoded sample rate | 44,100 Hz |
| Decoded channels | 1 |
MP3 timing can include encoder padding. This simple tone checks conversion, not speech quality. Judge your own recording by listening.
How we checked this
Synthetic samples. No personal files. Results can vary with browser encoders.
Tested: · Chromium 149.0.7827.55
Download measurements and file hashes · Testing method
Sample files are free to reuse under CC0.
File size comes from duration, codec, and bitrate
A one-minute MP3 and a one-hour MP3 cannot share a meaningful byte target without considering duration. Codec choice, bitrate, channel count, source complexity, and container overhead all influence the final result.
WAV is generally much larger because it stores uncompressed PCM audio. It can be the right choice for a destination that requires it, but it is not a compression strategy.
| Goal | Useful control | Review after export |
|---|---|---|
| Make speech easier to hear | Gain or normalisation with peak protection | Clipping, intelligibility, background noise |
| Reduce file size | A supported MP3 quality/bitrate choice | Bytes, duration, codec, audible artefacts |
| Keep an uncompressed result | 16-bit PCM WAV when appropriate | Destination support and practical file size |
Listening is a verification step
The output receipt can report bytes, duration, channels, and codec. It cannot fully report whether speech is harsh, music has obvious artefacts, or an important quiet detail disappeared. Listen to the completed result through a suitable device.
A result that meets a byte budget but fails the actual listening goal should be revised intentionally, not silently delivered.
Keep the claim bounded
A local audio tool can verify facts from the output it creates. It cannot promise a universal loudness standard, restoration quality, platform acceptance, or identical playback across every application and device.
Desktop tools and commands
Use a local tool