Listening setup and limitations
Use a quiet environment, match playback volume, and listen at several representative positions. Switching reuses a master playback time and clamps it to the shortest measured duration. Encoder delay and small duration differences mean the change is only near the same position. This implementation does not claim sample-accurate, gapless, or synchronized multi-player playback.
Browser media support can differ from the local encoder. If a valid AAC, OGG, or other result does not preview, download it or use MP3 for the listening pass. Do not increase volume only for one version. A short obvious passage can be useful, but checking the beginning, a dense section, and a quiet tail reduces accidental conclusions.
Why a higher bitrate is not always audibly better
A higher target gives the encoder more data, but the source may already be limited, previously compressed, noisy, or simple enough that the difference is not audible under current conditions. A larger number cannot recover discarded information. Re-encoding a low-rate source at 320 kbps usually makes a larger representation of the decoded source, not a restored original.
When two versions sound the same to you, choose from compatibility, size, and future use rather than assuming the largest must be best. For an archive, keep a lossless or original master. For delivery, select a tested copy. The measured result table helps separate those roles.
Re-encoding caveats
Every comparison output is newly encoded. If the source is MP3, AAC, or Vorbis, this adds another lossy generation. Comparisons can still answer a delivery-size question, but they do not represent encoding from an untouched master. For codec evaluation, begin with a WAV or FLAC source whose provenance you understand.
The engine processes versions serially and releases each virtual input/output after the result is copied. Output object URLs remain only for the active comparison and are revoked on cancellation, restart, or page exit. Estimated total output warns about workload, while actual browser memory use also includes the engine, input copy, and transient buffers.
How blind comparison works
Blind mode labels versions A, B, C, and so on. Before reveal, the chosen target rates are removed from the settings DOM and the result table, button names, and download names do not disclose them. After reveal, measured settings become visible. This reduces one obvious expectation cue but does not randomize trials, level-match codecs, or collect statistical evidence.
Normal mode displays measurements immediately. In either mode, switch at a stable passage and use the same playback chain. A blind preference can be meaningful for your task without becoming a universal finding. The tool never uploads your selected version, acceptable marker, source name, tags, or audio.