Five steps between a photograph and a URL you never have to change.

A Photo is an identity.
Files are candidates for it.

Photograph

01
Add candidate photographs
Create a Photo for a place on your website, then drop one or more files on it. This release processes JPEG, PNG, WebP, and TIFF, one HEIC, and a Canon EOS 7D sRAW2. Dropping a file does not process or publish it.
ph_001 · 3 candidates
02
Run a pipeline
A pipeline normalizes orientation and colour, cleans edges, composes each framing (main 4:3, card 1:1) and encodes renditions. Saving a pipeline makes a new revision; earlier runs keep the one they used.
rev 6 · 6 renditions
03
Review outputs
Compare candidates and compositions side by side, check the crop and the focal point, and see the failure code if a candidate is too small for a composition. A successful run publishes nothing on its own.
out_main_b · from run_104
04
Publish to the stable URL
Approve and publish selects one output per composition. The URL already existed; now it answers. Replace, roll back or withdraw later without touching your HTML.
Same address since day one
05
Deliver with your policy
The watermark and the protection policy of the project are applied at delivery and cached at the edge. Change either and delivered renditions are re-rendered from clean outputs.
At the edge within a minute

What changes, and what does not

You do thisWhat happensURL

Replace the photographSelect another output as live. Next request serves it.Same URL

Edit the pipelineNew revision. Existing outputs and publications unchanged until you run and select.Same URL

Change the watermarkRollout re-renders delivered renditions from clean outputs. Pipeline does not run.Same URL

Add a composition or renditionA new thing to embed gets a new path.New URL added

Withdraw the PhotoURLs answer 410 Gone or a neutral placeholder. Reversible.Same URL · 410

Delete the PhotoSources and outputs are removed. Not reversible.Same URL · 404 forever

Start with one photograph.