Abyssal Garden: how Claude built a 97 KB underwater world
Key takeaways
- Abyssal Garden is a swimmable underwater scene in a single 97 KB HTML file with no images, models, sounds or libraries
- Everything is generated by code on load using WebGPU shaders and Web Audio, with Three.js and Babylon.js explicitly banned
- The developer reports about 180 FPS at 2560 x 1440 on an RTX 5070 Ti, but that figure is unverified
- It is a graphical demo rather than a full game, and the build still took about three days of subscription-limited Claude time
How does a swimmable underwater world, complete with kelp forests, manta rays and a sunken ship, fit into a single 97 KB file? Abyssal Garden, a browser demo built with Anthropic's Claude Code, does it in 97 KB by generating everything from code at launch rather than shipping any artwork at all.
What Abyssal Garden actually is
Abyssal Garden is a single HTML file that opens as an explorable underwater environment. Visitors swim with WASD keys, the mouse and vertical swimming controls through dense kelp, past a sunken ship, a stone whale tail, manta rays and schools of fish, under light rays falling from the surface.
The project was shared on Reddit and credited by Wccftech to a developer called Noniv. XDA Developers, covering the same project, attributes the post to a user named Any-Reputation8118. The source code is on GitHub under the MIT licence, and the demo plays in the browser, ideally in Chrome or Edge with WebGPU support.
The notable part is what the file lacks. There are no images, no 3D models, no sound files and no libraries. Anything you see or hear is computed when the page loads.
How it works
Think of the difference between shipping a photograph and shipping a recipe. A conventional game ships the photographs: textures, meshes and audio files, often gigabytes of them. Abyssal Garden ships the recipe and cooks the meal on your machine every time.
The ingredients, according to the project's repository, are WGSL shaders (WebGPU Shading Language, the code that runs on the graphics card), a seabed sculpted on the GPU, roughly two million kelp leaves and plants, tens of thousands of rocks, and thousands of creatures and decorative objects. Sunlight filters through the surface, caustics (the rippling light patterns on the seabed) animate, and floating particles drift past. The soundtrack is synthesised live through the Web Audio API rather than played from a recording.
WebGPU is the browser's modern interface to the graphics card, the successor to WebGL. It lets a page hand the GPU large amounts of work directly, which is why millions of kelp leaves are feasible in a tab.
The prompt and the checking loop
The developer says the first version came from one detailed prompt to Claude Code. It specified visual quality, procedural generation, stable frame pacing and a self-contained HTML deliverable, and it banned Three.js and Babylon.js, two popular browser 3D libraries.
The prompt also built in verification. A separate AI subagent was to inspect rendered screenshots and flag visual defects, while GPU timing measurements judged performance during a scripted 60-second fly-through. In effect, Claude was asked to review its own output before declaring it finished.
It was not purely one-shot. Later prompts added collision detection, a start menu and adjustable graphics settings. The developer estimates two to three hours of actual Claude processing, spread across roughly three days because of subscription usage limits.
Who uses this approach and why
Procedural generation is not new, and Wccftech says as much. Wccftech notes that procedural rendering is hardly a new concept.
The practical appeal is straightforward. A 97 KB page loads almost instantly, needs no installer and runs wherever the browser supports WebGPU. The developer reports that even a Samsung Galaxy A16 manages about 20 FPS on the Low preset at reduced resolution.
The same Claude Fable 5.2 model was recently credited with a different kind of showcase: an Unreal Engine 5-based, Gears of War: E-Day-inspired shooter generated through extensive autonomous AI coding. Abyssal Garden sits at the other end of the scale: no engine, a small file and a modest compute budget. Readers following how Anthropic's tooling is evolving may also want to see how Claude Code Projects now runs parallel AI workers.
What the limitations are
The headline performance figure needs care. The developer reports about 180 FPS at 2560 x 1440 on an NVIDIA GeForce RTX 5070 Ti, and Wccftech notes this has not been independently verified.
Abyssal Garden is an interactive graphical demonstration, not a complete game. There is no objective, progression or gameplay loop in the source's description. Wccftech is also candid that procedural rendering is hardly a new concept.
There are practical limits too. WebGPU support varies by browser, hence the Chrome and Edge recommendation. The build needed a detailed, carefully structured prompt, human follow-up requests and three days of calendar time under subscription limits. It was not a casual one-liner.
What this means in practice
For developers, the repository is the useful part. The prompt is published, so it can be read as a worked example of how to brief a coding agent: state hard constraints, ban shortcuts, and define an automated way to check the result. The screenshot-reviewing subagent and GPU timing run are a template for verification that does not rely on the author eyeballing every frame.
For general readers, the demo is playable in a browser tab and the code is MIT licensed, so it can be forked and modified. Readers will need a WebGPU-capable browser, preferably Chrome or Edge, and can choose Low, Medium or High detail presets.
For IT teams, the takeaway is modest but real. Agentic coding tools can now produce a self-contained, dependency-free deliverable from a specification.
Where this is heading
The interesting trend is less the kelp than the workflow: a specification, an agent that builds, a second agent that inspects, and measurable performance targets. Expect more demos built this way, and expect the argument to shift from whether an agent can produce something impressive to how reliably it can be steered and checked. Abyssal Garden is a small, open, inspectable example of that, and anyone curious can open it, swim around and read the prompt that started it.
Frequently asked questions
What is Abyssal Garden?
A swimmable underwater world in a single 97 KB HTML file, generated by Claude Code. It contains no images, 3D models, sound files or libraries; everything is built by code when the page loads.
Does Abyssal Garden use a game engine?
No. The prompt explicitly prohibited engines such as Three.js and Babylon.js. The scene runs directly in the browser using WebGPU and WGSL shaders.
What do you need to run Abyssal Garden?
A browser with WebGPU support, preferably Chrome or Edge. The developer says low, medium and high presets exist, and a Samsung Galaxy A16 reaches about 20 FPS on Low.
Is Abyssal Garden free to use?
Yes. It can be played in the browser and the source code is available under the MIT licence.