Skip to content

EXR to RAF Converter

Convert EXR to RAF in your browser. You download a Linear DNG (.dng), not a .raf: only a Fujifilm camera can create a genuine RAF, and every editor that opens RAF also opens DNG. Nothing is uploaded.

  • Processed locally
  • No upload, no wait
  • No sign-up
  • No watermark

Drop images here

or choose files · paste with Ctrl/⌘ V

EXR expected · other image formats also work

Files are processed on this device. Nothing is uploaded.0 B uploaded

How to use EXR to RAF

  1. 1

    Add your EXR files: drop them here, choose them, or paste from the clipboard.

  2. 2

    Pick the colour that replaces transparent areas, since DNG has none.

  3. 3

    Click Convert. Each file is decoded and encoded in a background thread on this device.

  4. 4

    Download the .dng files one at a time or together as a ZIP.

Why use Aback Images for exr to raf

Where a RAF would go

RAF files are opened by Fujifilm X RAW Studio, Lightroom, Photoshop Camera Raw, Capture One and darktable, and every one of them opens the DNG too.

DNG next to EXR

Neither format compresses much, so the DNG lands close to the EXR in size.

Written without a lossy pass

The DNG is written uncompressed, so the pixels decoded from the EXR arrive unchanged, apart from precision beyond 8 bits per channel.

Processed on your device

Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.

EXR vs RAF

What changes from EXR to RAF

Encoding: the EXR uses none, RLE, ZIP, PIZ, PXR24, B44 or DWA, chosen per file; RAF uses uncompressed or lossless compressed sensor data in Fujifilm's own container, and the download is a Linear DNG: demosaiced 8-bit RGB with the colour matrices raw editors need.

Bit depth: 16-bit half or 32-bit floating point per channel in the EXR; RAF allows 12 to 16 bits per channel depending on the camera, and the DNG written here has 8 bits per channel, linearised. Floating-point values are mapped to 8 bits per channel, and anything brighter than white clips.

Colour: scene-linear RGB, often ACEScg or linear Rec.709 in the EXR; RAF supports camera RGB from an X-Trans 6×6 or Bayer 2×2 mosaic, written here as 8-bit sRGB.

Transparency: the EXR stores it as an A channel stored like any other channel; the DNG has none, so transparent areas are filled with the colour you choose.

Other images: the EXR can hold extra channels (depth, normals, render passes) and multiple parts; only the main image is converted.

Metadata: the EXR can carry named header attributes such as chromaticities, timecode and camera data; RAF can carry EXIF and Fujifilm maker notes, including the Film Simulation, but nothing is copied across.

About EXR

OpenEXR is the high dynamic range format of film visual effects. It stores half or full floating-point channels in linear light, plus any extra render passes, and is the working format of compositing pipelines.

An EXR starts with the magic number 76 2F 31 01 and a version field, then a header of named, typed attributes (channels, compression, dataWindow, displayWindow) and a table of offsets to scanline or tile blocks.

EXR files usually come from 3D renderers and compositing in Nuke, Blender, Houdini, After Effects and DaVinci Resolve.

About RAF

RAF is the raw format of Fujifilm cameras, from the X series to the medium-format GFX. Most X-series bodies use an X-Trans sensor with a 6×6 colour filter pattern instead of the usual Bayer 2×2.

RAF is not TIFF at the top level: it opens with the text 'FUJIFILMCCD-RAW', then a header with the camera model and offsets to three blocks: a JPEG preview near the start of the file, a header describing the sensor layout, and the sensor data.

RAF files come from Fujifilm X-T, X-H, X-S, X-E, X100 and GFX cameras.

When converting EXR to RAF makes sense

Forms and workflows that ask for RAF usually feed a raw editor, and each of those opens DNG as well, so the DNG can take the RAF's place. Keep the EXR if you only need to view or share the picture.

What RAF offers when it comes straight from the camera: Film Simulation baked into the embedded JPEG; Lossless compressed option on recent bodies; Large medium-format files from GFX cameras. Its drawbacks: Fujifilm's own container rather than TIFF; X-Trans demosaicing differs between raw editors; Film Simulations need camera-matching profiles in third-party editors.

Limitations

  • EXR values are scene-linear and can exceed 1.0; they are mapped to display values without tone mapping, so highlights clip to white.
  • Only the colour channels are converted; depth, normals and other render passes are dropped.
  • Single-part scanline files are supported; tiled, deep and multi-part EXRs, and those compressed with B44 or DWA, cannot be read here.
  • The DNG holds the decoded 8-bit pixels, so it adds no dynamic range or detail beyond the EXR.

Frequently asked questions

Why do I get a .dng file instead of a .raf?

A real RAF is written by Fujifilm cameras and holds the sensor's own readings (12 to 16 bits per channel depending on the camera, stored as uncompressed or lossless compressed sensor data in Fujifilm's own container) along with EXIF and Fujifilm maker notes, including the Film Simulation. An EXR holds no sensor data, so no software outside the camera can create a genuine RAF. The Linear DNG you get instead is Adobe's open raw format, and every editor that opens RAF files opens it with the same raw controls. It holds decoded pixels, so it adds no quality or dynamic range.

Does converting EXR to RAF lose quality?

DNG is written uncompressed, so the pixels are stored exactly as decoded. Floating-point values are mapped to 8 bits per channel, and anything brighter than white clips. Not carried over: any extra channels.

What happens to transparency when converting EXR to RAF?

EXR stores transparency as an A channel stored like any other channel. DNG has no alpha channel, so transparent pixels are composited onto a solid colour, white unless you pick another. To keep transparency, convert to PNG, WebP or AVIF instead.

Are my images uploaded anywhere?

No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.

Can I process many files at once?

Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.

Is it free? Is there a file limit or watermark?

It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.