IT
OmnvertImage • Document • Network

Audio Tools

Extract, convert, and clean up audio from video — trim, merge, remove silence, and normalize loudness.

About

Start with the goal. Need maximum playback compatibility? Use MP4 → MP3. Want a lightweight extract and your video already has AAC audio? MP4 → M4A can be faster because it copies the audio stream instead of re-encoding.

Know what to expect in the result: compressed formats (MP3/M4A) trade size for quality, and file size mostly follows duration + bitrate. Loudness normalization changes perceived volume (LUFS), but it won’t remove background noise or fix a distorted recording.

A reliable order is: extract → trim → remove silence (optional) → merge → normalize. If MP4 → M4A fails, the audio inside your video may not be compatible with M4A stream-copy—use MP4 → MP3 instead.

FAQ

When is it “no re-encode” or lossless?
Only when the tool can copy the existing audio stream into a new container (stream copy). For example, MP4 → M4A can be lossless when the source audio is compatible (commonly AAC). Other tools often re-encode to produce an MP3 output or apply edits.
Why did MP4 → M4A fail?
The video may contain a non‑AAC audio codec or unusual track metadata. This tool uses stream copy (fast, no quality loss when supported), so incompatible inputs can fail. If you need a guaranteed output, use MP4 → MP3.
My result is louder/quieter or clips — what should I change?
Normalization targets loudness, not peaks. If you hear distortion/clipping, choose a slightly lower target (more headroom) or normalize after trimming/merging. If the file is simply quieter, pick a higher target preset.
Is my audio stored?
Files are processed to generate your download and aren’t meant to be retained long‑term. Still, avoid uploading highly sensitive recordings and always review the output before sharing.

Most complaints about audio are level complaints wearing a costume. A podcast where one guest is twice as loud as the other, an intro that blows out headphones before the speech comes in, a compilation where every track needs the volume knob adjusted — none of those are quality problems, and none of them get fixed by re-exporting at a higher bitrate.

The other half of the job is understanding that MP3 is lossy and generational. Every decode-and-re-encode cycle throws away a little more, so a file that has been trimmed, merged and normalised in three separate sessions has been through three encoders. Do all the edits in one pass where you can, and keep the original around until you are finished.

Trimming, merging, speed changes, normalisation and stereo conversion run in the browser through the Web Audio API, so those files stay on your device. Pulling audio out of a video container and a few of the longer batch jobs go through server-side processing, where the file is held only as long as the conversion takes.

Loudness is not volume: LUFS and true peak

Peak normalisation raises a file until its loudest single sample touches the ceiling. That sounds like it should work, and it does not: one stray drum hit or door slam can be the peak, leaving an otherwise quiet recording untouched. Loudness normalisation measures perceived level over time in LUFS instead, which is why two files normalised to the same LUFS value actually sound equally loud.

Useful targets: around -14 LUFS integrated for music going to Spotify or YouTube, -16 LUFS for stereo podcast audio to match Apple’s recommendation, and a true-peak ceiling of -1 dBTP so that lossy encoding does not push samples into clipping after conversion. Streaming platforms turn anything louder back down anyway, so mastering at -9 LUFS buys you nothing except lost dynamics.

Trimming, merging and the clicks nobody wants

MP3 stores audio in frames of 1152 samples — about 26 milliseconds at 44.1 kHz — and a cut can only land on a frame boundary without re-encoding. This is why a trim occasionally leaves a few milliseconds you did not ask for. Encoders also add padding at the start and end, which is what produces the small gap between merged tracks that should have been continuous.

Cutting in the middle of a waveform leaves a sudden jump in amplitude, and a sudden jump is a click. A 5–10 millisecond fade at each edit point removes it without being audible as a fade. When merging files recorded on different days or different devices, normalise after merging rather than before, otherwise you are matching each file to a target instead of matching them to each other.

Speed, pitch, and how slowed + reverb works

Changing playback rate by resampling moves speed and pitch together — this is the tape effect, and at 0.8x it drops the pitch by roughly four semitones. Time-stretching uses a phase vocoder to change duration while holding pitch constant, which is what you want for a podcast played at 1.25x. It costs something: transients smear, and sharp percussion picks up a faint metallic ring past about 1.5x or below 0.7x.

The slowed + reverb sound deliberately uses the first method. The track is resampled to roughly 0.75–0.85x so pitch drops with the tempo, then a long reverb with a decay in the 2–4 second range is mixed in behind it. Push the rate below 0.7x and the low end turns muddy; keep the reverb mix under about 35% or the vocal stops being intelligible.

Silence removal and the mono decision

Silence detection works on two numbers: a threshold and a minimum duration. A threshold near -40 dBFS catches room tone in a decently treated space, but a noisy room may need -30, and setting it too aggressively clips the quiet tails off words. Requiring 300–500 milliseconds before a gap counts as silence stops the tool from eating natural pauses between sentences, and leaving 100–200 milliseconds of padding at each edge keeps speech from sounding clipped.

For interviews, lectures and voice memos recorded on a single microphone, converting to mono halves the file size and loses nothing, since both channels carry the same signal. Be careful with material recorded on two mics or processed with stereo widening: summing to mono can cancel out-of-phase content and make parts of the mix disappear. Check by listening to the mono version before you delete the stereo original.

Common questions

Does trimming an MP3 reduce its quality?
Only if the file is decoded and re-encoded, which most edits require. One extra generation at a decent bitrate is hard to hear; four or five stacked generations are not. Work from the highest-quality source you have and export once at the end.
Which format should I export?
MP3 at 192–320 kbps for anything that has to play everywhere, M4A/AAC when you want smaller files at similar quality, and WAV or FLAC if the file is going into another editing session. There is no audible reason to export speech at 320 kbps — 128 kbps mono is transparent for a single voice.
Why do my merged tracks have a gap between them?
MP3 encoders pad the beginning and end of a file, and unless the player reads the gapless metadata that padding becomes silence. Merging into a single decoded stream before export avoids it. Files that came from different sources may also differ in sample rate, which forces a resample at the join.
Can I speed up a podcast without the chipmunk effect?
Yes, that is exactly what time-stretching does — duration changes and pitch stays put. It holds up well between about 0.8x and 1.5x. Beyond that, speech starts to sound processed even though it stays understandable.
How large a file can I process in the browser?
Browser processing decodes to uncompressed PCM in memory, which is roughly 10 MB per minute of 44.1 kHz stereo audio. Most machines handle an hour comfortably; multi-hour recordings on a low-memory phone can fail. Split long files first if you hit a wall.
Is my audio uploaded to a server?
Trimming, merging, speed, normalisation, silence removal and stereo-to-mono all run locally in your browser. Extracting audio from video and some longer conversions need server-side processing; those files sit in temporary storage for the duration of the job and are removed afterwards.
What bitrate should a voice recording use?
For a single speaker, 96–128 kbps mono is effectively transparent and keeps an hour-long episode near 50 MB. Music needs more headroom, so 192 kbps stereo is a reasonable floor. Doubling the bitrate on a voice track adds size and no audible detail.