MOV to MP3 Converter

No. The conversion runs entirely in your browser. We decode your file using the Web Audio API and re-encode it using a JavaScript encoder library, all in your browser tab. Open DevTools while you convert — you'll see zero traffic carrying your audio.

No fixed limit from us. The real ceiling is your device's memory: decoded audio sits in RAM as raw PCM, which is roughly 10 MB per minute of stereo audio at 44.1 kHz. A typical 5-minute song needs about 50 MB of working memory — fine on any modern phone or laptop. Hour-long podcasts may struggle on older devices.

MP3 is a lossy format, so encoding to MP3 always involves some quality loss compared to the source. At 192 kbps (our default), the difference is inaudible to most listeners on most playback hardware. WAV is lossless — if you're converting TO WAV, the output is bit-identical to what your source decoded into. If you're converting FROM a lossy source (MP3, M4A), the WAV won't be higher quality than the source — it'll just be uncompressed.

Decoding is near-instant. Encoding speed depends on output format: WAV is essentially instant (just writing bytes). MP3 takes about 1 second of compute per 10 seconds of audio on a modern laptop — so a 5-minute song encodes in roughly 30 seconds. Phones are slower; expect 2-3x longer. Progress is shown live as the encoder works.

Yes. Tap the drop zone to open the file picker, choose your audio file, hit Convert. The result downloads to your device's standard download location. iOS users: the file lands in the Files app under Downloads.

Original ID3 tags are not preserved in v1 — the encoded file gets no metadata. The audio itself is preserved exactly. If you need to keep artist/album/title info, you'll want to re-tag the output with a tool like MP3Tag (Windows) or Kid3 (cross-platform) after converting.

Almost nothing on the inside. MOV is Apple's original QuickTime format from the early 1990s; MP4 is the open standard that grew out of it (the MPEG-4 spec borrowed heavily from QuickTime's design). The container structures are nearly identical, audio is usually the same AAC codec, and most software treats them interchangeably. The main practical difference: file extension and which apps default to which. iPhone used to record .mov, now records .mp4. Mac screen recordings still output .mov. Either works fine here.

Yes — recent iPhone screen recordings output .mov files, and they work directly here. AirDrop or sync the .mov to your computer, drop it here, get an MP3 of the audio. Useful for capturing audio from voice memos that were recorded inside an app, podcast clips played during a screen recording, or any other audio embedded in iPhone screen captures.

GoPros record in MP4 by default, but some older models and certain settings produced .mov. Either way, drop the file here — both formats use the same audio extraction path. The conversion focuses on the audio track only, so it's quick even on long action-camera files.

Soft limit around 500MB on desktop, 200MB on phone — above that the browser may run out of memory loading the file. If you hit a limit, compress or trim the video first. The conversion time depends on audio length, not file size, so a tightly compressed 100MB MOV and a loose 400MB MOV of the same duration finish in about the same time.

ffmpeg.wasm is 30MB+ to download per user, requires special browser headers (COOP/COEP) that break analytics and ads, and isn't needed for audio extraction — modern browsers already decode MOV audio natively via the Web Audio API. We use that built-in decoder instead. Result: tiny page, fast start, works on more devices.

Anything purchased from the iTunes Store or other DRM-protected MOV won't convert — the decoder refuses to read the audio, and we'd surface a generic error. This is normal copy-protection behavior; it works the same way for every browser-based converter. There's no workaround that we'd build into this tool.