Why the Scene Is Drawn in Code, Not Filmed

The scene is a vector illustration animated in code, not a looping video, which is why the page loads with nothing to buffer, stays sharp at any resolution and can react to your mix and the time of day. It also means nothing autoplays, the motion stops if your system asks for reduced motion, and the visuals use no bandwidth once the page has loaded.

Most ambient backdrops online are looping videos. The scene here is different: it's a single vector illustration drawn and animated in code, right in your browser. That choice isn't just aesthetic — it changes how the page behaves in ways a video loop can't match.

Instant, light, and always crisp

There's no video file to stream, so nothing buffers and the page loads almost immediately. Because the artwork is vector rather than recorded pixels, it stays perfectly sharp at any resolution — from a small phone to a large 4K screen — with none of the blur or compression a filmed loop shows when it's scaled up. Drawing a handful of shapes is also far lighter on the battery than decoding video frame after frame for hours.

Genuinely reactive, not a fixed loop

The bigger difference is that the scene responds to you. Light the fire and its glow actually warms the ground around it; raise the wind and the pines begin to sway. A pre-filmed loop plays the same few seconds no matter what you do — a drawn scene can change with your mix and with the real time of day. For more on the idea behind it, read the about page.

Nothing autoplays at you

A drawn scene separates the picture from the sound completely, which makes the page quiet by default. Opening it starts no audio at all: every layer begins at zero, and even a shared mix link waits for you to tap before anything plays, because browsers only allow sound to start from a deliberate gesture. There is no video element that might carry its own audio track, and nothing cuts, flashes or resets the way a looping clip does when it reaches its end and jumps back to the first frame.

Because the motion is drawn rather than recorded, it can also step aside when it should. If your system is set to reduce motion, every animation in the scene stops and you are left with a still illustration — the sound keeps working exactly as before. A filmed loop can't honour that setting; the movement is baked into the footage.

What a screen reader and a keyboard get

The scene is decoration, and it is marked as such: the whole illustration is hidden from assistive technology instead of trying to narrate a landscape nobody asked to have described. What's left exposed is the part that actually does something — each layer's volume is a proper labelled slider announcing its own name and percentage, adjustable with the arrow keys, and every toggle states whether it is on or off. A video backdrop with controls painted over it tends to give a screen reader an opaque box; a drawn scene lets the decoration and the controls be treated differently, because they were never the same object.

On a slow or metered connection

The animation costs nothing to keep running. Once the page has loaded, the scene is computed on your device frame by frame, so no further data moves for the visuals no matter how long you leave it open — a connection that drops mid-session can't stall the picture, and there is no stream to re-buffer when it comes back. Sound is the only thing downloaded, and each layer's file is fetched once, the first time you raise it above zero. That said, this isn't an offline app: the first load, and the first use of each sound, still need a connection.