A recording can make listeners reach for the volume control because its level is too low or inconsistent. Normalize its volume for the intended listening situation, then hear the entire result. A level change can improve audibility, but it cannot restore sound that was badly captured.
Drop an audio file to normalize
or click to browse — MP3, WAV, FLAC, AAC, OGG
Listen for quiet sections, loud jumps and noise before changing the file.
Use the available normalizing control while preserving the original source.
Hear quiet, loud and transitional passages in the saved recording.
Listen to the source at a normal device setting. Is the whole recording quiet, or does one section jump above the others? These are related but not identical concerns. A single voice note recorded too far from the microphone may need a different review from several clips recorded on different devices. Name the problem before assuming one overall change will solve it.
Also distinguish loudness from clarity. Raising a distant voice can raise room hiss and traffic noise at the same time. If words were lost under noise, a louder file may remain difficult to understand. Normalization should be judged by the listener's experience, not by a meter alone.
For speech, check quiet words, changes between speakers and the ends of sentences. A listener should not need to turn the device up for one person and down for another. In music, expressive soft and loud passages may be intentional. Making everything feel equally forceful could work against the piece's purpose.
Use representative material from the whole file. A calm introduction might not reveal a loud laugh later, and a musical chorus might hide a soft opening. If you are preparing a set of recordings for one presentation, compare them as a group as well as individually. The goal is comfortable continuity for the audience.
A clipped microphone recording already lacks some of the original shape of loud sounds. A level adjustment cannot simply recreate it. Similarly, a source full of background noise may become louder without becoming cleaner. Keep expectations tied to the actual operation: it changes the listening level, not the events captured during recording.
If the original is severely damaged, consider another take or a dedicated restoration process. For ordinary level differences, make a change and listen rather than stacking adjustments without comparison. The best result is one that helps the audience hear the content without introducing a new annoyance.
Open the output and check a quiet passage, a loud passage and each known transition. Are the words easier to follow? Is a sudden burst still uncomfortable? Does the end play completely? A small preview can make a normalized file appear successful while an outlier remains elsewhere.
Use a reasonable listening level during comparison. If you turn the device up for the original and forget to match the result, your impression may reflect playback settings instead of the changed file. Compare with care and, if the recording is important, try the type of headphones or speakers the recipients are likely to use.
Save the original separately. A future editor may need to revisit how the level was changed or use another approach for a different platform. Naming the new file clearly prevents a collaborator from mistaking a delivery copy for the untouched recording.
Check the receiving platform's requirements for file type, size and any stated loudness target separately. The existence of a normalized output does not guarantee compliance with every service. Share only after listening to the actual saved file in context; the goal is a comfortable, intelligible experience for the specific audience.
It can raise its level, but noise and unclear speech may rise with it. Listen to the actual result.
No. Changing level is different from removing unwanted sound.
No. Information lost during a distorted recording is not restored by level adjustment.
Not necessarily. Quiet and loud passages may be part of the performance.
Check the quietest and loudest moments, known transitions and the end of the saved file.
It provides a reference for another level decision or later editing.
Verify the service's own type, size and loudness requirements separately.