How to Share Your Fujifilm Recipe

Yes. A recipe you worked out on your own camera is yours to share, and sharing it is the entire point of a community like this one. A recipe is a list of camera settings, and settings only become useful when someone else can dial them in and see what you saw.

When you publish on X-Alchemy you keep ownership of what you post. You grant us a non-exclusive licence to display it here, which is what lets the recipe appear on the site, and nothing more. You can edit or delete a recipe at any time. The full wording is in our Terms of Service.

The one thing worth being careful about is content that is not yours to give away. Your example photos need to be yours, and if the recipe itself started as someone else's work, the honest move is to credit them rather than republish it as your own. That is covered further down.

A recipe someone can actually follow needs every setting you changed, plus enough context to know whether it will work on their camera. X-Alchemy captures sixteen Fujifilm settings, and the guided flow walks through them in the order the camera menu presents them.

Alongside the settings, a recipe carries the camera body it was built on. That one field does more work than it looks: the processor and sensor fill in from it automatically, and they are what let the site tell a reader whether the recipe runs on their camera. A recipe with no body attached cannot answer the question every reader asks first.

Then a title, a short description of when the look works, tags so it can be found, and at least one example photo. You can attach up to five. The photos are not decoration: they are the only way a reader can judge whether the numbers produce something they want before spending ten minutes typing them into a menu.

Transcribing sixteen settings off the back of a camera is where most people give up halfway. You do not have to. A Fujifilm JPEG straight out of the camera carries every one of those settings in its metadata, and dropping that file into the first step of the guided flow reads them out and fills the form for you, along with the camera model and the lens.

What is left is the part only you can write: the title, the description, and the photos.

Two conditions matter. The file has to be a JPEG the camera produced, not one exported from Lightroom or a phone, because editing software strips the Fujifilm maker note the settings live in. And it has to be the frame you shot with the recipe applied, since the metadata describes that frame rather than your current camera state. If a setting cannot be read, the flow tells you which one rather than leaving a field silently blank.

Most recipes are descendants of other recipes. Someone publishes a Classic Chrome look, you find it runs warm in British winter light, you pull the shift two points towards blue and it becomes the one you actually use. That is not copying and it is not original either. It is the normal way a look evolves, and it deserves to be recorded rather than argued about.

On any recipe page there is a Share Your Version link. Starting from there carries the source through the whole flow, and your published recipe credits it by name with a link back to the original and to its author. You can see the credit before you publish, on the Describe step, and remove it if you change your mind.

The rough line: if you changed the settings and the result is a look of your own, publish it as yours with the credit attached. If you did not change anything meaningful, there is nothing to publish. Favourite the original instead and it will be waiting in your account.

Recipes found elsewhere follow the same principle. Name the source in your description, and if the original is already on X-Alchemy, use Share Your Version so the link is structural rather than something a reader has to go and search for.

The two questions that come up the moment someone finds a recipe worth trying both have their own guides, because both deserve more room than a paragraph here.

How to Program Recipes Into Your Camera covers saving a recipe into the C1 to C7 custom slots so you can switch between looks with a dial rather than a menu dive.

Recipe Compatibility: Sensor Generations covers whether a recipe built on one body runs on yours. The short version is that availability does not fall neatly on sensor generations. Classic Neg. arrived with the X-Pro3, Eterna Bleach Bypass a wave later with the X-T4, and Clarity and Color Chrome FX Blue with the X-Pro3 as well. That leaves the X-T3 in the odd position of being a fourth-generation body with none of them.

Every recipe page on the site answers the compatibility question for you directly. Tell us which camera you shoot and the page will say whether the recipe transfers, transfers partially, or uses something your body does not have.