Initializing... drag & drop files here
Supports: RW2
RW2 is Panasonic's TIFF-based RAW container, used by every Lumix model from the early DMC-LX3/G1 era (2008-2009) through the current GH6, G9 II, S5 II/IIx, S1H, and LX100 II. Cameras store unprocessed sensor data at 12 or 14-bit precision (full-frame S-series and most G/GH bodies hit 14-bit single-shot, dropping to 12-bit during burst per the Lumix S5IIx user manual). Outside SILKYPIX (the bundled developer), Adobe Camera Raw, Lightroom, Capture One, or RawTherapee, an RW2 won't open in macOS Preview, Windows Photos (without the Microsoft Raw Image Extension), Gmail previews, or most messaging apps. Bundling them as a PDF turns an opaque proprietary file into a single document anyone with a free PDF reader can review.
.raw extension that some 2024+ tools no longer auto-detect.| Property | RW2 (Panasonic) | DNG (Adobe) | JPEG |
|---|---|---|---|
| Type | Proprietary RAW (TIFF-based) | Open RAW container (Adobe spec) | Lossy 8-bit baked image |
| Bit depth | 12 or 14-bit linear sensor data | 12, 14, or 16-bit | 8-bit per channel |
| CFA layout | BGGR Bayer (per libopenraw) | Camera-defined | N/A (rendered) |
| Compression | Proprietary lossless | Lossless or lossy | Lossy DCT |
| Typical file size (24 MP) | 22-32 MB | 25-35 MB | 6-12 MB (Fine quality) |
| Embedded JPEG preview | Yes (full-resolution on newer bodies) | Yes | N/A |
| Universal viewer support | No — needs RAW processor | Limited (better than RW2) | Universal |
| Editing latitude | Full sensor data, white balance neutral | Full sensor data | Baked, narrow latitude |
| Type | Internal target | Best for |
|---|---|---|
| Screen | ~72 DPI, lowest size | Quick-look web review, email proof |
| Ebook | ~150 DPI | Tablet review, client soft proof |
| Default | Balanced | General-purpose archive |
| Prepress | ~300 DPI, color-managed | Print broker, lab delivery |
| Printer | Highest fidelity | Final print, exhibition portfolio |
If you need the reverse direction or a different output, see RW2 to JPG, RW2 to PNG, RW2 to TIFF, or merge other RAW formats with merge CR2 to PDF, merge NEF to PDF, merge ARW to PDF, or merge DNG to PDF.
RW2 is Panasonic-proprietary and most recipients don't have software that opens it. Gmail, Outlook, iCloud Mail, and the macOS/iOS Mail apps preview JPEG and PDF inline but show RW2 as an opaque attachment. RW2 files are also large (22-32 MB on a 24 MP S5 II, 35-45 MB on the 47 MP S1R), so a 10-photo selection blows past the 25 MB Gmail attachment cap before Gmail forces a Drive link. A merged PDF at Ebook quality is typically under 1.5 MB per page.
RW2 stores 12 or 14-bit linear sensor data — PDF page content is rendered to 8-bit per channel, so a small amount of dynamic range is collapsed during the render (this is what your editor does anyway when exporting JPEG). For a deliverable proof or print-ready PDF, choose Prepress or Printer with Image Quality 90-100 to keep visible detail. For the absolute archival original, keep the RW2 alongside the PDF — the PDF is a viewing copy, not a substitute for the negative.
Apple ships RAW codec support for many cameras through the system's RAW Compatibility list, but it lags new Panasonic bodies by months and excludes very old ones; Windows Photos requires the free Microsoft Raw Image Extension and even then doesn't render every Lumix model. SILKYPIX Developer Studio SE — bundled with Panasonic cameras — is the safest first-party viewer, with Adobe DNG Converter as the universal fallback that turns RW2 into DNG that anything Adobe-compatible can open. Merging straight to PDF skips all of that for the recipient.
Effectively all Lumix models from the late-2000s onward: the S full-frame line (S1, S1H, S1R, S5, S5 II/IIx, S9), GH series (GH4, GH5, GH5S, GH5 II, GH6), G series (G7, G9, G9 II, G85/G80, G95/G90), GX series (GX7, GX8, GX85, GX9), LX premium compacts (LX100, LX100 II), and FZ bridge cameras (FZ1000 II, FZ2500). Older models (DMC-LX3, G1, FZ28, TZ70) sometimes used a .raw extension for the same underlying format. xconvert renders the embedded preview or the full sensor data depending on the body's RW2 variant.
Direct merging works when you want a fast proof reflecting the camera's as-shot rendering — xconvert reads the embedded JPEG preview that newer RW2 files include, which is the same image SILKYPIX shows in its browser before any adjustments. For final deliverables where you've already corrected white balance, exposure, or lens distortion in SILKYPIX, Lightroom, or Capture One, export to TIFF or high-quality JPEG first and use merge image to PDF on those. The RW2-to-PDF route is for unedited proofs and contact sheets.
Yes. The merge engine reads the EXIF orientation tag (the same tag SILKYPIX, Lightroom, and Lumix Tether use for auto-rotate) and renders each page right-side up. If you set Page layout to Portrait but an RW2 was shot landscape, Contained placement will letterbox it; Cover will crop. Mix-orientation shoots usually look best with Contained + Center alignment.
Each RW2 is rendered in your browser session, so the limit is your device's available memory. Modern desktops handle 50-100 frames at full resolution (S5 II 24 MP files are ~25 MB; S1R 47 MP files are ~40 MB); mobile devices may struggle past 15-20 frames at S1R resolution. If you hit a slowdown, split into two batches and combine the resulting PDFs with merge PDF.
Cover fills the entire page edge-to-edge and crops anything that doesn't fit the page aspect ratio — best for photo-book style presentation where you want each frame to bleed to the page edge. Contained scales the full image to fit within the page's margin box, letterboxing if aspect ratios don't match — best for client proofs where you must show the full frame including any planned crop area. RW2 from a 4:3 Micro Four Thirds body (GH/G series) on a Letter or A4 page benefits from Contained; a 3:2 full-frame S-series RW2 on Letter looks tight under Cover.
No. xconvert processes your files in the browser session — your RW2s never leave your machine for the merge step. That matters for sensitive shoots (real estate pre-listing, legal evidence, embargoed editorial, NDA-bound product photography) where a third-party upload would breach a release or contract.