Initializing... drag & drop files here
Supports: HEVC, MOV, MP4, M4V, MKV
This walk-through is for anyone holding a raw .hevc file — the bare H.265 elementary stream an encoder, capture card, or ffmpeg command spits out — who needs it inside an .AVI container for an old Windows editor or a legacy player that only accepts .avi. Two things about this conversion catch people off guard, so they come first: a raw .hevc stream is video only, with no audio track, which means the AVI you get back is silent; and AVI is a 1992 container that was never built to carry H.265, so the video is re-encoded into an older codec rather than copied. Both are explained below, along with when you should pick MP4 or MKV instead.
.hevc file onto the page or click "+ Add Files" to browse. You can queue several streams at once; they convert with the same settings in one batch..AVI file. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark.For most people AVI is the wrong target for an H.265 stream. This table shows why, and where AVI still makes sense.
| Property | AVI | MP4 | MKV |
|---|---|---|---|
| Released | 1992 (Microsoft, Video for Windows) | 2001 (ISO/IEC 14496-14) | 2002 (open, Matroska) |
| Carries H.265 without re-encoding | No — forces a transcode | Yes | Yes |
Re-encode from a .hevc stream |
Required (to MPEG-4, H.264, etc.) | No — video is remuxed | No — video is remuxed |
| Typical output size | Largest | Small | Small |
| Multiple audio tracks / subtitles | Limited | Yes | Yes (best) |
| Best for | Old Windows editors or players that demand .avi |
Phones, web, modern devices | Archival and multi-track files |
Because AVI cannot hold H.265, the converter decodes your stream and re-encodes it into an AVI-friendly codec. Which one you choose in the Video Codec dropdown decides both compatibility and file size.
| Codec (in Video Codec) | Best for | Trade-off |
|---|---|---|
| MPEG-4 (default) | Broad playback in classic Xvid/DivX-era Windows tools | Larger than modern codecs |
| H.264 | The smallest AVI at a given quality, if your target decodes H.264-in-AVI | Some legacy AVI tools can't open it |
| Motion JPEG (MJPEG) | Frame-accurate scrubbing in old editors — every frame is stored whole | Very large files |
| Xvid / DivX | Matching a specific DivX/Xvid-era workflow | Dated, lower efficiency than H.264 |
A .hevc file is a raw H.265 video elementary stream — NAL units with Annex B start codes, and nothing else. It carries no audio, no reliable timestamps, and no container metadata. That is why the AVI comes out silent: there is no audio track in the source to carry over. If your footage needs sound, that audio lives in a separate file, so you would mux it back in afterward (with a desktop tool such as ffmpeg or your editor) or, better, convert from the original muxed recording instead of the bare stream.
The codec change is the second half of the story. AVI was designed in 1992, before B-frame codecs were common, and its stream model expects one decoded frame for every stored frame. H.265 leans heavily on B-frames that reference future frames, which AVI was never intended to carry — DivX and Xvid only ever fit inside AVI through a non-standard "packed bitstream" hack, and there is no equivalent for H.265. So this converter decodes the H.265 video and re-encodes it into an AVI-friendly codec. That is a quality-losing transcode, not a lossless copy, so the settings matter:
This tool accepts a bare .hevc elementary stream. Most recordings people call "HEVC" are actually H.265 video wrapped in a container — an iPhone clip is a .mov — and if the uploader rejects your file, it is almost certainly a container, not a raw stream.
| Your file | What it actually is | Right tool |
|---|---|---|
A bare .hevc / .h265 / .265 |
Raw H.265 video elementary stream (picture only, silent) | This page — HEVC to AVI |
An iPhone recording (.mov) |
HEVC video + AAC audio in a MOV container | Convert the .mov directly for sound |
An existing .avi a new tool rejects |
Old container, often DivX/Xvid | convert AVI to MP4 |
.hevc stream contains no audio at all, so there is nothing to place on the AVI's audio track. The sound, if you have it, is in a separate file; mux the two together after conversion, or go back to the original recording that still had audio attached.For almost everyone, AVI is the wrong destination for an H.265 stream. It cannot carry H.265 properly, so the conversion forces a quality-losing re-encode to an older codec and still leaves you without audio. If your goal is simply to make the footage playable or editable in something modern, keep it in H.265: both MP4 and MKV hold H.265 directly, so convert HEVC to MP4 for the most widely supported result, or convert HEVC to MKV when you want a flexible container that also carries multiple audio tracks and subtitles. Reach for AVI only when a specific legacy application or device explicitly demands the .avi extension. If your source is long and you only need a slice, trim the HEVC first, then convert the short clip here.
Because the source has none. A raw .hevc file is an H.265 video elementary stream — video frames only, with no audio track and no container. There is nothing to carry over to the AVI's audio channel, so the output is silent by definition. If your footage had sound, that audio is in a separate file (or in the original muxed recording); mux it back in after conversion, or convert from the recording that still contains the audio.
No, not properly. AVI dates to 1992 and expects one decoded frame per stored frame, whereas H.265 depends on B-frames that reference future frames — a technique AVI was never designed to carry. Forcing H.265 into AVI produces a non-standard file most players mishandle, which is why this converter re-encodes to an AVI-friendly codec instead. To keep H.265 untouched, convert HEVC to MP4 or convert HEVC to MKV — both carry H.265 directly.
Yes. Because AVI cannot carry H.265, the video is decoded and re-encoded into an older codec such as MPEG-4 or H.264, and that re-encode is lossy. How much you lose depends on the codec and Quality Preset you choose. In our testing, the MPEG-4 default at the "Very High" preset with the original resolution kept the loss visually minor; aggressive presets and downscaling are where the softening becomes obvious.
For almost any modern purpose, choose MP4 or MKV. Both carry H.265 directly, so you avoid the quality-losing re-encode that AVI forces, and the files stay smaller and far more widely supported. Pick AVI only when a specific older Windows editor, player, or device requires the .avi extension. For everything else, convert HEVC to MP4 or convert HEVC to MKV.
MPEG-4 (the default) is the safest choice — it is what classic Xvid/DivX-era Windows tools decode without extra codec packs. Choose H.264 instead if your target software supports it and you want smaller files at the same quality. Pick Motion JPEG (MJPEG) only when a legacy editor needs every frame stored independently for frame-accurate scrubbing, and accept that the file will be much larger.
Because H.265 is one of the most efficient video codecs available, while the AVI-friendly codecs it re-encodes to — MPEG-4, H.264-in-AVI, or MJPEG — are far less efficient, and AVI itself adds more per-frame overhead than a modern container. Motion JPEG inflates the file the most because it stores every frame whole. To shrink the result, switch to H.264, drop the Quality Preset a step, or downscale the resolution.
That is the main reason to choose AVI, and the MPEG-4 default is picked for exactly this. AVI is a RIFF-based container recognized by nearly every media player and editor built for Windows, so an MPEG-4 or Xvid/DivX-class AVI opens in classic tools without extra codec packs. If a specific player still refuses it, it is almost always the codec, not the container — re-export with the MPEG-4 Video Codec for the widest compatibility.
Yes. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, and your files are never shared or made public.