Initializing... drag & drop files here
Supports: RAF
Drop a run of .raf files from an interval timer, a bracketing burst or a stop-motion setup and get back one looping animated PNG — full 24-bit colour, no 256-colour palette, no round trip through a raw editor first. Most APNG makers refuse raw camera files outright and expect you to export PNGs by hand; this page decodes each Fujifilm raw on our servers and assembles the frames directly. Upload one RAF and you get a single still image instead; the animation needs at least two files.
.raf files onto the page or click "+ Add Files". Upload order is playback order, so sort them before you add them. Only .raf inputs are accepted here..apng. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. No sign-up, no watermark.APNG stores each frame's delay as an exact numerator/denominator fraction, so the frame rate you pick is the frame rate you get. GIF cannot do this — it stores delays in hundredths of a second, so anything that is not a whole number of centiseconds is silently rounded. Every APNG produced here loops forever; the loop count is not adjustable.
| Framerate setting | Per-frame delay | 24 RAF frames run for | Typical use |
|---|---|---|---|
| 50 FPS (Max Speed) | 0.02 s | 0.48 s | High-speed burst played back fast |
| 30 FPS (Smooth) | 0.0333 s | 0.80 s | Cine-style motion |
| 25 FPS | 0.04 s | 0.96 s | PAL-style cadence |
| 20 FPS | 0.05 s | 1.20 s | Smooth but not frantic |
| 15 FPS | 0.0667 s | 1.60 s | Web loops |
| 12 FPS | 0.0833 s | 2.00 s | Classic animation cadence |
| 10 FPS (default) | 0.10 s | 2.40 s | Interval-timer sequences |
| 8 FPS | 0.125 s | 3.00 s | Deliberate, readable motion |
| 5 FPS | 0.20 s | 4.80 s | Slow reveal |
| 2 FPS (Slow) | 0.50 s | 12.00 s | Before/after comparisons |
| 1 FPS (Slideshow) | 1.00 s | 24.00 s | Stepping through a bracket set |
| Property | APNG | GIF |
|---|---|---|
| Colour | True colour, 8 bits per channel from this pipeline | 256-colour palette per frame |
| Transparency | Full alpha channel | 1-bit, on or off |
| Compression | Lossless | Lossless, but palette-limited |
| Frame timing | Exact fraction (1/N second) | Rounded to hundredths of a second |
| Photographic gradients | Clean skies and skin tones | Dithering and banding |
| Native rendering | Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, Opera 46+ — about 96% of users | Effectively universal |
| Behaviour where unsupported | Shows the first frame as a normal PNG | Plays |
| MIME type | image/apng |
image/gif |
For photographic frames APNG is the better container by a wide margin — a Fujifilm raw is full-colour data, and forcing it through a 256-entry palette is where GIF conversions of photo sequences fall apart. If you specifically need the universal compatibility, use RAF to GIF instead and accept the palette.
Worth knowing before you go hunting for a setting that is not there:
Because there is nothing to animate. A one-frame sequence is duplicated internally so the assembler has two frames to work with, and the assembler then recognises the two frames as identical and collapses them back into one. The result is a valid, plain static PNG carrying an .apng name — no animation control block, no playback. Upload two or more raw files to get a real animation.
Start at the default 10 FPS and adjust from the length you want, not from the look. Divide your frame count by the target duration: 240 frames over 10 seconds needs 24 FPS, so pick 25. If the result stutters it is usually not the frame rate — it is uneven spacing in the original interval capture, which no playback rate can smooth out.
No. APNG itself can store 16 bits per channel, but the raw decoder here develops Fujifilm raw at 8 bits per channel by default and the converter does not override it, so every frame is 8-bit true colour. That is plenty for playback and matches what browsers render anyway, but it means an APNG from this page is not an archival-depth master. Keep the .raf files.
Yes. Chrome 59+, Firefox 3+, Safari 8+, Edge 79+ and Opera 46+ all play APNG natively, which caniuse currently puts at roughly 96% of users. Where it is not supported the file degrades gracefully rather than breaking: viewers see the first frame as an ordinary still PNG. Internet Explorer and Opera Mini are the notable exceptions.
Yes — switch Combine from "Single animation" to "Individual files" and each raw is processed on its own. Since a single image cannot animate, each of those outputs is a static PNG under an .apng name. If that is what you actually want, RAF to PNG is the more honest route.
Two levers, in order of effectiveness. First, resolution: set Preset Resolutions or Width x Height under Image resolution, since halving the long edge removes about three quarters of the pixels in every frame. Second, frame count: upload fewer raws. An APNG is a lossless stack of frames, so its size is roughly linear in frames × pixels.
No. The frames are re-rendered and re-assembled, so shooting metadata does not travel into the animation, and the Film Simulation recorded in the RAF is a rendering instruction rather than baked pixels — a general-purpose raw decode produces a neutral render instead of reproducing Velvia or Acros exactly. Develop in Fujifilm's own software first if a specific simulation is essential.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. If you want the same sequence as a real video file rather than an animated image, RAF to MP4 gives you a slideshow instead, and the RAF converter hub lists every other target.