Convert RW2 to APNG Online

Convert RW2 to APNG: What This Tutorial Covers

This walks you through stitching a sequence of Panasonic RW2 raw photos into a single animated APNG, where each RW2 file becomes one frame played in upload order. It is written for LUMIX shooters who captured a burst, bracketed set, or interval timelapse in raw and want a compressed, web-viewable animation that keeps full color and smooth transparency.

How to Convert RW2 to APNG

1. Upload Your RW2 Files: Drag and drop or click "Upload" to add your .rw2 photos. Add them in the order you want them animated — the sequence on the page is the playback order. Each raw file is demosaiced and rendered to an 8-bit sRGB frame on our side.
2. Set the FRAMERATE: Open the options and pick a value under FRAMERATE — 10 FPS is the default and a good starting point; lower it (2-5 FPS) for a slideshow-style timelapse, raise it for smoother motion.
3. Tune Image Quality (%) and Colors: Adjust Image quality (%) (default 80) to balance sharpness against file size, and optionally switch Colors from ORIGINAL to "By Color Reduction + Dither" to shrink the output. You can also scale every frame down with Image resolution or a Preset Resolution.
4. Convert and Download: Click Convert, then download your APNG. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.

Walk-through: Turning a RW2 Sequence Into Frames

The biggest difference between this and a normal photo conversion is that RW2 holds minimally-processed sensor data — Panasonic LUMIX bodies record 12- or 14-bit raw, not a finished image. Before anything can animate, each RW2 is demosaiced (the Bayer sensor data is interpolated into RGB) and rendered down to an 8-bit sRGB frame, since APNG, like all PNG, tops out at 8 bits per channel. That render uses a neutral default; it will not match a custom edit you made in Lightroom or SILKYPIX, so if you have a specific look in mind, develop the raws first and animate the exported stills instead.

Order matters more than any other setting. The converter reads your RW2 files top-to-bottom as they appear in the list and assembles them into one APNG, so a shuffled list produces a shuffled animation. A few patterns that come up often:

• If you shot an interval timelapse, keep the FRAMERATE low (2-8 FPS) so each captured moment is readable; high framerates blur a long day into a flicker.
• If the output looks too large, the raws are the cause — full-resolution LUMIX frames are 12-24 megapixels each. Drop a Preset Resolution first, then lower Image quality (%), then reduce Colors for flat or graphic content.
• If exposures jump between frames, that flicker comes from the camera, not the converter — auto-exposure varied shot to shot. Re-developing the raws with a fixed exposure before animating is the only real fix.
• If you only have one RW2, you will get a one-frame APNG (effectively a static PNG). For a single still, convert RW2 to PNG instead.

Common Errors and How to Fix Them

• "Animation only shows one image" — A browser without APNG support displays just the first frame as a static PNG. The file is fine; view it in Chrome 59+, Firefox 3+, Safari 8+, or Edge 79+ to see the motion.
• "Output file is too large to share" — Raw frames are high-resolution and the APNG stays lossless, so big sequences balloon. Lower the resolution preset, drop Image quality (%), reduce Colors, and use fewer frames at a lower framerate.
• "Colors or white balance look off" — The neutral demosaic render does not apply your in-camera or raw-editor adjustments. Develop the RW2 files first and animate the exported JPEG/PNG stills if you need a specific grade.
• "Frames are in the wrong order" — Re-upload the RW2 files in the intended sequence; the page order is the playback order. Renaming them with zero-padded numbers (001, 002…) keeps long bursts sorted.
• "Transparent areas turned solid" — A camera raw has no alpha channel, so an APNG built from RW2 frames is fully opaque. APNG can carry 8-bit transparency, but only if the source frames already have it.

When This Doesn't Work

A single RW2 produces a single-frame APNG — there is nothing to animate, so use a still-image converter instead. Very new LUMIX bodies occasionally ship a raw variant that open-source decoders do not yet support, in which case the file may fail to decode and should be exported from Panasonic's own SILKYPIX-based software first. And if your goal is the absolute widest playback across old software, an animated GIF still has broader legacy reach than APNG; in that case convert RW2 to GIF instead and accept GIF's 256-color limit.

Frequently Asked Questions

Can I combine multiple RW2 files into one animated APNG?

Yes — that is the point of this tool. Upload several Panasonic RW2 photos and they are stitched into a single APNG, each file becoming one frame in the order you arranged them. A burst, an exposure bracket, or an interval timelapse all work; one RW2 on its own just yields a single static frame.

Will my custom RW2 edits and white balance carry over?

No. RW2 stores minimally-processed sensor data, and the converter renders each raw with a neutral default before animating, so any develop settings you applied in Lightroom, Capture One, or SILKYPIX are not reflected. To keep a specific look, develop the raws first and animate the exported stills. In our testing, a set of LUMIX RW2 frames at default Image quality (%) produced clean, sharp APNG frames that matched the camera's neutral render closely.

Why is my RW2-based APNG so large?

Panasonic LUMIX raw frames are typically 12-24 megapixels and APNG compression is lossless, so an animation built from many full-resolution frames stays big. Drop a Preset Resolution, lower Image quality (%), reduce the Colors palette, and use fewer frames at a lower framerate to bring the size down.

Does APNG look better than GIF for these frames?

For photographic raw content, yes. APNG supports full 24-bit color and 8-bit alpha with lossless frames, while GIF is capped at 256 colors with on/off transparency — so gradients and skin tones from a LUMIX sensor stay smooth in APNG and band in GIF. Choose GIF only when you need the widest compatibility with very old software; for that, convert RW2 to GIF.

What happens in a browser that doesn't support APNG?

It falls back to the first frame, shown as an ordinary static PNG, because an APNG's first frame is stored as a valid PNG stream. Around 95% of browsers in use today (current Chrome, Firefox, Safari, and Edge) render the full animation.

Is the bit depth reduced when RW2 becomes APNG?

Yes. RW2 records 12 or 14 bits per channel straight from the sensor; APNG, like all PNG, stores 8 bits per channel. Each raw is demosaiced and tone-mapped down to 8-bit sRGB during conversion. That is plenty for on-screen viewing, but it is why you should keep the original RW2 files if you plan to re-edit later.