Initializing... drag & drop files here
Supports: ARW
This walks a Sony shooter through turning a .arw raw file into a small, web-ready AVIF — when it is the right move, the two settings that actually change the result, and the gotchas that trip people up. The short version: convert a copy to AVIF for the web and keep the original .arw as your editable master, because the conversion bakes in the render and the raw editing latitude does not survive it.
.arw onto the page or click "+ Add Files" to browse. You can queue several Alpha raw frames at once — straight off an α7, α6000-series, or older DSLR-A body.The raw is demosaiced and rendered to ordinary pixels first, then AVIF-encoded, so "Quality Preset" is the single biggest lever on both the look and the weight of the result. AVIF degrades gently — at lower quality it tends to soften and smear fine texture rather than throw up the blocky squares JPEG produces — so you can push the preset down further than you would dare with JPEG before anyone notices.
| Property | ARW (source) | AVIF (output) |
|---|---|---|
| What it is | Sony Alpha camera raw still | AV1 Image File Format still |
| Container | TIFF-based raw wrapper | HEIF / ISOBMFF (ISO/IEC 23008-12) |
| Payload | Unprocessed mosaic sensor data | AV1-coded picture |
| Published by | Sony (proprietary) | Alliance for Open Media, royalty-free |
| Bit depth | Typically 12-bit or 14-bit per channel | 8, 10 or 12-bit supported by the format |
| Editing latitude | Full — white balance and exposure recoverable | None — the render is baked in |
| Alpha channel | No, an opaque sensor capture | Supported by the format, unused here |
| Typical size, 24 MP frame | Tens of megabytes | A small fraction of the raw |
| Best for | Master archive and re-editing | Web delivery, app assets, sharing |
| Environment | Status |
|---|---|
| Chrome | Supported since version 85 |
| Firefox | Supported since version 93 |
| Safari | Supported since version 16.4 |
| Edge | Supported since version 121 |
| Browser users worldwide | About 94.7% can display AVIF, per caniuse |
| Desktop viewers and editors | Uneven — recent macOS and Windows builds and current image editors handle it, older ones often cannot |
.arw and expected to keep editing it." A converted AVIF is a finished picture, not raw data — there is no editing latitude left in it. Keep the .arw and convert copies as needed.AVIF is a delivery format, so it is the wrong target whenever you still need the raw's headroom or maximum reach. If you plan to recover highlights, reset white balance, or push exposure, do not convert yet — keep the .arw master and edit that. If you need a print-ready or lossless editing file, render ARW to TIFF for high-bit-depth, lossless output instead. And if the file has to open on anything and everything — email, older phones, any viewer — ARW to JPG is the safe, universal choice. There is no motion or hidden layer to extract from an ARW; it is a single still frame, so this page exists to render and compress that one frame, not to recover something that was never in the file.
Yes. An ARW stores unprocessed sensor data — typically 12-bit on early Sony Alpha bodies and 14-bit on most modern α models — which is why you can recover highlights and shadows and reset white balance long after the shot. To write an AVIF, the converter demosaics that data and bakes in the current white balance, exposure, and tone. Once it is an AVIF you are editing a finished image, not the raw. Adjust in a raw editor first if you want control, then convert the result, and keep the .arw as your master.
Not in the sense the question usually means. ARW holds unprocessed sensor data with wide editing latitude; AVIF holds a rendered, compressed picture. The visible result can look excellent — often indistinguishable from the raw at normal viewing sizes — but the editing headroom is gone. For a faithful, web-ready copy AVIF is an excellent target; for anything you may re-edit, keep the original .arw.
Size at a given quality. At similar perceived quality, AVIF files are commonly around 30-50% smaller than JPEG, and AVIF degrades more gracefully — its artefacts look like soft blur rather than JPEG's blocky edges, which shows up most across skies, gradients, and fine texture. The trade-offs are encoding speed and reach: AVIF takes longer to encode, and a small share of browsers and older desktop apps cannot display it. If universal compatibility matters more than file size, ARW to JPG is the safer choice.
Yes — that is what the "Specific file size" control is for. Enter a number and choose Bytes, Kilobytes, or Megabytes, and the encoder works toward that ceiling instead of a fixed quality level. Leave "Auto Scale" on if you want the converter to also reduce the pixel dimensions when your target is too small to reach by compression alone; a 3 MB target on a 60-megapixel frame at full resolution is asking a lot of any encoder.
The AVIF format supports both an alpha channel and high dynamic range with wide colour gamut at 10 or 12 bits — that is one of its real advantages over JPEG. Neither applies to this conversion in practice, though: an ARW is an opaque sensor capture with no transparent areas, so there is nothing to make transparent, and the output here is a standard-dynamic-range delivery copy rather than an HDR-graded master. If you need a wide-gamut, high-bit-depth file for editing or print, render ARW to TIFF instead.
In browsers, AVIF works in Chrome 85+, Firefox 93+, Safari 16.4+, and Edge 121+ — about 94.7% of browser users worldwide can display it, per caniuse. Outside the browser the picture is patchier: recent macOS and Windows builds and current image editors handle AVIF, while some older viewers and utilities cannot open it at all. If you are handing the file to someone on an unknown setup, JPEG remains the safest bet.
Because AVIF is a still image wrapped in AV1, a modern video codec, and AV1 spends far more computation searching for an efficient encoding than JPEG's decades-old transform does. That search is exactly what buys the smaller file. It matters most when you queue a batch of full-resolution Sony raws — each frame is tens of megapixels going through both a raw render and an AV1 encode. Downscaling first, when you do not need full resolution, is the quickest way to cut the wait.
It is uploaded over an encrypted connection, rendered and encoded on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public. The AVIF you download is yours; nothing is kept. Because Sony raws are large, the slowest part of the job is usually sending the file rather than encoding it, so if you are working through a shoot, convert in smaller batches rather than one enormous queue.