X-Trans V & Recipe Conversion Notes

The X-T5 uses Fujifilm's X-Trans V sensor generation (a 40MP X-Trans CMOS 5 HR sensor + X-Processor 5). Recipes are written per sensor generation because the same settings render slightly differently across generations. This file explains the X-T5-specific behaviour and how to safely borrow recipes written for other cameras.

Architecture deep-dive: what X-Trans actually is (6 × 6 CFA, 55.6 % green, no optical low-pass filter), the pixel-pitch figures behind these generations, and what GFX really uses now live in sensor-architecture-x-trans-and-gfx.md. This file stays focused on porting recipes between generations.

Sensor generations (for context)

⚠"X-Trans V" is two different sensors (added 2026-07-25)

The X-T5's photosite is 19.3 % smaller in pitch, roughly 35 % less area, than the X-H2S's, so at a matched ISO the X-H2S is the cleaner sensor per pixel.

Every recipe in this bank is validated on X-Trans CMOS 5 HR (the X-T5). Colour transfers to the X-H2S. Same film simulations, same CFA, same processor family, so the blue-rendering rule below applies identically to both. What does not transfer unchanged is high-ISO texture. Recipes that deliberately use sensor noise as part of the look, Delta 3200, Tri-X 400 and T-Max P3200 at ISO 12800, and Acros Red, which uses high-ISO noise instead of Grain. Will read cleaner on an X-H2S. Re-judge those there rather than assuming they match. Full reasoning in sensor-architecture-x-trans-and-gfx.md.

The X-T5's processor also unlocks the full modern feature set the recipes rely on: Grain Size, Color Chrome FX Blue, Clarity, Nostalgic Neg., and the Reala Ace film simulation.

Reala Ace on the X-T5. Confirmed, and it needs firmware (verified 2026-07-25). Reala Ace was added to the X-T5 by firmware 4.00, released June 2024 (the same update also reached the X-H2, X-H2S, X-S20 and X100VI). Earlier notes in this repo hedged with "on some bodies/firmware", that is now resolved: any X-T5 on firmware 4.00 or later has it; below that it does not. Check under MENU → USER SETTING → FIRMWARE. This matters for any recipe built on the base, see AP's Portra, which uses it and ships a Classic Chrome fallback for older firmware.

The blue-rendering difference (the #1 conversion rule)

X-Trans V renders blue more deeply/saturated than X-Trans IV on these film simulations: Classic Chrome, Classic Negative, Eterna, Eterna Bleach Bypass.

✅ Corroborated numerically, 2026-07-27. This rule was observational until now. Comparing Adobe's published colour matrices for the two generations, the blue channel changes more than red or green between X-Trans IV and V: under three independent metrics, on two independent body pairs (X-T4→X-T5 and X100V→X100VI). Blue is largest in all six comparisons. Independent evidence for a rule that was not derived from it. Data, method and the limits of the claim in sensor-architecture §7e.

⚠Two things that measurement does not license: it says nothing about which simulations are affected (it describes the sensor, upstream of all of them, the four sims named below remain the community-observed scope), and the red-versus-green ordering is estimator-dependent and is not claimed.

To make an X-Trans IV recipe (using one of those sims) look the same on the X-T5, drop Color Chrome FX Blue by one notch:

Most of the "X-Trans V version" recipes in this collection already have this adjustment baked in; the per-recipe the notes notes where it applied.

AWB (Auto White Balance) considerations

X-Trans V bodies have a newer AI-driven Auto White Balance. On recipes that call for AWB, the X-T5 may choose a slightly different balance than an older body would, especially in mixed/artificial light. If an AWB recipe looks —, options are: - switch to a fixed WB (Daylight or a Kelvin value) close to the intended cast, or - adjust the WB shift to compensate.

This is why colour-critical recipes tend to prefer fixed WB, while versatility-first recipes accept AWB's scene-to-scene variation.

Borrowing recipes from other generations

• X-Trans IV → V: usually only the CCFXB one-notch drop (above); occasionally an AWB tweak. Otherwise settings transfer directly.
• X-Trans III → V: III bodies lack Grain Size, CCFXB, Clarity, and Color Chrome FX Blue, and some lack Classic Neg./Eterna. Converting means adding those modern settings, so it's less mechanical. Treat III recipes as inspiration rather than a direct port.
• GFX: ⚠not an X-Trans camera at all. (corrected 2026-07-25) Every GFX body uses a conventional Bayer CFA. X-Trans is an APS-C X-series technology only. So a GFX runs the same film simulations through a different colour filter array (2 × 2 Bayer, 50 % green, vs X-Trans's 6 × 6 at 55.6 %), a different demosaic, and a sensor 3.91 × the area. Since a Fujifilm simulation is a spectral-sensitivity-aware conversion of the raw signal, a different CFA is a genuinely different input to that conversion. Treat these recipes as a starting point on GFX, not a transfer: the simulation names and parameter ranges are shared, the rendering is not guaranteed to be. No GFX body is available to this project, so nothing stronger is claimed. See sensor-architecture-x-trans-and-gfx.md.

Practical setup notes on the X-T5

• Store recipes in the C1–C7 custom presets (Image Quality → Edit/Save Custom Setting). The X-T5 (X-Pro3-and-newer) remembers a White Balance Shift per custom preset, so each recipe keeps its own WB shift. Older bodies did not.
• The X-T5 also has the film-simulation/recipe-friendly Q menu and can map Film Simulation to a function button for quick switching.
• Firmware: the bundled New Features Guide (x-t5_nfg_en_s_f.pdf) documents v4.30 changes, which are connectivity/menu items only (wireless comms, instax printer support, smartphone pairing). None affect image quality or the recipes.

Last updated: 2026-07-27