Initializing... drag & drop files here
Supports: ARW
Converting a Sony Alpha raw to AVI produces one rendered photograph held on screen as a silent video clip, wrapped in Microsoft's Audio Video Interleave container. The short answer on format choice: pick AVI only when something on the other end specifically demands .avi — an older Windows editing timeline, a legacy capture or playout tool, a submission spec that names the extension. For every other purpose ARW to MP4 gives you a smaller file that plays on far more devices, and if you only want to look at the photograph, ARW to JPG is the honest answer.
| Property | AVI | MP4 |
|---|---|---|
| Origin | Microsoft, 1992, as part of Video for Windows | ISO/IEC standard, based on the ISO base media file format |
| Underlying structure | RIFF chunks | Box/atom structure |
| Default codec on this site | MPEG-4 Part 2 | H.264 |
| Container overhead | Higher, with per-chunk indexing designed for 1990s disks | Lower and more compact |
| Progressive playback over the web | Not what it was designed for | Standard behaviour |
| Playback on phones, browsers, smart TVs | Patchy — often needs a desktop player | Effectively universal |
| Modern extras (variable frame rate, chapters, embedded subtitles) | Limited or bolted on | Native |
| Reason to choose it | A specific legacy tool or spec demands the extension | Everything else |
.avi as its accepted import format and rejects MP4.If none of those describe your situation, AVI is costing you file size and compatibility for nothing. The photograph itself is identical either way — the container is just the box it ships in.
.arw files onto the page or click "+ Add Files." Several can be queued at once, and upload order is the order they appear in the clip.AVI is a container, not a codec, so it has to carry an encoded video stream. The Video Codec dropdown starts on MPEG-4 for AVI output and offers a long list of alternatives — these are the ones worth knowing about.
| Codec option | What it is | Worth choosing when |
|---|---|---|
| MPEG-4 | MPEG-4 Part 2, the ASP family that DivX and Xvid popularised — the default here | You want the classic, widely-readable AVI pairing |
| Xvid / DivX | The same MPEG-4 Part 2 family under their better-known implementation names | A player or device documents DivX or Xvid support specifically |
| H.264 | The modern mainstream codec, far more efficient than MPEG-4 Part 2 | Size matters and the target player is current |
| MJPEG | Every frame stored as an independent JPEG | An editor or instrument wants frame-independent footage |
| HuffYUV | Lossless intra-frame codec; choosing it removes the File Compression control, since there is nothing to trade away | You need a pixel-exact intermediate for another tool |
| MPEG-1 / MPEG-2 | Older broadcast and Video CD era codecs | Matching a legacy pipeline that expects them |
| H.265, VP9, AV1 | Modern high-efficiency codecs | Rarely a good idea in AVI — the container predates them and many players will refuse the combination |
The rule of thumb: the more modern the codec you put inside an AVI, the more you erode the only reason to use AVI in the first place, which is compatibility with old software.
Neither. From one ARW you get a single rendered frame held as a steady picture for the duration you set — no pan, no zoom, no transition — and no audio track, because a photograph has no sound to carry. Upload several photos with Merge strategy on "Merge images" and they play back to back, but each is still a static frame shown for its interval, with a hard cut between them.
MPEG-4 Part 2, the ASP-family codec that AVI files have carried since the DivX and Xvid era. It is the safe default because almost anything that opens an AVI at all can decode it. Change it only for a reason: H.264 for a much smaller file if the target player is current, MJPEG or HuffYUV if a downstream tool needs frame-independent or lossless frames.
Yes, permanently, in the output file. An ARW stores unprocessed sensor data — 12-bit on the earliest Alpha bodies, 14-bit on later ones — which is why highlights, shadows, and white balance stay adjustable long after the shot. Encoding to video requires demosaicing that data into finished pixels and baking in one interpretation. Your original .arw is untouched, so keep it as the master and treat the AVI as a delivery copy.
Two reasons stack up. AVI carries more per-chunk overhead than MP4's box structure, and its default MPEG-4 Part 2 codec is substantially less efficient than the H.264 an MP4 gets. A long-held, full-resolution frame from a high-megapixel Alpha body magnifies both. Shortening the duration, lowering Video resolution, or switching the codec to H.264 all shrink it.
Not reliably. An ARW records sensor data plus the camera's settings, but a Creative Look or picture profile is a rendering instruction that Sony's own pipeline applies — third-party raw renderers do not reproduce it exactly. If the look matters, develop the raw in an editor that reads ARW, export a finished image, and convert that instead.
Because its aspect ratio doesn't match the output frame size, so the converter pads the difference rather than stretching or cropping your picture. The padding uses the Background Color option, which starts on White and offers black plus a long list of named colours. Choosing an output resolution with the same proportions as the photo removes the bars.
Yes. Add them in the order you want and leave Merge strategy on "Merge images" — each photo is held for the Image Duration you set, one after another, in a single file. "Video per image" does the opposite, writing a separate AVI per photo, which is the setting you want for batch conversion rather than a slideshow.
Not obsolete, but legacy. It has been around since 1992 and remains readable by essentially every desktop video tool, which is exactly why it survives in older editing, capture, and playout workflows. What it lacks is everything added since: efficient default codecs, reliable variable frame rate, embedded subtitles and chapters, and dependable playback on phones and in browsers. Use it when something asks for it, not by preference.
Files are uploaded over an encrypted connection, rendered and encoded on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. ARW files often run tens of megabytes each, so on a batch the limiting factor is upload size and connection speed rather than the encode.