Initializing... drag & drop files here
Supports: ARW
You have a burst, a bracket, or a timelapse sequence sitting in a folder of Sony .arw files, and you want it to play as one looping image you can drop into a page or a chat. This walks through building that animation: how frame order is decided, what the frame rate control actually does to the length of the loop, why APNG rather than GIF for photographic frames, and where the conversion falls short. A single ARW works too — with nothing to animate it comes back as an ordinary static PNG — but the tool earns its keep on sequences.
Two things confuse people on their first run, and both come down to the same design: this converter applies one uniform interval to every frame.
DSC0xxxx numbering.1 ÷ frame rate seconds.That gives you three usable patterns. For a hand-held burst that should look like motion, stay at 10 FPS or move up to 15–30 FPS. For a timelapse where each frame is its own photograph, drop to 2 FPS or 1 FPS so viewers can actually see each shot. For a product turntable or a before/after pair, 5 FPS reads as deliberate rather than jittery.
| FRAMERATE setting | Each frame is held for | 12 frames play for | Reads as |
|---|---|---|---|
| 1 FPS (Slideshow) | 1 s | 12 s | Distinct photographs |
| 2 FPS (Slow) | 0.5 s | 6 s | Timelapse steps |
| 5 FPS | 0.2 s | 2.4 s | Deliberate, flip-book |
| 10 FPS (Recommended) | 0.1 s | 1.2 s | Motion, still readable |
| 15 FPS | ≈0.067 s | 0.8 s | Smooth movement |
| 30 FPS (Smooth) | ≈0.033 s | 0.4 s | Video-like |
| 50 FPS (Max Speed) | 0.02 s | 0.24 s | A blur unless you have many frames |
| Property | APNG | GIF |
|---|---|---|
| Colour depth | 24-bit, ~16.7 million colours | 8-bit, 256 colours per frame |
| Transparency | 8-bit alpha channel | 1-bit, on or off |
| Compression | Lossless (DEFLATE, same family as PNG) | Lossless, but only after the palette is crushed |
| Photographic skies and skin tones | Reproduced smoothly | Visible banding and dithering |
| Specification status | Part of the PNG specification, Third Edition (W3C Recommendation, 24 June 2025) | GIF89a, unchanged since 1989 |
| Browser support | About 96% of tracked usage per caniuse; Chrome 59+, Firefox 3+, Safari 8+, Edge 79+ | Effectively universal |
| Where unsupported | Falls back to displaying the first frame | Not an issue |
| File size on photo frames | Large — nothing is thrown away | Smaller, because most of the colour is thrown away |
That trade is the whole reason to pick APNG here. A demosaiced Sony raw frame is a full-colour photograph, and forcing it through a 256-colour palette is exactly the kind of image GIF handles worst.
Add every frame before converting and leave "Combine?" on "Single animation." Each Sony raw becomes one frame in upload order, and the FRAMERATE value sets how long each is held. There is no separate "build animation" button — the merge behaviour is what that control decides.
No. ARW stores unprocessed sensor data — 12-bit on the earliest Alpha bodies, 14-bit on later ones — with the latitude to recover highlights and reset white balance afterwards. APNG is an 8-bit-per-channel format, so each frame is demosaiced and tone-mapped down to finished sRGB before it goes in. Keep the original .arw files as your editable masters; the APNG is a delivery copy.
Not from an ARW source. APNG carries a full 8-bit alpha channel, but a camera raw is an opaque sensor capture with no alpha to inherit, so every frame is fully opaque. Transparency only matters when the source already has it — starting from PNG to APNG preserves alpha through the conversion.
Because APNG throws nothing away. GIF reduces every frame to 256 colours before compressing, and video codecs discard detail and encode only the differences between frames. APNG stores full 24-bit colour losslessly, frame after frame, which is exactly what makes it look right on photographs and exactly what makes it heavy. Lowering the output resolution is the practical fix; compressing the APNG afterwards is the other.
Not on this page. The APNG format itself supports a per-frame delay, but this converter applies a single interval from the FRAMERATE dropdown to every frame. If you need variable timing — a long opening frame, quick middles — build the animation in a dedicated editor instead.
Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, and current Opera all animate APNG natively, which covers roughly 96% of tracked browser usage according to caniuse. Anywhere the animation chunks aren't understood, the file degrades gracefully to its first frame as a normal PNG, so a viewer always sees a valid image rather than a broken one.
It is official now. APNG started as a Mozilla extension to PNG in the mid-2000s and was long treated as unofficial, but it is written into the PNG specification's Third Edition, published as a W3C Recommendation on 24 June 2025, which also registers the image/apng media type. Its ancillary chunks are ignored by older decoders, which is why it stayed backwards-compatible the whole time.
APNG when the frames are photographic and colour accuracy matters — which is the usual case for rendered Sony raws. ARW to GIF when you need something that plays absolutely everywhere and can live with a 256-colour palette. ARW to MP4 when the sequence is long: a video codec will produce a far smaller file than any lossless animated image, at the cost of not being an image any more.
Files are uploaded over an encrypted connection, rendered and assembled on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. Raw files are big, so the slow part of a long sequence is getting the frames up to the server rather than the conversion itself.