Fujifilm RAF files do not need a special set of creative standards, but they do reward a deliberate preview workflow. Many Fujifilm cameras offer RAW plus JPEG or HEIF capture, film simulations, and several RAW compression choices. Those settings affect what you can browse quickly and what you retain for editing later.

The useful distinction is between a camera-generated preview and processed RAW data. A preview can be excellent for judging timing, expression, composition, and broad exposure. It cannot show every adjustment or recovery available from the RAW file. Treat it as a fast decision surface, then inspect the source you will edit when a decision depends on fine detail or tonal latitude.

What X-Trans changes, and what it does not

Fujifilm describes X-Trans as a distinctive colour-filter array designed to control moiré and false colour without an optical low-pass filter. That is a sensor and RAW-processing difference; it does not establish a universal speed penalty for every RAF file or every application. Camera generation, resolution, compression, storage, preview settings, and software all affect responsiveness.

GFX and X-series bodies also differ, so avoid treating every RAF as the same sensor format. Check support for your exact camera and compression mode before a paid job. A representative shoot is more useful than a generic claim that one brand or decoder is always faster.

Use previews for the broad pass

Start with the fastest trustworthy preview your application provides. Judge the moment, framing, expression, gesture, duplicates, and obvious technical failures without opening every file at maximum detail. Camera Bits documents that Photo Mechanic uses embedded previews where supported; Adobe offers Embedded & Sidecar previews during Lightroom Classic import. Other applications may generate their own previews.

A camera-generated preview reflects in-camera choices such as film simulation, white balance, tone, and JPEG or HEIF settings. That can make it a useful view of the look you intended, but it is still not the editable RAW result. If your final grade will differ substantially, keep that difference in mind while choosing.

Check uncertain frames at useful detail

Open a closer view when the decision turns on eye focus, fine motion blur, small expressions in a group, or highlight and shadow detail. Compare neighbouring burst frames at the same magnification. Do not infer RAW recovery from a clipped or dark camera preview alone.

Selekt uses Space to open Quickview for the focused or selected photo. Clicking the image in Quickview enters or exits a 100% loupe, and the loupe can remain active while you step between frames. R switches the available JPG/RAW preview source. That control identifies the source being shown; it is not a promise that every camera or file produces a new full-resolution RAW demosaic.

Choose RAW, JPEG, or both before the shoot

Fujifilm manuals document RAW-only, JPEG or HEIF-only, and combined RAW plus JPEG or HEIF choices on supported cameras. Combined capture gives you an immediately usable rendered file and a RAW source for later editing, at the cost of additional storage and file management. RAW-only avoids the extra companion file, while JPEG or HEIF-only commits more of the look in camera.

There is no universal instruction to shoot RAW plus JPEG. Choose it when the rendered companion improves your workflow or is itself a deliverable. Test how your culling and editing applications pair or display companion files, especially if you create additional in-camera conversions with the same base filename.

A repeatable RAF cull

  1. Copy and verify the card before deleting or formatting anything.
  2. Confirm that your application supports the exact camera and RAF compression mode.
  3. Make a broad pass from a usable preview, marking obvious rejects and likely keepers.
  4. Compare similar frames together rather than relying on memory.
  5. Inspect focus and uncertain exposure on the source and at the magnification that matters.
  6. Transfer the decisions using a method your editor actually reads, then verify a small batch before moving the whole job.

This workflow separates fast editorial decisions from the smaller number of checks that need more detail. Measure it with your files and hardware rather than adopting fixed seconds-per-image or percentage targets.

Sources and further reading