How to Convert Fujifilm X-Trans IV Recipes to X-Trans V (X-T5, X100VI)

If you've ever dialed a beloved older recipe into your X-T5 or X100VI only to find the skies look aggressively, unnaturally blue, you aren't imagining things.

Fujifilm film simulation recipes don't always port perfectly across camera generations. The processing pipeline changes, the base color profiles get tweaked, and what looked like a perfect Kodak Portra on a X-T3 can suddenly look like bad HDR on a X-T5.

To bring older X-Trans IV recipes forward to the X-Trans V generation (which includes the X-T5, X-H2, X-S20, and X100VI), you have to understand the mechanical differences between the sensors. I've spent hours validating recipes across both generations, and the conversion essentially comes down to a few hard rules.

The Blue Channel Shift (And How to Fix It)

When Fujifilm launched the X-Processor 5, they subtly tweaked the color science for several of their most popular film simulations. Specifically, the X-Trans V renders the blue channel significantly deeper and more saturated than previous generations on these four profiles:

• Classic Chrome
• Classic Negative
• Eterna
• Eterna Bleach Bypass

If you load a X-Trans IV recipe built on Classic Chrome directly into a X-T5, the blues will clip faster and look heavily stylized. To compensate and match the original intent of the recipe, you need to manually adjust the Color Chrome FX Blue (CCFXB) setting.

The Conversion Rule

If the older recipe uses one of the four profiles listed above, drop the CCFXB setting by exactly one notch:

• If the original asks for Strong, change it to Weak.
• If the original asks for Weak, change it to Off.
• If the original was already Off, leave it Off. Your blues will still be slightly deeper than they were on the older camera, but it's as close as you can get without shooting raw.

Dealing with Auto White Balance Drift

The X-Trans V bodies introduced a new AI-driven Auto White Balance (AWB) algorithm. While it's objectively better at nailing neutral white balance in mixed lighting, "objectively accurate" isn't always what you want when shooting film emulations.

If a recipe relies on AWB, your X-T5 might interpret the scene differently than a X-Pro3 would have. You'll notice this most often indoors under artificial light. If a AWB-based recipe looks wrong, try one of these fixes:

1. Lock the White Balance: Switch from AWB to a fixed Kelvin value or a preset (like Daylight). This completely bypasses the AI's guesswork.
2. Tweak the Shift: If the recipe feels too cool, push the White Balance Shift a notch further into the Red or drop the Blue.

I strongly prefer fixed White Balance for color-critical film emulations because it removes the inter-generational drift entirely.

A Note on Older Sensors (X-Trans III)

Trying to bring a X-Trans III recipe (like those for the X-T2 or X100F) to the X-T5 is a totally different ballgame.

X-Trans III bodies lack modern settings entirely: no Grain Size control, no Clarity, no Color Chrome Effect, and no Color Chrome FX Blue. You can't do a 1:1 mechanical conversion here. Instead, you have to interpret what the creator was going for. Use their X-Trans III settings as a baseline, but you'll need to manually season it with the newer settings (like adding Color Chrome Effect for deeper reds) to bring the emulation to life on a modern sensor.