Choose your video
Drop an MP4, MOV, WebM, MKV, AVI, M4V, or MPEG file. We check the file locally before conversion.
Your video stays on this device. Processing starts only after you click Convert.
Three steps, no upload
A focused workflow that keeps the file, the processing, and the result on your device.
Drop an MP4, MOV, WebM, MKV, AVI, M4V, or MPEG file. We check the file locally before conversion.
Use MP3 for sharing, WAV for editing, M4A for efficient playback, or Original to avoid re-encoding.
ffmpeg.wasm extracts the audio in a worker. Download the result, then temporary processing memory is released.
Choose with confidence
The best format depends on what happens after the download. This table makes the trade-off explicit.
MP3
Sharing, music players, presentations
Lossy re-encode at your chosen bitrate
WAV
Editing, transcription, archives
Uncompressed PCM output; it cannot restore detail already lost in the source
M4A
Phones, podcasts, efficient libraries
AAC re-encode with strong quality per byte
Original (.mka)
Fast extraction and later editing
Audio packets are copied; no generation loss
Practical rule: choose Original when you want the source audio untouched, WAV before serious editing, MP3 for maximum compatibility, and M4A when file size matters.
Built around the real constraints
The selected video is not uploaded for conversion. WebAssembly processes it inside this browser tab.
Stream-copy mode skips re-encoding, so it is usually the fastest option and introduces no generation loss.
Single-thread mode is the safe default. Compatible isolated browsers can use a faster multi-thread core.
Cancel stops the worker. A finished job revokes old download URLs and closes temporary processing memory.
Made for the next step
The converter is tuned for common tasks, not an endless list of unexplained switches.
Extract interview audio to WAV before cleanup, mixing, or mastering.
Trim a recording and export a compact MP3 or M4A for transcription.
Copy the original track when you need the closest possible source for later work.
Remove the picture and keep a smaller audio file for listening on the move.
Implementation notes
Conversion uses ffmpeg.wasm, a WebAssembly port of FFmpeg. The engine runs in a Web Worker so the page stays responsive. When supported, the selected video is mounted read-only through WORKERFS instead of being copied into the worker's memory file system; a memory copy is the compatibility fallback. The result is returned as a browser Blob for download. We do not receive either file. Browser conversion is slower than native desktop FFmpeg and still needs output memory, so the first release limits input to 300 MB, blocks risky output estimates, and handles one file at a time.
Format, quality, privacy, trimming, performance, and compatibility answers without vague promises.
No. Conversion runs in this browser with ffmpeg.wasm. The selected video and converted audio are not sent to our server. Standard hosting or optional analytics may still receive normal page-request data, never the file contents.
The first release accepts MP4, MOV, WebM, MKV, AVI, M4V, MPEG, and MPG. A container can hold unusual codecs, so a valid extension does not guarantee that every file can be decoded by the browser build of FFmpeg.
Choose MP3 for broad compatibility, WAV for editing, M4A for efficient AAC audio, or Original when you want to copy the source audio without re-encoding.
No. WAV avoids another lossy compression step, but it cannot recreate detail already removed by AAC, MP3, Opus, or another source codec. It is useful because editors handle PCM predictably.
It copies the first audio stream into an MKA container with no audio re-encoding. This is usually faster and preserves the encoded source quality, but MKA is less universally supported than MP3 or M4A.
Yes. Set start and end times before conversion. Re-encoded MP3, WAV, and M4A cuts are precise for normal use; Original mode follows source packet boundaries and may differ by a fraction of a second.
WebAssembly runs on your device and is slower than native FFmpeg. Video length, source codec, output format, CPU, memory, and whether multi-thread mode is available all affect speed.
The current limit is 300 MB because browser conversion may hold the input, engine, and output in memory at the same time. Shorter files are more reliable on phones and older devices.
Yes. Cancel terminates the processing worker and releases its temporary file system. You can then choose another file or start again.
It works in current mobile browsers for modest files. Mobile memory limits vary, so long or high-resolution videos may fail even when they are below 300 MB. A desktop browser is safer for large jobs.