Scroll Animation Website Builder
One prompt builds a site where scroll moves the camera — dive into a scene, fly out, land in the next, no cuts.
Katagiri High — The Last Light, built in the Horimiya world for this page. Scroll inside the frame: three scenes, two seams, one continuous flight.




SENGOKU
SENGOKU
SENGOKU
Five Realms
Five Realms
Five Realms
Homer’s Odyssey
Homer’s Odyssey
Homer’s OdysseySee it live.
Open the work and use it here.
A scroll site is a flight, not a slideshow.
Studio generates the world, one 16:9 still per scene, and the camera clips that carry you between them. The page that ships is plain HTML and vanilla JavaScript: scroll position sets video time, so it runs on a phone, needs no framework, and weighs about as much as three short videos.
- Seams, not cuts — Each connector is generated from the last frame of one clip and the first frame of the next, so the join is identical rather than crossfaded.
- One look across scenes — Every scene still is derived from a single master image, so the harbour in scene one is the same harbour in scene three.
- A page, not a video — You get a published URL you can open, fork and send. Scene titles, eyebrows, stat rows and nav labels are plain HTML you can edit.
Questions people ask before building one.
What is a scroll animation website?
A page where scrolling drives a camera instead of just moving the page. Each scroll position is a frame of video, so the visitor flies through the scene at their own speed instead of watching a clip play.
Do I need GSAP or Three.js?
No. The engine is plain JavaScript that scrubs pre-rendered clips by scroll position. It drops into a GSAP or Next.js site if you already have one, but nothing here requires either.
How many scenes should I start with?
Three. That is roughly 25 MB of video at 16:9 — quick to load and already reads as a journey. Every extra scene adds two clips, about 9 MB more.
Will it work on a phone?
Yes. Small screens get a 640×360 encode and the scrub follows touch scrolling; the heavy desktop clips never load there.
What does one build involve?
Three stills, three dive clips and two connectors — eight generated assets. Ask Studio for the clip count and the model before it starts, because video is the slow, paid part.
Can I edit the copy afterwards?
Yes. Scene titles, eyebrows, stat rows and nav labels are plain HTML in the published page. Change the words without re-rendering a single frame.
What happens if a generation fails?
The build stops and tells you which clip failed. It will not fill the gap with placeholder art, because a fake scene breaks the seam and the illusion with it.
Can I use an existing IP or my own art?
Yes. Scenes can be derived from a reference still, and the worlds on this page were built inside existing IP worlds. Bring a character sheet or a key visual if the look has to match something.
Give one place three stops.
Studio generates the scenes, the dives and the seams, then publishes a page you can scroll and send. Start with the harbour below, or write your own place.