Kodak Ektar 100 (Classic Chrome) vs LomoChrome Metropolis
The same photograph, developed by the camera in both recipes. Drag the divider.
Every image is rendered by the camera itself and verified from its metadata. How this works
Star the recipes you like and they pin to the top of these pickers.
Kodak Ektar 100 (Classic Chrome)LomoChrome Metropolis
Same photo, two recipes. Swipe a side to change that recipe, hold it to see it on its own, or tap to inspect up close.
Seawall, photographed by Lucas Costa
The gallery is just getting started.
9 reference scenes so far, each developed in-camera across the full recipe catalog, and we're still testing the pipeline. Contribute a photograph and every comparison ever made with it carries your name and your link, like the credit above.
The full recipe
12 settings differ, highlighted below.
| Setting | Kodak Ektar 100 (Classic Chrome) | LomoChrome Metropolis |
|---|---|---|
| Film Simulation | Classic Chrome | Bleach Bypass |
| Dynamic Range | 100 | 200 |
| Grain | Off | Strong |
| Grain Size | Off | Small |
| Color Chrome | Strong | Strong |
| Color Chrome Blue | Weak | Strong |
| White Balance | Kelvin | Auto White Priority |
| Color Temp | 6050K | — |
| WB Shift | R+3 B0 | R+1 B-7 |
| Highlights | +1 | +1 |
| Shadows | -2 | +2.5 |
| Color | +4 | -2 |
| Sharpness | 0 | -1 |
| Noise Reduction | -4 | -4 |
| Clarity | +3 | +4 |
Recipe by Ritchie Roesch (Fuji X Weekly), with Thomas Schwab source
View recipe page →Develop your photo in it →
designed for X-Trans IV, rendered on X-Trans V
Recipe by Ritchie Roesch (Fuji X Weekly) source
View recipe page →Develop your photo in it →
designed for X-Trans IV, rendered on X-Trans V
What separates these two recipes
Kodak Ektar 100 (Classic Chrome) is built on Classic Chrome and LomoChrome Metropolis on Eterna Bleach Bypass: two different film simulations as the starting point. They differ in 11 settings: Film Simulation (Classic Chrome vs Bleach Bypass), Dynamic Range (100 vs 200), Grain (Off vs Strong), Grain Size (Off vs Small), Color Chrome Blue (Weak vs Strong), White Balance (Kelvin vs Auto White Priority), and more.
The full settings sheet for both recipes is under the viewer above, differences highlighted. Every render is the photographer's single RAW file developed by a Fujifilm camera's own processor and verified against the camera's metadata. The pictures are the settings, nothing else.
Kodak Ektar 100 (Classic Chrome) is by Ritchie Roesch (Fuji X Weekly), with Thomas Schwab (source). LomoChrome Metropolis is by Ritchie Roesch (Fuji X Weekly) (source).
Photos shot with Kodak Ektar 100 (Classic Chrome) →·Photos shot with LomoChrome Metropolis →
More comparisons
More comparisons
- Classic Cuban Negative vs Reggie's Portra
- Classic Chrome vs Classic Negative
- Acros vs Monochrome
- Reggie's Portra vs Leica X
- Reggie's Portra vs Classic Chrome
- Reggie's Portra vs Kodachrome 64
- Reggie's Portra vs Kodak Portra 400
- Classic Cuban Negative vs Leica X
- Classic Cuban Negative vs Classic Chrome
- Classic Cuban Negative vs Kodachrome 64
How this works
How this works
A photographer submits a RAW file. We connect a real Fujifilm camera over USB and have its processor develop that one file in every recipe in the catalog, using the same in-camera engine that develops your photos when you shoot. Each render's settings are verified from the camera's own metadata before it's published.
Is this really the camera, or a software simulation?
Really the camera. Every image here is a JPEG developed by a Fujifilm camera's own processor. We send the photographer's RAW file to the camera over USB with a recipe's settings, and the camera develops it exactly as if it had been shot that way. No Lightroom, no presets, no emulation.
Is it the same photo in every recipe?
Yes. Each scene is one single RAW file, developed once per recipe. Everything that changes between two renders is the recipe: same light, same moment, same exposure.
How do you know a render actually matches the recipe?
Every developed JPEG carries the camera's own record of the settings used, written into its metadata. We read that back and verify it against the recipe before a render enters the gallery.
Why is a recipe missing on some scenes?
Physics, mostly. DR400 recipes need the shot to be taken at ISO 500 or higher, and DR200 at ISO 320 or higher; below that the camera refuses. A few recipes also use settings the USB conversion can't reproduce (like toned black-and-whites); those wait rather than render wrong.
About Focal Click
This tool is part of Focal Click.
The place where Fujifilm recipes are proven: compared on the same scenes, read from real files, and shot by the photographers who bring them.
Explore recipes
47 community recipes, proven by 117 real photos. Every setting is read from EXIF, never typed in.
Recipe Extractor
Drop any straight-out-of-camera JPEG and read the exact recipe it was shot with. Free, in your browser, nothing uploaded.
Join free
Keep your favourite recipes on every device, post your shots, and put your name on recipes you bring first. The account is free.
Want a recipe added to the gallery, or found a bug? Tell me. Focal Click is built by one photographer, and you can support it.