Flipbook Deep Dive: When the Whole Internet Becomes an AI Pixel Stream
> Project: Flipbook — Infinite Visual Browser > Released: 2026-04-22/23 > Team: Zain Shah (ex-OpenAI, Samsung, YC S13), Eddie Jiao (ex-Humane/Slack), Drew O'Carr (ex-Apple) > Affiliation: South Park Commons (compute sponsored by Modal Labs) > Live demo: flipbook.page
Key points
- Flipbook is not a "better browser" — it replaces the browser concept entirely. Every pixel on screen is generated by a model in real time, making HTML, CSS, and DOM an optional legacy layer.
- Type "plan a Paris trip" and instead of nav bars and card lists, you get a single fully custom illustration — map, photos, schedule, and clickable hotspots. Click the Eiffel Tower and the image morphs into a new tailored illustration.
- The stack: LTX Video (Lightricks' open-source Diffusion Transformer video model) generating frames on demand; Modal Labs serverless GPUs; WebSocket streaming at 1080p 24fps; an interaction loop of visual understanding → intent inference → agentic web search → new prompt → generation → streaming, all within seconds.
- Text rendering errors: misspelled or misplaced text (high severity)
- Factual accuracy: no citations, invisible hallucinations (medium)
- Cost: 100–1000x a traditional page (high)
- Latency: seconds vs milliseconds (high)
- Accessibility: screen readers cannot parse pixels (high)
- SEO/indexing: search engines cannot crawl image content (high)
- State and actions: no real booking, purchase, or form submission; no cross-page consistency (medium)
- For 30 years the UI stack was
app → page → component → DOM → CSS → pixels. Flipbook flattens it tointent → model → pixels, dissolving HTML, CSS, React, and the browser engine into the model. This mirrors input-side trends (voice/vision replacing keyboard/mouse), forming an end-to-end model-native experience. - Compared with DeepMind Genie 3 (world model, persistent minute-scale 3D worlds, keyboard/controller input), Flipbook targets information browsing with page-level consistency. Both point the same way: rendering output is becoming model inference rather than a component tree.
- Versus generative UI (Vercel v0, Claude Artifacts), which outputs AI-generated *code* (editable, maintainable), Flipbook skips code entirely: AI → pixels. Short term, generative UI is more practical; Flipbook represents the ultimate simplification.
- Official site: flipbook.page
- Official FAQ: sketchapedia.com/flipbook
- Zain Shah on X: x.com/zan2434
- Simon Willison's take: x.com/simonw
- LTX Video (Lightricks): github.com/Lightricks/LTX-Video
- Modal Labs: modal.com
- DeepMind Genie 3: deepmind.google/genie
Traditional Web vs. Flipbook
| Dimension | Traditional Web | Flipbook | |---|---|---| | Output unit | HTML/CSS/JS → DOM → pixels | Model directly outputs pixels | | Text rendering | Browser font engine | Pixels painted by image model | | Interaction | Predefined buttons/links/forms | Click any region → new prompt → new image | | Animation | CSS/JS | LTX Video real-time stream, 24fps | | Latency | ~100ms (CDN cached) | Several seconds (real-time generation) | | Cost | ~$0.0001/page | ~$0.01–0.1/page (GPU inference) |
Current hard limitations
Zain Shah is candid in the FAQ: Flipbook has limited functionality designed around visual explanation, and capabilities will expand as models become more accurate and stateful. It is a technical demo proving possibility, not a finished product.
Why this is a "direction signal," not a product
Independent assessment
1. "HTML is dead" is clickbait, but "HTML is no longer the only answer" is real. Deterministic, auditable, low-latency scenarios (e-commerce checkout, banking, admin systems) stay on DOM; exploratory, explanatory, immersive information consumption is where pixel streams shine. 2. The real bottleneck is state, not model capability. Useful products need cross-page consistency, persistent state, and structured actionable outputs — likely a hybrid architecture: model-generated visual layer + deterministic transactional code. 3. The cost curve governs adoption. At ~$0.01–0.1/page vs near-zero for static pages, mainstream use needs ~100x cost reduction or high-value use cases (travel planning, education). GPU price-performance trends could make this moot in 3–5 years. 4. Accessibility is an ethical issue, not a technical one. A parallel structured-text channel for screen readers is non-negotiable for public-facing products.
Actionable takeaways for product teams
1. Don't panic — HTML/CSS/JS won't vanish in 5 years, but start experimenting with model-native interfaces. 2. Segment use cases: deterministic scenarios keep the classic web; explanatory scenarios try pixel streams or hybrids. 3. Invest in visual understanding (segmentation, OCR, object detection) to bridge pixel interfaces and functionality. 4. Prepare hybrid architectures; don't do everything with diffusion models. 5. Watch open-source video models (LTX, CogVideo, SVD) — their maturity determines pixel-stream viability.
A philosophical question: do design systems survive?
If every interface is generated from scratch, what remains of the design system? Possible answers: prompts as the new design system ("generate an Apple HIG-compliant button"), style embeddings for brand consistency via fine-tuning, or post-processing layers applying deterministic rules. Design tools themselves may shift from Figma's Auto Layout to "give the model an intent and let it decide the layout."