History Lesson: What Is a .raf File? Fujifilm RAW

What is a .raf file?

A .raf file is Fujifilm’s proprietary camera RAW package — the stills capture many FinePix, X-series, and GFX digital bodies write when you choose RAW (or RAW+JPEG) instead of JPEG alone. Think of it as the capture kept for later demosaic and tone work, not a social-ready JPEG. Developer and archive references commonly cite MIME type image/x-fuji-raf.

Under the hood, RAF is not a plain JPEG rename. Well-documented layout notes (from the open RAW-decoding community) describe Motorola / big-endian byte order and a 16-byte magic string FUJIFILMCCD-RAW (trailing space included in the documented signature), followed by version/model fields and an offset directory pointing at: an embedded JPEG preview (often a full Exif JFIF preview used for camera playback and naive thumbnails), a proprietary metadata directory (tag/length/payload records), and a CFA / raw payload region — commonly described as a TIFF-like (Tagged Image File Format) container for the sensor data. Sensor samples are deeper than JPEG’s 8-bit (historically often 12- or 14-bit, depending on body). Later X-series options add uncompressed, lossless compressed, and — on some newer cameras — lossy compressed RAF recording; ExifTool’s RAF header map documents those compression enums in the header.

A classic Bayer CFA is a repeating 2×2 red/green/blue filter mosaic over the photosites. Fujifilm’s story is messier on purpose. Early Super CCD FinePix bodies used an unusual photosite geometry (including diagonally oriented photodiodes on well-known S-series DSLRs, and Super CCD SR dual-sensitivity S/R photodiode pairs on models such as the FinePix S3 Pro). From the X-Pro1 onward, many X-series bodies use X-Trans: a larger, more irregular 6×6-style color-filter layout Fujifilm designed to reduce moiré and false color without an optical low-pass filter. That irregular mosaic is why third-party raw software historically struggled more with X-Trans RAF than with Bayer RAW — demosaic algorithms written for Bayer do not drop in cleanly. Open format notes also point to RAF metadata tag 0x131 for the X-Trans layout when present.

Why won’t my computer open a .raf file?

Because RAF is camera RAW, not a finished display image. Windows Photos, File Explorer, and many browsers often have no native RAF decoder path — you may see a blank or generic icon even when the capture is intact. When something *does* appear, it is often only the embedded JPEG preview (the camera’s quick-look JPEG inside the RAF), not a full demosaic of the sensor mosaic. That mismatch is why a file can “open” as a soft preview in one tool and refuse to develop in another.

Adobe Camera Raw / Lightroom support for brand-new Fujifilm bodies often arrives after the camera ships — older installs can refuse a fresh model’s RAF until you update. X-Trans made that gap feel sharper: early third-party converters needed new demosaic logic for the irregular CFA, so “my friend’s NEF opens but my RAF looks wrong / won’t open” was a common photographer complaint after the X-Pro1 era. Separately, compressed RAF options (lossless, and later lossy on some bodies) can outpace older software that only understood uncompressed RAF.

Film simulations (Provia, Velvia, Astia, Acros, and later looks) are Fujifilm’s in-camera JPEG / preview looks inspired by the company’s film heritage. They are not the same thing as the raw mosaic being permanently “baked” into one look. Community and metadata write-ups describe the chosen simulation as recorded in MakerNotes / related tags and applied to the embedded JPEG preview; the sensor RAW remains available for later reprocessing. Opening a RAF in a generic viewer that only shows the preview can therefore look “already film-simulated,” while a full raw pipeline lets you change the look.

One more confusion to own: .raf is not exclusively Fujifilm on the wider internet. Some Riot Games titles used Riot Archive File packages also named .raf (often beside a companion .raf.dat). Those are game data archives, not camera RAW. If a “.raf” came from a game install folder rather than a camera card, it is a different format. Fujifilm camera RAF is commonly identified by the FUJIFILMCCD-RAW signature up front.

Where RAF came from (FinePix Super CCD, X-Trans, GFX)

Fujifilm’s digital stills path runs through the FinePix brand before the modern X and GFX lines. A well-documented early CCD-RAW chapter is the FinePix S2 Pro — announced 30 January 2002 — a Nikon F-mount DSLR body paired with Fujifilm’s Super CCD sensor electronics. Contemporary reviews note that S2 Pro RAW files used the .RAF extension and carried an embedded JPEG preview. Hedge the absolute “very first RAF ever” crown if earlier FinePix experiments existed; the S2 Pro is the clear, widely reviewed early DSLR RAF landmark. The earlier FinePix S1 Pro (~2000) is widely described as shipping JPEG/TIFF without a production RAW mode.

Through the mid-2000s, FinePix S-series and other Super CCD cameras kept the unusual sensor story alive — including Super CCD SR on the FinePix S3 Pro (2004), with paired large “S” and small “R” photodiodes aimed at wider dynamic range. Consumer FinePix bodies and, later, the FinePix X100 (shown at photokina September 2010, sold from 2011) continued writing .raf while Fuji’s rangefinder-styled X language took shape.

The interchangeable-lens leap that made RAF famous among mirrorless shooters is the FUJIFILM X-Pro1, announced 10 January 2012, with the first X-Trans CMOS sensor, a new X mount, and hybrid viewfinder. Fujifilm’s own launch materials describe a film-grain-inspired irregular RGB filter arrangement in 6×6 sets meant to suppress moiré without an optical low-pass filter — and an EXR Processor Pro strong enough to demosaic that pattern in-camera. Third-party raw tools had to catch up. Through later X-T / X-E / X-H bodies and fixed-lens X100 successors, stills RAW stayed .raf on disk.

Medium format kept the same extension. Fujifilm announced the GFX system and GFX 50S development at photokina on 19 September 2016 (43.8×32.9 mm G Format sensor, new G mount), with commercial release in early 2017. Fujifilm’s own GFX 50S specs list 14-bit RAW (RAF original format) alongside JPEG. Later GFX bodies continue the RAF name even as sensor generations change — so a folder of “.raf” can span a 2002 Super CCD SLR, a 2012 X-Trans mirrorless body, and a modern medium-format GFX card.

Why .raf files still sit on disks in 2026

By 2026, .raf still shows up from FinePix S-series cards, more than a decade of X100 / X-Pro / X-T archives, travel backups, Lightroom catalogs, wedding and street shoots, and newer GFX medium-format captures that continue the same extension. Windows may still show a blank icon or only the embedded preview without a raw pipeline; an older Lightroom install may refuse last year’s body or a compressed RAF option. These are legacy files in the everyday sense: still valuable captures, often confusing next to JPEGs, and easy to leave stranded on an old drive.

Legacy File Converter converts RAF and other listed camera RAW extensions (CR2, CR3, DNG, NEF, ARW, ORF, RW2, and related family members on Supported File Types) locally on Windows to JPG or PNG. Nothing is uploaded. It does not claim conversion for Riot Archive .raf game packages. This article stays the history; for practical open-and-convert steps, see Opening RAW Camera Files Without the Camera Software. For neighboring RAW lessons, see History Lesson: What Is a .rw2 File? Panasonic Lumix RAW, History Lesson: What Is a .orf File? Olympus RAW, History Lesson: What Is a .dng File? Adobe’s Digital Negative, History Lesson: What Is a .nef File? Nikon RAW, and History Lesson: What Is a .cr2 File? Canon RAW.