PicaJet

Reference Formats

RW2

RW2 is Panasonic's proprietary raw image format for Lumix (and co-branded Leica) digital cameras, storing unprocessed Bayer sensor data in a TIFF-derived container.

Extension

.rw2

Full name

Panasonic RAW Image (version 2)

Introduced

circa 2008, when Panasonic moved its Lumix RAW-capable cameras from the earlier .RAW extension to .RW2 (around the Micro Four Thirds DMC-G1 generation)

Vendor

Panasonic

What is inside the container

RW2 uses a TIFF-like structure but with a different file signature and non-standard tag numbers, so generic TIFF readers cannot parse it correctly. Files hold 12-bit or 14-bit Bayer-pattern sensor data with Panasonic's own lossless or lossy compression, standard EXIF metadata, and an embedded JPEG preview. There is no public specification; third-party support (Adobe, RawTherapee, libraw) exists because these tools reverse-engineered the structure rather than implementing a documented standard.

How to open it

Windows / macOS Adobe Camera Raw (in Photoshop) or Lightroom Classic, with the camera's RW2 profile installed via the Camera Raw update
Cross-platform, open source RawTherapee or darktable, both of which decode RW2 through the libraw/RawSpeed libraries
Panasonic native Panasonic's own SILKYPIX-based raw converter bundled with Lumix cameras
Professional tethered/asset workflows Capture One, which added Panasonic RW2 support for most current Lumix bodies

For archives

RW2 is undocumented and proprietary, so long-term support depends entirely on Adobe and open-source maintainers continuing to reverse-engineer new camera models. For DAM archival, convert RW2 masters to DNG using Adobe's free DNG Converter and store the DNG as the durable access copy, while keeping the original RW2 only where bit-exact re-processing in Panasonic's own software might matter.

RW2 is the raw format Panasonic uses across its Lumix line, including the cameras co-branded with Leica. Panasonic originally shipped raw files with a plain .RAW extension on early Lumix models, then switched to .RW2 as the format matured alongside the launch of the Micro Four Thirds system. The files are built on a TIFF-like skeleton, but Panasonic altered the file signature and several internal tag numbers, which means software has to specifically target RW2 rather than treat it as generic TIFF.

Inside an RW2 file sits the sensor’s raw 12-bit or 14-bit Bayer readout, compressed with a Panasonic-specific lossless or lossy scheme depending on the camera generation, plus EXIF metadata and an embedded JPEG preview used by thumbnail generators. Because Panasonic has never published a specification, everything the wider software ecosystem knows about RW2’s internal layout comes from reverse engineering by Adobe, the libraw project, and tools like dcraw and RawTherapee.

For a DAM, that reverse-engineered support is the central risk: a new Lumix sensor or compression variant can outpace decoder updates, leaving fresh RW2 files unreadable in some tools until support catches up. Ingest pipelines that auto-generate previews and extract metadata need to be tested against current Lumix models specifically, and RW2 masters are a strong candidate for a DNG-normalized access copy rather than being relied on directly for downstream rendering.

Frequently asked

Is there a public specification for RW2 that DAM tool vendors can implement against?

No. Panasonic has never published an RW2 format specification, unlike DNG's public spec. Vendors building RW2 support—Adobe, RawTherapee, darktable, LibRaw—rely entirely on reverse-engineering camera output, since LibRaw began recognizing RW2 around October 2009. This means DAM tools depend on third-party libraries maintaining ongoing reverse-engineering work rather than implementing against documented Panasonic tag definitions, sensor layouts, or compression algorithms.

Can generic TIFF readers parse RW2 correctly?

No. Although RW2 stores its header and metadata in a TIFF-derived container, Panasonic modified the file signature and used non-standard, proprietary tag numbers that don't match the baseline TIFF 6.0 specification. A generic TIFF parser will typically read the container structure but fail to locate or correctly interpret the actual Bayer sensor data and Panasonic-specific MakerNote fields, requiring RW2-aware decoding logic instead.

What should a DAM do with RW2 masters for archival?

Convert them to DNG using Adobe's free DNG Converter and store the DNG as the durable access copy, keeping the original RW2 only where bit-exact re-processing in Panasonic's own software might matter.

What compression and bit depth does RW2 use?

RW2 stores 12-bit Bayer-pattern data on older Lumix models and 14-bit on newer ones, capturing raw sensor readout before demosaicing. Panasonic applies its own proprietary compression, offering both lossless and lossy modes depending on the camera body and firmware. Files also embed standard EXIF metadata alongside an embedded JPEG preview, plus extensive Panasonic MakerNote tags covering lens data, image stabilization, and Photo Style settings.

When did Panasonic introduce RW2?

Panasonic introduced RW2 in 2008 alongside the Lumix DMC-G1, the world's first Micro Four Thirds mirrorless camera, replacing the earlier .RAW extension used on prior Panasonic and Leica-co-branded models. The format has since been carried across the entire Lumix G-series and full-frame S-series lineup. LibRaw and dcraw began recognizing RW2 files around October 2009, roughly a year after the format's debut.

What native software opens RW2?

Panasonic ships a SILKYPIX-based raw converter bundled with its cameras for native RW2 processing. Beyond Panasonic's own tools, RW2 support is widely available through Adobe Camera Raw and Lightroom Classic, the open-source RawTherapee and darktable, and Capture One—all relying on reverse-engineered decoding rather than an official SDK. DAM archivists should confirm which converter version matches a given camera model, since newer Lumix bodies sometimes outpace third-party support.

Why does RW2's undocumented status matter for long-term DAM planning?

Because no published specification exists, long-term RW2 readability depends entirely on Adobe and open-source maintainers continuing to reverse-engineer each new Panasonic sensor and compression variant. If that maintenance lapses—for a discontinued library or an unsupported camera model—archived RW2 masters could become unreadable years later. This is why DAM workflows commonly convert RW2 to DNG for preservation, keeping the original file only when Panasonic-specific reprocessing is genuinely required.

How do open-source tools decode RW2?

RawTherapee and darktable decode RW2 through the LibRaw and RawSpeed libraries, which bundle years of accumulated reverse-engineering knowledge about Panasonic's tag layout and compression schemes. LibRaw, built on dcraw's codebase, has recognized RW2 since around October 2009. However, newer Panasonic encoding variants can outpace this support—RawTherapee's custom dcraw fork sometimes extracts the compressed raw stream but fails to fully decode its internal structure for newer camera models.

Sources