Convert HEVC to M4A — Free Online Tool
Extract audio from HEVC/H.265 video files and save it as M4A with AAC encoding — perfect for pulling soundtracks, dialogue, or music from high-efficiency video files into a compact, iTunes-compatible audio format. The video stream is discarded entirely, and the extracted audio is encoded to AAC at 128k bitrate by default.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your HEVC file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
HEVC (.hevc) files contain a raw H.265 video bitstream, and while they sometimes carry an embedded audio track, the primary goal of this conversion is to extract that audio and repackage it into an M4A container. Because a raw .hevc file does not share a codec with the M4A audio container, FFmpeg discards the video stream entirely using the -vn flag and encodes the audio to AAC — the native codec of M4A — at 128k bitrate. The result is an MPEG-4 audio file that is fully compatible with Apple devices, iTunes, and any AAC-capable player. No video data survives the conversion, so the output file is dramatically smaller than the source.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool — in this browser-based tool, it runs as a WebAssembly binary (FFmpeg.wasm) entirely within your browser without uploading your HEVC file to any server. |
-i input.hevc
|
Specifies the input file — a raw HEVC/H.265 elementary stream. FFmpeg reads this file to locate any embedded audio track that will be extracted and re-encoded into the M4A output. |
-c:a aac
|
Sets the audio encoder to AAC (Advanced Audio Coding), the native and universally compatible codec for the M4A container format, ensuring the output plays correctly on Apple devices, iTunes, and virtually all modern media players. |
-b:a 128k
|
Encodes the AAC audio at a constant bitrate of 128 kilobits per second — a standard quality level suitable for most music and voice content. Increase this value (e.g., 256k) for higher fidelity, or reduce it (e.g., 96k) to produce smaller files for speech-only content. |
-vn
|
Disables video output entirely, instructing FFmpeg to discard the H.265 video stream from the HEVC source. This is essential for producing an audio-only M4A file, and it is what causes the dramatic reduction in file size compared to the original HEVC input. |
output.m4a
|
Defines the output filename and format. The .m4a extension tells FFmpeg to wrap the encoded AAC audio in an MPEG-4 audio container, producing a file that is natively recognized by iTunes, Apple Music, iOS, and any AAC-compatible audio player. |
Common Use Cases
- Extract the audio commentary or narration track from an H.265-encoded video to distribute as a standalone podcast or lecture recording
- Pull the music or soundtrack from an HEVC-encoded film clip into an M4A file for use in an iTunes or Apple Music library
- Convert a raw H.265 camera recording to M4A so the audio can be imported into GarageBand or Logic Pro for further editing
- Strip audio from an HEVC video captured on a modern smartphone (which records in H.265 by default) to create a ringtone or notification sound compatible with iOS
- Archive just the spoken-word audio from an HEVC video interview as a lightweight M4A file for transcription or captioning workflows
- Extract audio from an HEVC broadcast recording and save it in M4A format for playback on iPods or other Apple hardware that requires AAC in an MPEG-4 container
Frequently Asked Questions
Not necessarily. A raw .hevc file is a bare H.265 bitstream and may contain only video data with no embedded audio. If your file has no audio track, FFmpeg will produce an empty or zero-byte M4A output and may display a warning about no audio streams found. If your HEVC content came wrapped in a container like MKV or MP4, you should use the appropriate input format (MKV or MP4) rather than the raw .hevc format for reliable audio extraction.
If the source audio is already compressed (e.g., AC-3, DTS, or AAC), re-encoding it to AAC introduces a generational quality loss — you are decoding a lossy format and re-encoding to another lossy format. At the default 128k bitrate, the result is perfectly acceptable for speech and most music, but audiophiles may prefer bumping the bitrate to 256k or 320k. If you want truly lossless output, you can change the codec to FLAC within the M4A container, though FLAC in M4A has limited player support compared to AAC.
Replace the value after -b:a in the command. For example, to encode at 256k instead of the default 128k, use: ffmpeg -i input.hevc -c:a aac -b:a 256k -vn output.m4a. Higher bitrates produce larger files with better audio fidelity. For spoken word content 96k is usually sufficient, while 192k–256k is recommended for music. The maximum meaningful bitrate for AAC is generally considered to be 320k.
M4A technically supports other codecs such as FLAC, Opus (libopus), and Vorbis (libvorbis), but AAC is the only codec that has universal compatibility with the M4A format across Apple devices, iTunes, and mainstream media players. If you encode with FLAC in M4A you get lossless audio but reduced device support. Opus in M4A is largely experimental and may not play back correctly on iOS or macOS. For broadest compatibility, stick with the default AAC codec.
The dramatic size reduction happens because the video stream — which accounts for the vast majority of data in an HEVC file — is completely discarded by the -vn flag. You are left with only the audio track, encoded to AAC at 128k. Even a 2GB HEVC video file might produce an M4A of just a few megabytes if the audio is a short clip, or tens of megabytes for a feature-length audio track. This is expected behavior and not a sign of data corruption.
M4A supports chapter markers and iTunes-style metadata tags, but a raw .hevc file typically carries very little metadata to begin with. Basic tags like title or artist are unlikely to be present in a bare HEVC bitstream. FFmpeg will pass through whatever metadata exists in the source, but do not expect rich tagging in the output. If you need to add chapters or ID3-style metadata to the resulting M4A, you can do so with a separate FFmpeg pass or a dedicated tagging tool like Mp3tag.
Yes. On Linux or macOS you can use a shell loop: for f in *.hevc; do ffmpeg -i "$f" -c:a aac -b:a 128k -vn "${f%.hevc}.m4a"; done. On Windows Command Prompt the equivalent is: for %f in (*.hevc) do ffmpeg -i "%f" -c:a aac -b:a 128k -vn "%~nf.m4a". The browser-based tool on this page processes one file at a time, but the FFmpeg command is ideal for bulk processing large collections on your local machine.
Technical Notes
Converting a raw HEVC bitstream to M4A is fundamentally an audio extraction operation: FFmpeg reads the .hevc file, ignores the H.265 video payload, decodes the audio stream, and re-encodes it as AAC inside an MPEG-4 audio container. One important caveat is that .hevc as a container format is quite bare — it is essentially a demuxed video elementary stream and audio tracks may be absent or non-standard. If your source material originated as an MKV, MP4, or TS file containing H.265 video, you will get more reliable results working from that original container. The AAC encoder used here is FFmpeg's built-in native AAC encoder, which produces compliant LC-AAC output suitable for all Apple platforms and most modern players. M4A does not support multiple audio tracks, so only the first detected audio stream from the source will be encoded. Metadata support in M4A is robust for iTunes-style tags (title, artist, album, artwork), but since raw HEVC files carry minimal metadata, the output M4A will likely require manual tagging. Transparency and subtitle streams are unsupported by both the HEVC input format and the M4A output format in this pipeline, so no data of that type will be present in the output.