ARW to HEVC Converter

ARW to HEVC Converter

An ARW is a Sony Alpha RAW photo — a single, high-bit-depth still straight off the sensor — and HEVC (H.265) is a video codec. The .hevc file this tool writes is a Matroska (MKV) container holding an H.265 video stream — only the extension is unusual. Converting one isn't a like-for-like swap — there is no video inside an ARW, so the tool renders the photo and writes a short, silent H.265 clip that holds that single frame on screen for a set duration (silent because a photo has no audio to carry over). None of HEVC's motion-compression advantage applies to one still, and the unusual .hevc extension confuses software that judges files by name. The tables below explain both formats. Most people who land here actually want a normal photo — ARW to JPG is the right tool for that — and if you genuinely want the still as a playable clip, ARW to MP4 writes H.264 inside an MP4, which plays far more widely in stock phone, TV, and browser apps than a Matroska file.

ARW Format at a Glance

HEVC (H.265) Format at a Glance

How to Convert ARW to HEVC

1. Upload Your ARW File: Drag and drop your ARW onto the page or click "+ Add Files". You can queue several at once — RAW files are large, so the main wait is the upload, not the conversion.
2. Set Merge strategy and Image Duration: Choose Merge images to combine every uploaded ARW into one HEVC stream, or Video per image for a separate file each. Then set Image Duration (default 5 seconds per frame) to control how long each photo stays on screen.
3. Pick Background Color and Quality Preset: Background Color (default White) fills the letterbox bars when your photo's aspect ratio differs from the video frame. Leave Quality Preset on Very High (Recommended), or choose a Video Resolution preset to cap the output size.
4. Convert and Download: Click "Convert" and download your HEVC file. No sign-up, no watermark. The output is silent by design.

Frequently Asked Questions

What actually happens when I convert a single ARW to HEVC?

The tool demosaics the RAW, renders it to a normal image, then encodes that one frame as an H.265 stream that displays for the Image Duration you set. The result is a freeze-frame: no panning, no animation, and no sound. An ARW is one photograph, not footage, so there is no motion to carry over — and that matters here, because HEVC's whole reason to exist is compressing motion between frames. With a single still there is no inter-frame redundancy to exploit, so you pay HEVC's slow, heavy encode and get none of its benefit. To build a real moving sequence you need several ARWs merged together; to add audio, convert first and add a track in any video editor.

Why does the HEVC output have no audio track?

Because the source is a still image: an ARW is a photograph with no audio to begin with, so there is simply nothing to carry over. The .hevc file is actually a Matroska (MKV) container, which could hold an audio track perfectly well — but for image sources the tool hides the audio codec menu entirely and writes a video-only, silent file. If you need sound, convert the ARW first, then combine your clip and an audio file in a video editor or with a tool like FFmpeg.

Why is .hevc an odd target for a single photo?

Three reasons. First, no gain: wrapping a still in HEVC adds no detail — it is the same rendered pixels, just encoded with a slow, patent-encumbered codec built for video. Second, lost resolution: a 24-61 MP ARW is scaled down to a standard video frame, so most of the sensor data is discarded by design. Third, playback friction: the file is a Matroska (MKV) container carrying an unusual .hevc extension, so extension-driven software may not recognize it (renaming it to .mkv helps), and stock Apple apps do not play Matroska at all. If your aim is the picture, ARW to JPG is far better; if you need a playable clip, ARW to MP4 gives you H.264 in an MP4 that plays more widely.

Will I lose image quality going from a RAW ARW to HEVC?

Yes, substantially, and it is inherent to the conversion rather than a tool flaw. An ARW stores 12- to 14-bit, unprocessed sensor data that must be demosaiced and tone-mapped to become viewable; that render bakes in white balance, exposure, and color, so the RAW editing latitude — the whole reason to shoot ARW — is gone once it is a video frame. On top of that, a 24-61 MP RAW is scaled down to a standard video frame, discarding most of the resolution. The HEVC encode adds its own lossy compression on top. Always keep the master ARW — the HEVC file is a throwaway delivery file, not an archive.

How is .hevc different from H.265 inside an MP4 or MOV?

The codec is the same — H.265 — but the packaging differs. The .hevc file this tool writes is a Matroska (MKV) container holding the H.265 stream, with normal timestamps, duration, and working seek; only the extension is unusual, so extension-driven software may not recognize it (renaming it to .mkv helps). An MP4 or MOV wraps H.265 in a container that stock phone, TV, and browser apps accept far more readily — QuickTime and other stock Apple apps do not play Matroska at all — so it plays far more widely. If you want H.265 you can actually play, ARW to MOV wraps it in a QuickTime container; for the broadest compatibility, ARW to MP4 writes H.264, which every device decodes without a licensing or codec-support gap.

Should I really convert ARW to HEVC, or to JPG or MP4 instead?

For almost every purpose, JPG or MP4. To view, print, share, or upload the photograph, ARW to JPG gives a universal image that opens everywhere, and for lossless 8-bit output use ARW to PNG. If you genuinely need the still as a playable clip, ARW to MP4 produces an H.264 file that plays on phones, browsers, and modern editors without HEVC's licensing and playback friction. Reach for the .hevc target only when a specific pipeline or device explicitly asks for that extension — for anything else it is the least convenient of the options.

Can I turn several ARW photos into one moving HEVC clip?

Only as a slideshow, not real footage. Choose Merge images and the tool concatenates your uploaded ARWs into one H.265 stream, holding each photo for the Image Duration you set. But the result is a run of static freeze-frames cut end to end — there is no panning, motion interpolation, or animation between shots, because every frame is still a single rendered RAW. For genuinely moving video you need actual footage as the source, not a stack of stills.

What happens to my uploaded ARW file after conversion?

Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after the conversion — no sign-up, no watermark, never shared or made public. In practice, a single 24-megapixel ARW converted at the default 5-second duration comes out as a short, silent Matroska (MKV) file carrying the .hevc extension: VLC, mpv, and other FFmpeg-based players open it directly with working seek, extension-driven software may need it renamed to .mkv, and stock Apple apps — which do not play Matroska — want an MP4 instead.