Practical guides
How to compare two audio files in a browser without uploading them
Try a local audio sample, align two recordings, review changed moments and export a difference WAV. Learn what the signal score can and cannot tell you.
Updated 2026-10-15 · 7 min read
When this workflow helps
Use this workflow when two audio exports sound close but you need evidence before approving a podcast, voiceover, music cue, sound effect, or converted file.
A simple waveform view is not enough when one file starts a little later, was re-encoded, or has subtle EQ and loudness changes.
What to check first
Start with duration, peak level, average loudness, and channel count. These metrics catch obvious export mistakes before you spend time listening through the whole file.
If the files have different start padding, use offset alignment before judging similarity. Otherwise a tiny timing shift can make the entire waveform look different.
- Duration delta: confirms whether the files are trimmed or padded differently.
- Loudness delta: shows whether one version was normalized, limited, or exported at a different level.
- Offset alignment: compensates for small start-time differences.
- Spectral difference: helps separate low, mid, and high frequency changes.
Try the sample before choosing files
Open Audio Diff, click Try sample audio, then click Start Compare. MKDiff generates two four-second WAV files locally: the revised recording contains silence from 2 to 2.5 seconds.
Find that interval in the heatmap and changed-moment list, then listen to the original and revised recordings. This gives you a known edit to check before using your own files.
Browser-only comparison steps
Choose the original recording on the left and the revised recording on the right, up to 50 MB each, then click Start Compare. MP3 and WAV are useful starting points; decoding support for other formats depends on your browser.
If the recordings start at different times, try Auto align and verify the result by listening. The timing control runs from -2 to +2 seconds: a positive modified offset skips the revised opening, while a negative offset delays it on the original timeline.
Review the heatmap and changed moments, listen to both versions, and compare loudness-normalized mode with raw volume. Normalization can hide a gain-only change, so use raw volume when checking export levels.
Export the JSON report for durations, levels, offset, comparison mode and changed time ranges. Export the difference WAV to hear the residual for the currently selected alignment and normalization.
How to interpret results
Treat the score as a sampled waveform estimate, not a listening verdict. Timing and phase shifts can lower it even when two recordings sound similar. Loudness, duration, sample rate and channel count also affect the displayed result; the spectral panel is a separate review aid.
For a brief strong difference, listen at that time for a cut, dropout, click or inserted silence. If differences cover the whole recording, first check alignment, loudness and whether one file was re-encoded.
The timeline starts at the original file’s zero and includes the longer ending after applying the offset. Audio missing from either file is compared with silence. Review that ending when one export was trimmed or padded.
If the comparison cannot finish
Check that both inputs are valid audio files within the 50 MB limit. If your browser cannot decode a format, export a supported WAV or MP3 and try again.
Long recordings can require much more memory than their compressed size suggests. Compare a shorter excerpt when the tab slows down or decoding fails. The file-size limit is not a guarantee that every recording will fit in memory.
FAQ
Does browser audio diff upload my files?
In MKDiff, selected audio files are decoded and compared in the browser for the normal workflow, so the files do not need to be uploaded to a server.
Why do two MP3 files differ even if they sound the same?
Lossy encoders can change samples, timing padding, loudness, or spectral energy. Compare waveform, loudness, offset, and spectral difference before deciding whether the content changed.
What does a difference WAV mean?
MKDiff mixes each recording to mono, applies the current timing offset and optional loudness normalization, then subtracts the modified signal from the original. The residual includes the longer ending, with absent audio treated as silence. A quiet residual describes those aligned, processed signals; it does not prove that the original stereo files are identical.
Can the score identify a speaker or detect song plagiarism?
No. It is a sampled signal comparison that is sensitive to timing and phase. Different words, microphones, rooms or encoding can change the result. It does not identify people, search for songs or determine copyright ownership.
Why does a small audio file use so much memory?
Compressed files are decoded into audio samples before comparison. Memory use depends on duration, channel count and sample rate as well as file size. If decoding fails or the tab slows down, compare a shorter excerpt or export a WAV your browser can decode.