Initializing... drag & drop files here
Supports: RAF
.raf files from FinePix, X-series, and GFX cameras, including X-Trans sensor models. Batch is supported — drop in a folder of RAF shots and each one is demosaiced and converted in parallel.RAF is Fujifilm's proprietary raw image format, written by FinePix, X-series mirrorless, and GFX medium-format cameras. A raw file is not a finished picture — it is the sensor's unprocessed readout, typically 14-bit per channel, that still needs demosaicing (turning the color-filter mosaic into full-color pixels), white balance, and tone curves applied before it looks like a photo. That raw data is what gives you the latitude to recover blown highlights and lift shadows in an editor, but it also means a RAF won't display in a browser, attach to an email as a viewable image, or upload to most websites.
Fujifilm complicates this further than most brands: most X-series bodies use an X-Trans sensor, whose color filter is laid out in a 6×6 pattern instead of the standard 2×2 Bayer grid. That layout reduces moiré (Fujifilm omits the optical low-pass filter because of it), but it also means RAF files need X-Trans-aware demosaicing code that older or generic raw decoders don't have — which is exactly why a fresh RAF so often "won't open" in an out-of-date Photoshop or Camera Raw. Converting on a server that already speaks X-Trans sidesteps the whole plugin-update treadmill.
The common reasons people convert RAF away from raw:
| Target | Compression | Bit depth | Alpha | Best for |
|---|---|---|---|---|
| JPG | Lossy | 8-bit | No | Sharing, web, email, social — opens everywhere |
| PNG | Lossless | 8 / 16-bit | Yes | Compositing, graphics, lossless export with transparency |
| TIFF | Lossless or LZW | 8 / 16-bit | Yes | Editable master, retouching, archival, print |
| WEBP | Lossy or lossless | 8-bit | Yes | Modern web galleries — ~25-30% smaller than JPG |
| AVIF | Lossy or lossless | 8 / 10 / 12-bit | Yes | Smallest high-quality web image; newer browser support |
| HEIC | Lossy (HEVC) | 8 / 10-bit | Yes | Compact stills in the Apple ecosystem |
| BMP | Uncompressed | 8-bit | No | Legacy Windows software that requires a raw bitmap |
Need a single direction? Jump straight to a pair: RAF to JPG · RAF to PNG · RAF to TIFF · RAF to WEBP · RAF to PDF. To shrink an exported photo afterward, use the Image Compressor.
Fujifilm's own software reads RAF natively: X RAW Studio (which offloads processing to a connected camera) and the bundled raw converters. Adobe Lightroom, Photoshop, and Camera Raw read RAF too, but only if your Camera Raw version is recent enough to support your specific camera — Fujifilm adds new RAF variants with each body, so a new camera often needs a Camera Raw update. macOS Preview and Apple Photos open many RAF files via the system raw decoder. If yours won't open in any of them, your raw decoder predates your camera, which is the most common reason a RAF "fails to load" — converting it here is the fastest workaround.
Yes, and that is expected. A RAF holds the sensor's full 14-bit-per-channel raw readout; a JPG is an 8-bit, lossy, already-developed image. Converting bakes in the white balance, tone curve, and demosaicing, then discards the editing latitude that made raw worth shooting. That's fine for a finished, share-ready photo — but keep the original RAF as your negative. If you want to keep editing headroom, export to a 16-bit TIFF or PNG instead, which preserves far more tonal detail than JPG.
Almost always because Adobe Camera Raw is older than your Fujifilm camera. Each new Fujifilm body writes a slightly different RAF variant, and Adobe adds support for it in a Camera Raw update — so a brand-new camera's files won't open in an older install. The fixes: update Camera Raw and your app to the latest version, or convert the RAF to DNG or TIFF first and open that. Converting RAF to TIFF here gives any editor a file it can read regardless of its raw support.
X-Trans is the color-filter design in most Fujifilm X-series cameras: a 6×6 photosite pattern instead of the 2×2 Bayer grid used by nearly every other brand. It reduces moiré well enough that Fujifilm drops the optical low-pass filter, but it requires special demosaicing code to turn that 6×6 mosaic into full-color pixels. Generic or outdated raw decoders that only understand Bayer produce smeared detail or "wormy" artifacts on X-Trans files. Our pipeline uses an X-Trans-aware decoder, so the converted JPG, TIFF, or PNG renders the fine detail Fujifilm's sensor was designed to capture.
Pick by purpose. Choose JPG when the photo is finished and you just need to share, post, or email it — small files, universal support, 8-bit. Choose TIFF (set Bit Depth to 16-bit) when you'll keep editing: it's lossless, holds the high-precision tonal data raw is prized for, and is the safe interchange format for any editor or print lab. In our testing, a 26-megapixel X-Trans RAF exports to roughly an 8-12 MB high-quality JPG, versus a 150 MB-plus 16-bit TIFF — so reserve TIFF for masters you'll actually rework.
Yes. Drop a whole shoot in and each RAF is demosaiced and converted independently, then handed back as a ZIP. Because every file is processed server-side, batch jobs don't bog down your computer the way opening a folder of raws in a desktop editor does. The practical limit is upload size and connection speed, not file count — and the files are deleted from our servers automatically after a few hours.
Standard EXIF — camera model, lens, exposure, ISO, capture date — is carried into formats that support it, such as JPG and TIFF. Fujifilm's film-simulation "recipe," however, is a develop setting applied to the raw data, not a permanent part of the pixels; a straight RAF-to-JPG conversion applies a neutral default render rather than baking in Velvia, Classic Chrome, or Acros. To keep a specific film look, apply it in-camera or in Fujifilm X RAW Studio first, then convert the resulting file.