Initializing... drag & drop files here
Supports: ARW
An ARW is a Sony Alpha RAW photo — a single, high-bit-depth still straight off the sensor — and M4V is Apple's video container, the .m4v variant of MP4 used by iTunes, the TV app, and QuickTime. Converting one isn't a like-for-like swap: there is no video inside an ARW, so the tool renders the photo and holds that single frame on screen as a short, silent clip. 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 do want a playable file, ARW to MP4 writes the very same H.264 video under the universal .mp4 extension that plays everywhere, not just in Apple apps.
| Property | Value |
|---|---|
| Full name | Sony Alpha RAW (camera RAW still image) |
| Based on | TIFF/EP (ISO 12234-2), with Sony extensions |
| Released | 2006, with the Sony α100 DSLR |
| Payload | Unprocessed Bayer sensor data — one frame, no audio |
| Bit depth | 12- or 14-bit per channel (ARW 2.3 onward is 14-bit) |
| Resolution | 24-61 megapixels depending on the Alpha body (α7R series ~61 MP) |
| To view | Must be demosaiced and tone-mapped by a RAW decoder |
| Best for | Editing latitude and archival master files (a digital negative) |
| Property | Value |
|---|---|
| Full name | Apple's MP4 variant (MPEG-4 Part 14 container) |
| Developer | Apple Inc. |
| Container | Same ISO base-media (MP4) structure, .m4v extension |
| Video codec | H.264 (what this tool writes) |
| Audio codec | AAC when present — but an ARW source has no audio, so the output is silent |
| DRM | iTunes-store .m4v can carry FairPlay DRM; the M4V this tool creates is DRM-free |
| Native support | QuickTime, iTunes/TV app, Apple TV, iPhone, iPad |
| Note | Renaming .m4v to .mp4 usually lets non-Apple players open it |
The tool demosaics the RAW, renders it to a normal image, then writes an M4V that displays that one frame 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. To build a real moving sequence you need several ARWs merged together; to add music or narration, convert first and then add an audio track in any video editor.
M4V is Apple's flavour of the same MPEG-4 container — the structure is essentially MP4 with a .m4v extension. Apple uses it so the operating system can apply FairPlay DRM to purchased iTunes content, but a file you create yourself carries no DRM. Because the underlying video is identical, an M4V usually plays in non-Apple players the moment you rename it to .mp4. If you want a file that just works everywhere without renaming, use ARW to MP4; choose M4V when you are staying inside Apple apps like the TV app, QuickTime, or an iOS workflow that expects the .m4v extension.
No — it is silent. An M4V container normally pairs H.264 video with an AAC audio track, but an ARW is a still photo with no sound to encode, so the tool hides the audio codec entirely for image sources and writes a video-only file. If you need a soundtrack, convert the ARW to M4V first, then drop the clip and your audio into any editor (iMovie, Final Cut, Premiere) and export.
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 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 an M4V frame (standard-definition-to-1080p class), discarding most of the resolution. Always keep the master ARW — the M4V is a delivery file, not an archive.
H.264, inside the standard .m4v (MP4) container — the same codec ARW to MP4 writes, which is exactly why the two files are interchangeable once you swap the extension. H.264 is what Apple devices decode natively, so the M4V plays in QuickTime, the TV app, and on iPhone or iPad without any extra codec download. The tool does not output HEVC for .m4v; if you specifically want HEVC, ARW to MOV exposes that codec choice.
No. EXIF — camera body, lens, focal length, aperture, shutter, ISO, GPS — lives in the ARW's image metadata block, and an M4V video container has no equivalent place for it. The render discards that information; the M4V stores only the picture and standard video stream tags. If you need the metadata to survive, convert to ARW to JPG instead, which carries the EXIF block into the output.
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 the same H.264 file under the universal extension. Reach for M4V only when an Apple-specific workflow expects the .m4v extension — otherwise MP4 saves you the eventual rename.
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 our testing, a single 24-megapixel ARW converted at the default 5-second duration produced a short, silent H.264 M4V that opened in QuickTime and the Apple TV app, and that played in VLC unchanged after we renamed it to .mp4.