How to wav to flac converter — zero upload, browser-based
- Step 1Open the tool (no account needed to convert) — The page loads the FFmpeg 8.1 WASM engine into your browser. That engine download is the only network activity — after it loads, your file never travels. You can convert without signing in.
- Step 2Drop your confidential WAV — One file per run (
acceptsMultipleis false). The file is written to FFmpeg's in-memory filesystem in the tab — it is read from your disk by the browser locally and is not sent anywhere. - Step 3Confirm nothing uploads (optional but reassuring) — Open DevTools → Network before converting. You'll see the WASM/asset loads, then the conversion runs with no request carrying your audio. This is how you verify the no-upload claim for yourself.
- Step 4Pick a compression level — Default 8 is the sweet spot. The level (0-12 accepted; dropdown offers 0/5/8/12) only changes file size and encode time, never the audio. For confidential archives where size matters, 12 squeezes a bit more.
- Step 5Convert locally and download — FFmpeg re-encodes the PCM with the
flacencoder and-compression_level <n>, entirely on your machine. The output.flacis a local download — bit-identical, ~40-60% smaller, never having left the device. - Step 6Close the tab to clear it from memory — Because processing is in-memory in the tab, closing or reloading the tab discards the working data. Nothing persists server-side because nothing was ever sent there.
Server-upload converter vs. this in-browser tool
Where your confidential audio actually goes during conversion. The distinction is the whole point for sensitive material.
| Aspect | Typical 'online' converter (server) | This tool (in-browser WASM) |
|---|---|---|
| Where the file is processed | Uploaded to a remote server | In your browser tab, locally |
| Audio leaves your device? | Yes — over the network | No — never transmitted |
| Server-side copy exists? | Yes, at least transiently | None — nothing is sent |
| Upload wait on big files | Yes, scales with file size | None — local CPU only |
| Verifiable by you | Hard — you trust their policy | Yes — watch the Network tab |
| Audio fidelity | Lossless (FLAC) either way | Lossless (FLAC), bit-identical |
Sensitive audio scenarios and why no-upload matters
Confidentiality contexts where uploading audio to a third-party server is unacceptable, and how local conversion addresses it.
| Scenario | Confidentiality concern | Why local conversion fits |
|---|---|---|
| Legal recordings / depositions | Privilege, chain of custody | Audio never leaves the device; no third-party copy |
| Medical / therapy session audio | HIPAA-style duty of care | No transmission to a server outside your control |
| Unreleased masters under NDA | Leak risk before release | No upload means no exposure surface |
| HR / internal investigation audio | Employee privacy | Processing stays inside the browser session |
| Source / journalism recordings | Source protection | Nothing transits the network to be intercepted |
Cookbook
Privacy-first conversion patterns. Each keeps the audio on your device while still producing a lossless FLAC.
Verify no upload before trusting it with sensitive audio
Do this once so you believe the claim. The only network traffic should be loading the engine, not your file.
1. Open DevTools -> Network, clear the log 2. Drop deposition_2026.wav onto the tool 3. Click convert Observe: only .wasm / asset loads appear. No request body contains your audio. File never left.
Convert a privileged legal recording locally
Privileged audio should never sit on a third-party server. Convert in-browser, archive the FLAC on your secure storage.
Source: client_interview.wav 16-bit / 48 kHz / 38:00 Level: 8 Output: client_interview.flac ~95 MB (was ~219 MB) Processed in-browser; no server copy exists to disclose.
Work offline once the page is cached
After the WASM engine loads, conversion is local compute. For maximum assurance you can disconnect before converting.
1. Load the tool page (engine caches) 2. Disconnect from the network 3. Convert your sensitive WAV -> FLAC The conversion completes offline, proving the audio is processed entirely on-device.
Archive an NDA master without exposure
An unreleased master must not leak before release. Local FLAC keeps it small for backup with zero transmission.
Source: album_premaster.wav 24-bit / 96 kHz / 4:30 Level: 12 (smallest archive) Output: album_premaster.flac ~87 MB (was ~155 MB) No upload -> nothing to intercept before the release date.
Clear the working data when done
Because processing is in-tab memory, closing the tab wipes it. There is no server cache to also worry about.
After downloading the FLAC: close the browser tab -> in-memory working buffers are released -> no server-side copy ever existed to delete Clean by construction.
Edge cases and what actually happens
WASM engine must load over the network first
By designThe one thing that does cross the network is the FFmpeg 8.1 WASM engine and page assets, loaded when you open the tool — standard for any web app. Your audio is never part of that. Once loaded (and cached), you can even disconnect before converting to prove the file stays local.
Closing the tab mid-conversion
Run lostSince everything runs in-tab memory, closing or reloading during a conversion discards the in-progress job. That's a privacy feature as much as a limitation — nothing persists anywhere. Just keep the tab open until the download completes, then close it to clear memory.
File over the Free 50 MB cap
413 blockedConfidential masters are often large. Free caps a single file at 50 MB; Pro at 200 MB; Pro-media and Developer at 100 GB. The cap is enforced locally on the input WAV — it is not because of any upload, just a tier policy on processing.
Recording longer than the duration cap
RejectedA separate per-file duration limit applies: 30 min Free, 120 min Pro, unlimited on Pro-media and Developer. Long depositions, therapy sessions, or interviews can exceed 30 (or 120) minutes, requiring a higher tier even though nothing is uploaded.
Expecting metadata to be scrubbed for privacy
Carried, not strippedThis converter preserves source metadata via -map_metadata 0 — it does not remove identifying tags. If the WAV embeds names, dates, or device info you need gone, that's a metadata-scrubbing task, not a conversion one. Strip tags separately before sharing; the conversion keeps what's there.
Thinking the FLAC itself is anonymised
Audio is unchangedNo-upload protects the file in transit, but the FLAC contains the same audio (voices, content) as the WAV. It is lossless, not redacted. If you need to remove spoken PII from the audio itself, that is a different task — see pii-redactor for audio PII handling.
32-bit float source
Converted to integerFLAC stores integer PCM, so a 32-bit float WAV is converted to integer samples — lossless for that form but not a bit-exact float container. This is a fidelity note, not a privacy one; keep the float WAV if exact float data matters.
Browser doesn't support WASM / SharedArrayBuffer
Tool unavailableThe in-browser engine needs a modern browser with WebAssembly support (and the page sets the headers FFmpeg WASM requires). A very old or locked-down browser may not run it. Use an up-to-date Chrome/Firefox/Edge/Safari — the no-upload guarantee depends on the local engine running.
Corrupt or truncated confidential WAV
Decode errorFFmpeg validates the stream locally and errors on a damaged WAV rather than producing a bad FLAC. The failure happens entirely on your device — no file was sent anywhere to fail. Recover the source from backup and retry.
Wanting a copy on another device
Transfer it yourselfBecause nothing is uploaded, there is no cloud copy to access elsewhere — the FLAC exists only where you downloaded it. Move it via your own secure channel (encrypted drive, internal share). That's the trade-off of true no-upload: the file is yours to handle end to end.
Frequently asked questions
Does this tool really not upload my file?
Correct. Conversion runs in your browser via FFmpeg 8.1 compiled to WebAssembly. Your WAV is written to an in-memory filesystem in the tab, encoded, and handed back as a download — no request ever carries the audio. The only network traffic is loading the engine itself, which you can verify in DevTools.
How can I prove nothing was uploaded?
Open your browser's DevTools → Network panel before converting. You'll see the WASM engine and page assets load, then the conversion run with no request body containing your file. For extra assurance, load the page, disconnect from the network, and convert offline — it still works.
Is this safe for legal, medical, or NDA audio?
The no-upload architecture means the audio never leaves your device, so there's no third-party server copy to leak, subpoena, or retain. That addresses the transmission risk for privileged, regulated, or confidential material. You remain responsible for handling the resulting file under your own policies.
Does local processing reduce quality?
No. Local doesn't mean lower quality — FLAC is lossless either way, decoding to bit-identical PCM and ~40-60% smaller. The compression level (default 8, 0-12 accepted) only affects size and encode time, never the audio.
Do I need an account to convert?
No — you can convert without signing in. The feature works the same whether or not you have an account; you don't trade personal data for the conversion. Higher tiers raise the size and duration limits, but the no-upload behaviour is identical at every tier.
Does the FLAC remove identifying metadata from my WAV?
No — the converter preserves source tags via -map_metadata 0; it doesn't strip them. If the WAV embeds names, dates, or device identifiers you need removed, scrub the metadata separately before sharing. No-upload protects the file in transit, not its embedded tags.
Is the audio content itself redacted?
No. FLAC is lossless, so the converted file contains the same voices and content as the WAV — it's not anonymised. To remove spoken PII from the audio itself, that's a separate task; see pii-redactor for audio PII handling. This tool's privacy is about not uploading, not about altering content.
What's the only thing that crosses the network?
The FFmpeg 8.1 WASM engine and standard page assets, loaded when the tool opens — the same as any website loading its code. Your audio is never part of any request. Once the engine is cached, you can convert with the network disconnected.
Can I convert offline?
Effectively yes. Load the page so the WASM engine caches, then disconnect from the network and convert — the conversion completes locally. This is a strong, hands-on way to confirm the audio is processed entirely on your device.
How big a confidential file can I convert?
Free allows 50 MB / 30 min per file, Pro 200 MB / 120 min, and Pro-media / Developer up to 100 GB with unlimited duration. Both limits apply and are enforced locally — they're a tier policy on processing, not a consequence of any upload.
Where does the file go after I close the tab?
Nowhere — the in-memory working data is released when the tab closes, and since nothing was uploaded there's no server cache either. The only persistent copy is the FLAC you downloaded, which lives only on your device. Transfer it yourself via a secure channel if you need it elsewhere.
Can I do the reverse trip privately too?
Yes. The sibling FLAC to MP3 tool also runs entirely in the browser, so making a lossy share copy of a confidential recording stays local as well. The whole JAD audio family uses the same in-browser FFmpeg WASM engine — no upload across the board.
Privacy first
Every JAD Audio tool runs entirely in your browser via FFmpeg (WebAssembly) and RNNoise. Your audio files never leave your device — verified by zero outbound network requests during processing.