MP3 to FLAC converter
The policy and the material disagree: an archive that demands lossless files, holding material that only exists as MP3. FLAC gives byte-level integrity for the samples that survive the decode; it cannot undo what the MP3 encoder discarded decades ago.
FLAC stores lossless PCM, but the source is already decoded: any lossy source keeps its existing loss.
Processed on your device. Files aren’t sent anywhere.
Write the decision before running the batch
Illustrative: a station archive holds 1990s interviews as MP3, and the new policy requires lossless files. Re-recording is impossible, so the migration has to be honest about what it preserves. The decision is not 'make the audio good'; it is 'make the bytes stable'.
| Option | What the shelf gains | What it costs |
|---|---|---|
| Keep MP3 only | Nothing changes | Policy unmet; no stable lossless shelf |
| MP3 to FLAC | Lossless storage of surviving samples, stable checksums | Shelf grows; lossy history must be documented |
| MP3 to WAV | Raw PCM, simple tooling | Shelf grows several times larger than FLAC |
| Re-record | Full fidelity | Impossible for archived material |
The policy conflict, stated plainly
Does FLAC make the MP3 lossless?
Why FLAC instead of keeping MP3?
Why not convert to WAV instead?
Should the original MP3 be deleted?
Is the archive uploaded?
Running the shelf, one file at a time
One file per run, up to 60 MiB and 600 seconds of audio. A shelf of hundreds of files is a repeated run with discipline, not a bulk operation.
- Drag the MP3 onto this page; the local FFmpeg worker loads on first use
- Convert, then read the reported codec, duration, sample rate and channel count
- Name the FLAC file after the catalogue number, not the MP3's filename
- Write the provenance note beside it: source format, source bitrate if known, migration date
Integrity checks that survive a migration
A shelf is only trustworthy if it can be verified after a move. Checksums over the FLAC files give that; duration comparison catches a decode that came out short.
- The engine probes the encoded file and compares codec and duration with the source; drift beyond a small tolerance is reported as failure
- Keep a checksum list beside the shelf and re-run it after any storage move
- Read the reported sample rate rather than assuming it — encoder builds differ in the rates they accept
- Never re-encode the FLAC copy back to MP3 as a 'cleanup'; that adds loss
What the provenance note has to say
One line per file: source: MP3, 128 kbps; migrated to FLAC; lossy source, detail not restored. Without it, a future reader assumes the shelf holds native recordings, and that assumption is wrong.
Where FLAC on the shelf pays off
The shelf is the input for everything else: delivery copies, transcription runs, measurement passes. Encoding from FLAC means each downstream job starts from stable bytes instead of from a lossy file that gets re-encoded again.
- Delivery copies: encode from the shelf with FLAC to MP3 or FLAC to Ogg
- Editing and measurement: decode from the shelf with FLAC to WAV
- Future migrations: the shelf is the source of record, not the old MP3 folder