Community

Every post carries its recipe

On most photography sites a published image is a flat file. Whatever was done to it is gone — you can admire the result and you cannot learn from it. Asking how a look was made gets you a comment thread and a guess.

Here a post is the edit, not a picture of the edit. The exposure, the tone curve, the HSL bands, the split toning and the local masks travel with it as data. That is why every post has a before and an after that actually correspond, and why the numbers under it are exact rather than estimated.

Deconstruct, then remix

Opening a post gives you two things a gallery cannot. The Deconstruction Engine replays the edit in six cumulative stages — RAW, light, curves, colour, masks, finish — so you can see which stage did the work rather than only the sum of all of them. Most looks turn out to depend on one or two decisions and a lot of small ones that barely matter.

Remixing takes that recipe onto your own photograph. Because it is a recipe and not a filter, every value stays editable: you can take somebody’s colour grade, keep their split toning, and throw away their contrast. The same look can leave as a Lightroom .xmp preset or a .cube LUT for video work.

Publishing here

Publishing needs an account, but reading does not, and neither does the Studio — you can deconstruct your own edits without signing up for anything, because the processing happens in your browser rather than on a server. A post is created by dropping a photograph and its sidecar together, so the recipe is read from the file rather than typed in, which is what keeps the published numbers honest.