how it works
Shoot a video. Drive the place.
A new kind of capture: take a video of somewhere real, and turn it into a place you can actually drive through. Not a photo, not a film. The real street, rebuilt so you can move around in it.
It runs in the browser you already have. No download, no install, and no special graphics card. A WebGPU browser is all it asks (Chrome 113+, Edge 113+, Firefox 141+, or Safari 18+).
Three steps, start to finish.
From a phone-grade video of a real place to a scene you can drive in a tab. Here is the whole arc.
- 01ordinary video → raw material
Capture
Someone walks a real place with an ordinary video camera. A street, a shop, a stretch of road. That footage is the only raw material we need.
- 02footage → the place itself
Reconstruct
We rebuild that footage into the place itself: real depth, real light, captured exactly as it looked. Not a model an artist guessed at. The real thing.
- 03a link → you, driving
Drive
The finished place opens in a browser tab and you drive it, live, with your own inputs. Nothing to download, nothing to install.
Captured from life, not modeled by hand.
the usual way
Putting a real place into 3D normally means someone models it by hand from reference. It is slow, and it is always a guess at what was actually there. Then it ships as a heavy download.
this way
We skip the guessing. The place comes straight from footage of the real street, so what you drive is what was there, down to the light on the day. And it arrives over a link, not a launcher.
Real places, in a tab.
It looks real because it is
The places come from real footage of real streets, so they carry the light and depth of the day they were shot. The bar I hold myself to: at a glance, you should not be able to tell whether you are looking at the scene or at a photo of the street.
It opens like a web page
You click a link and you are driving. There is no app, no download, no waiting on a store. It comes up in seconds the first time and faster after that, on the hardware you already own.
More on the browsers, hardware, and the capture pipeline lives in the FAQ.
Words do not do this justice. Open it in a tab and drive.
▶ Try it