Video to MP3 or M4A
Your file stays on this device. No upload and no third-party request.
Temporary output uses private device storage when available (up to 2 GiB, subject to the estimated quota). Memory is the last fallback: 64 MiB. Input: 200 MiB, 5 min, up to 3840 × 2160 or portrait. Operation: 15 min max. GIF excerpt: 15 s max. Requires WebCodecs and workers. Availability depends on the browser and codec. With Safari, audio conversion requires version 26+; codecs still depend on the browser. Direct AAC copying can work without an audio encoder.
Extract the soundtrack from a video you own, without sending it away. Choose a broadly compatible MP3 or keep an existing AAC track in M4A. The original recording stays untouched.
Convert a file in three steps
- Choose a video saved on your device. Check its size and duration before proceeding.
- Select MP3 and its bitrate, or M4A only for an existing AAC track.
- Start the local conversion and keep this tab open. Check the result, then use its download link.
Choose the right audio output
For MP3, choose 128, 192 or 320 kbps. A higher setting uses more space; it cannot restore detail missing from the original soundtrack. For a voice note, test 128 first. For a music rehearsal you recorded, compare a short section at 192 and 320 before choosing. Only the primary audio track is extracted, with no video track in the result.
M4A uses direct copying only when the selected track is AAC. There is no AAC encoder hidden behind this option: if the source is Opus or another codec, the tool refuses M4A and you can try MP3 instead. Copying AAC avoids another lossy audio generation. If the video has no audio track, there is no sound to extract.
Files, privacy and device limits
Choose an MP4, MOV or WebM file already saved on your device. These extensions describe containers, not the codecs inside them. H.264 video with AAC audio and WebM with VP8 and Opus are useful test cases. A MOV recording may use a different codec, including HEVC, so its extension alone does not establish compatibility. The browser checks the actual tracks before starting.
Input is limited to 200 MiB and 5 minutes on touch or low-memory devices, and 1024 MiB and 20 minutes on other desktops. One MiB is 1,048,576 bytes. Up to 3840 × 2160 pixels is accepted, including portrait 2160 × 3840, when the browser can decode the codec. Input size and output memory are different limits: a large file is read progressively rather than copied into one input buffer.
Outputs can use private device storage (OPFS), written in a worker, up to 2 GiB when the estimated quota allows. We reserve 16 MiB and a 25% margin. The quota is checked before conversion and again at startup; it is an estimate, not a guarantee of physical free space. If it is insufficient, use the proposed stronger preset or shorter excerpt. The browser streams the completed file to its download manager without assembling it in a JavaScript buffer. The temporary is deleted when that stream finishes or is cancelled, or when you discard the result. A later visit cleans files left by a crash. Only if file storage is unavailable does memory fall back to 64 MiB on mobile or 64 MiB on desktop. Operation limits are 15 and 30 minutes respectively.
The file never leaves your device. No media upload, account or third party request is used on these tool pages. The site serves its own worker and codec files after you select an accepted file. The result is saved locally, through a download link or directly into the file you choose. It is not a public hosting address. Resetting or leaving releases temporary browser URLs; a file already saved remains where you saved it.
Use material you created or have permission to edit. Local processing does not transfer copyright or remove anyone's rights. Keep your source separately: the downloaded result is a new file, and compression or reencoding can lose detail. Test playback, duration and sound in the app where you intend to use the copy before deleting anything.
Current desktop browsers, Android Chrome and iOS Safari differ in their WebCodecs support. A native video preview may fail even when a track can be copied. If the tool reports an unsupported format or codec, try a supported recording or a desktop editor. It does not install codecs, send the file to a fallback server or retry against another service.
Media choices explained
A video can contain a separate audio track. Turning it into an audio file means either copying that track into a suitable container or encoding it into another format, such as MP3. Copying can preserve the encoded audio exactly; transcoding can improve compatibility but does not improve the original sound. Start with a video you own or have permission to use.
Some recordings are silent or contain no audio stream at all. Others contain several tracks, such as different languages or a commentary. Listen to the video and inspect its track list before choosing an output.
A few useful answers
Does the file get uploaded?
No. The selected video is read and processed locally. The tool downloads its engine from VidFetch, then offers a local output file; it does not upload the recording.
Why is a small file refused?
Size is only one check. Duration, pixel count and the codecs available in your browser also matter. A recording can fit the size cap and still need an unsupported decoder or encoder.
Where is the finished file?
Use the download link when processing finishes. Your browser chooses the download location. On a phone, check Files or Downloads before trying to import a compatible video into Photos or the gallery.