reality remixer / how it works

an interactive explainer

How a sentence rewrites a photograph.

No slides. No jargon dumps. Scroll through five interactive scenes and you'll actually understand the AI that powers Reality Remixer — from random noise to a finished edit.

scroll to begin
01the core idea

A sentence should rewrite the photo — not describe it.

Most AI you've met answers with words. Reality Remixer answers with pixels. You hand it an image and an instruction, and it gives back a new image where only the thing you asked for has changed. Flip the switch to feel the difference.

Source photograph of a neon diner at night
input
Photograph edited to: make it snow
edited pixels

A chat model describes a change. An image-native model like FLUX Kontext performs it — returning new pixels while keeping everything you didn't ask to change. That's the whole trick.

02the engine

Every image begins as pure static, then gets sculpted away.

FLUX is a diffusion model. It starts from a field of random noise and, step by step, removes the noise it predicts shouldn't be there — until a coherent image is left behind. Drag the slider to run the schedule yourself, forward or back.

The panel is a simplified simulation — a blur-to-sharp reveal with a noise overlay — built to make the idea legible, not a real inference trace. FLUX's actual intermediate states aren't rendered as images at all.

loading…
step 1/28
0% denoised
simulated, not a real inference trace
noiseimage

Pure Gaussian noise

The model starts from random static — no image at all yet.

03conditioning

Two things steer the noise: your image, and your words.

A plain diffusion model would invent something random. Kontext is conditioned: your source image anchors what stays the same, and your instruction pulls the result toward the change you want. It denoises toward the version of reality that satisfies both.

Source image input
image → what stays
"make it snow" → what changes
Conditioned result
denoised toward both
04the plumbing

Behind the button: a submit, a poll, and a handoff.

Generation isn't instant, so the API is asynchronous. Your server submits the job, polls until it's ready, then fetches the finished image and streams it back. Press run request to watch a real round trip.

Browser

your app

Your API

/api/remix

Black Forest Labs

FLUX Kontext

idle

// press “run request” to trace a live edit

Everything past your API runs server-side. Your key never reaches the browser, and because the server fetches the short-lived signed image and hands back a data URL, the result never expires and never trips CORS.

05the interface

Nothing is overwritten. Every edit is a branch.

Because each result is just data, we keep all of them. Your edits form a tree you can climb — rewind to any point and take reality somewhere new, without losing where you've been.

seed+ snow+ sunset→ noir+ neon+ fogclose-up

Editing is non-destructive. Every instruction forks a new node from the one you're on — so you can rewind, branch a different direction, and keep every version. Click any node above to trace its lineage back to the original seed.