As XDA Developers highlighted in its coverage, the project lands right alongside another eye-catching entry in the same AI-assisted "vibecoding" wave: Voidstruck, a sci-fi browser game created with Claude that squeezes a procedural galaxy of 150 million star systems into a 299 KB HTML file. Naturally, whenever someone claims an entire 3D world fits inside a file smaller than a modest JPEG, healthy skepticism should kick in immediately. Did Anthropic's AI somehow reinvent data compression, or is something much cleverer—and much more demanding on your PC's graphics card—happening under the hood?
The answer reveals both the promise of modern browser graphics on Windows and the real engineering workflow behind AI-generated code.
Small File Size Does Not Mean Small Graphics Workload
The first rule of Atlantis is simple: the HTML file does not actually contain 3D models, bitmap textures, audio recordings, or external JavaScript libraries. There is no Unity, no Unreal Engine, and no Three.js download waiting in the background. Instead, the file holds compact mathematical recipes and shader code. When you open index.html, your browser unpacks the compressed script in a few milliseconds and hands the instructions directly to your GPU via WebGPU, generating the city on the spot.
According to Noniv's GitHub README, the city itself—modeled around descriptions of Atlantis associated with regression hypnosis—features concentric rings of canals surrounding a stepped podium, a 105-meter quartz-like crystal sitting inside a crystal lotus, six spiral crystal towers, glass domes, marble villas, swaying flowering trees, a harbor, farmland, waterfalls, and limestone mountains under a golden-hour sun. Even the background audio is a 32-bar chiptune loop synthesized live through the browser's Web Audio API rather than streamed from an MP3.
Crucially, "tiny download" is the exact opposite of "lightweight hardware requirements." Because the scene is built and shaded dynamically at runtime, your graphics processor does heavy lifting every single frame:
- Direct WebGPU pipeline: Rather than wrapping older WebGL calls, the demo talks directly to WebGPU, the modern W3C graphics and compute API backed by Direct3D 12 on Windows, Metal on macOS, and Vulkan.
- GPU-driven culling and instancing: A compute pass runs each frame to discard off-screen geometry and pick level-of-detail tiers for parametric shapes—buildings, bridges, trees, and crystals—drawn via instancing.
- Modern lighting effects: Because the sun stays fixed, the sky, large shadow maps, and environment lighting are baked once at load time. Frame by frame, the renderer still executes sun shadow cascades, canal mirror reflections, deferred lighting with ambient occlusion and light shafts, translucent water and refracting crystal shaders, temporal anti-aliasing (TAA), bloom, and AgX tone mapping.
In plain English: Atlantis is closer to classic demoscene programming than a static web toy. Compressing instructions into 96 KB saves bandwidth, not silicon.
Section summary: Atlantis keeps its download under 100 KB by storing procedural math and WebGPU shaders instead of heavy 3D assets, shifting the real workload onto your device's GPU at runtime.
Collision Detection and Flying Around the City
Many ultra-compact browser graphics demos are little more than glorified screensavers: pretty fly-throughs where the camera ghosts straight through marble walls. What caught XDA Developers' attention—and what makes Atlantis feel closer to an actual game sandbox—is that Noniv's project includes real collision geometry alongside full free-flight controls.
Per the repository documentation, the ground, water surface, quays, bridges (including space underneath their arches), the central podium, the great crystal, towers, domes, and buildings are solid surfaces that you glide along rather than clip through. Foliage such as trees, bushes, and rocks remain pass-through so exploration never snags on branches—and if you want pure noclip freedom, pressing C toggles collision off at any time.
| Control | Action | Notes |
|---|---|---|
| Click scene + Mouse | Look around | Captures pointer; Esc releases mouse and opens menu |
| W / A / S / D | Fly horizontally | Standard directional flight |
| Q / E | Descend / Ascend | Vertical movement |
| Hold Shift | Boost speed (8x) | Jumps from 12.5 m/s normal speed to 100 m/s |
| Mouse wheel / Middle click | Adjust flight speed | Ranges from 0.25 to 50 m/s; middle button resets to 12.5 m/s |
| Keys 1–6 | Jump to viewpoints | Snaps to six curated camera spots |
| C / M / H | Toggles | Collision (C), live chiptune music (M), performance stats (H) |
Touchscreen users are also accounted for: holding one finger flies forward and steers, a second finger boosts speed, and phones held vertically automatically orient the view into landscape mode.
Section summary: Unlike passive shader demos, Atlantis pairs full 6-DOF flight and camera presets with selective solid-surface collision that users can toggle on the fly.
How Claude Fable 5.2 Actually Built It
Whenever a viral post declares that an AI model "built an entire 3D world," it is tempting to picture a developer typing a single sentence, grabbing coffee, and returning to a finished masterpiece. The actual files in Noniv's GitHub repository tell a far more grounded—and instructive—story for software developers.
The project was built using Claude Code powered by Claude Fable 5.2, Anthropic's technical frontier model introduced on November 9, 2026. Designed for demanding reasoning and long-horizon agentic coding—with a 1-million-token context window, up to 128,000 output tokens, and always-on adaptive thinking—Fable 5.2 is available across Anthropic's Claude Platform as well as AWS, Google Cloud, and Microsoft Foundry.
Yet Noniv did not just hand Claude a blank check. The repository openly preserves the human scaffolding that kept the AI on track:
- An explicit engineering prompt (
prompt.txt): It locked in hard architectural rules—WebGPU only, zero external engines or libraries, full procedural generation, and a concrete frame-time budget. - A detailed art bible (
artstyle.md): This document spelled out the concentric city plan, marble and crystal materials, vegetation species, water behavior, lighting mood, and six specific review camera angles. - Visual reference art (
concept-art/): Noniv supplied eight concept images created with ChatGPT so the coding agent had visual targets rather than vague adjectives. - Automated self-critique and profiling: As Noniv explained in the README and on Reddit, a separate subagent inspected actual rendered frames solely against the art bible and concept images to flag visual defects, while a scripted 60-second flight measured GPU frame times.
That workflow highlights an important reality about late-2026 AI coding: models like Claude Fable 5.2 can write complex WGSL shaders, layout math, and Web Audio synthesizers autonomously, but strong human constraints, visual specifications, and automated test loops remain the difference between broken slop and a cohesive demo.
Section summary: Atlantis was not conjured from one casual prompt; it combined Claude Fable 5.2 in Claude Code with a strict human-authored specification, ChatGPT concept art, and an automated visual-and-performance feedback loop.
Windows Browser Requirements, Performance, and GPU Pitfalls
Before you download index.html—it runs offline as well as on the live GitHub Pages site—there are a few Windows and browser realities worth knowing.
First, your browser must support WebGPU. Although WebGPU first arrived by default in Chrome 113 and Microsoft Edge 113 back in May 2023—and later reached Firefox 141 on Windows in July 2025 and Safari 26 on Apple platforms in September 2025—cross-platform support still varies, and MDN continues to classify the API as having limited availability across all environments. Noniv specifically recommends Microsoft Edge or Google Chrome on a desktop PC for the smoothest experience.
Second, reported performance varies dramatically by hardware. In the README, Noniv reports that an NVIDIA RTX 5070 Ti renders a frame on High at 2560 × 1440 in roughly 2.5 milliseconds, while a budget Samsung Galaxy A16 phone manages about 28 frames per second on Low at 660 × 378. Those figures are creator-reported observations on specific devices rather than an independent lab benchmark, and your mileage will depend heavily on your GPU.
To help prevent weaker machines from choking, Atlantis includes automatic quality tiers and dynamic resolution scaling whenever frame rates dip below 60 fps:
- High: Selected automatically on desktop PCs, rendering the full shader and reflection suite.
- Medium: Caps resolution at 2560 × 1440, shrinks shadow maps, uses cheaper reflections, and simplifies distant geometry (default for 8 GB phones).
- Low: Caps resolution at 1280 × 720 and disables ambient occlusion, light shafts, polished-stone reflections, and full canal reflections. The page picks this automatically for devices with 4 GB of RAM or less, lower-memory phones, and Windows PCs running the browser on integrated Intel graphics.
If you are on a Windows laptop with hybrid graphics (for instance, an Intel or AMD iGPU paired with a discrete RTX or Radeon GPU) and notice sluggish frame rates or Low quality kicking in unexpectedly, Windows may be routing Edge or Chrome to the power-saving chip. Noniv's README outlines the exact Windows fix: open Settings → System → Display → Graphics, select your browser (msedge.exe or chrome.exe), and switch its GPU preference to High performance. One extra troubleshooting tip from the developer: if a graphics driver crashes several times while loading heavy WebGPU shaders, Chromium browsers like Chrome, Edge, and Opera will temporarily disable WebGPU entirely. If the demo complains that no graphics card is available, close every browser window completely and relaunch.
Section summary: Desktop users on Windows should run Atlantis in Edge or Chrome, verify that hybrid-graphics laptops assign the browser to the high-performance GPU, and expect quality tiers to scale automatically on integrated graphics.
Inspecting, Tweaking, and Rebuilding the Code
For developers and curious tinkerers, perhaps the best part of Atlantis is that it is released under the MIT license with readable, modular source files sitting right next to the packed HTML build.
Instead of a single obfuscated wall of minified text, the source/src/ directory splits the project cleanly into 15 focused JavaScript modules—covering everything from layout.js (city rings and fly-through paths) and collide.js (solid surface bounds) to sh_fx.js (water, crystal, and glass shaders) and music.js (tempo, root note, scale, and volume). If you have Node.js 18 or newer installed, cloning the repository lets you modify parameters—such as raising the 100 m/s boost speed in main.js—and rebuild locally via npm install and npm run build. Developers can also build an unminified copy (npm run build:readable), an unpacked 194 KB HTML build (node build.mjs --unpacked), or dev.html (npm run build:dev), which unlocks F for the automated 60-second fly-through and B to run GPU timing benchmarks.
Ultimately, Atlantis is less about magic compression and more a crystal-clear demonstration of two converging trends: WebGPU finally bringing near-native Direct3D 12-class rendering pipelines to zero-install web pages, and AI coding agents like Claude Fable 5.2 handling complex multi-file shader math when paired with disciplined human direction. You still need decent GPU silicon to tour the marble canals at 1440p—but being able to email an entire interactive 3D world as an attachment smaller than a holiday photo is a pretty remarkable sign of where browser engineering is heading.
Correction (November 22, 2026): An earlier version of this article said the source/src directory contains 16 JavaScript modules. The repository actually lists 15 JavaScript files there; the sixteenth file in the README table is the HTML template, which lives in the parent source folder. The count has been corrected.
References
- GitHub - Noniv/atlantis: A procedural Atlantis you can fly through in the browser: a marble garden city with crystal towers, canals and mountains at golden hour. One 95 KB HTML file with no images, models or libraries, rendered with WebGPU. Built with Claude Code. · GitHub github.com
- People are still doing amazing filesize feats with Claude, as this Atlantis scene clocks in at 96KB XDA · 2026-11-22T07:48:51+00:00
- mozilla.org developer.mozilla.org