Last week World Labs opened Atlas, its world model, to everyone. I wanted to see what it could actually do, so I gave it a hard brief: an architectural mash-up that doesn't exist anywhere in its training data, in a hand-painted animation style, with a camera move I could turn into video.
This post covers what I made, how the tool works under the hood, where it fits for 3D scenes, games and video, and how it compares with the other options in 2026.
TL;DR: Atlas's Chisel app takes a prompt, builds a rough 3D blockout of your scene with an AI agent, then "paints" that geometry into consistent images, camera-path videos and an explorable 3D Gaussian splat. Because every output comes from the same 3D layout, the palace looks the same from every angle and in every frame. That's the big difference from text-to-video tools.
Atlas is World Labs' new world model (World Labs is the spatial-intelligence startup co-founded by Fei-Fei Li, and the company behind Marble). It was announced in September and opened to the public on November 12, 2026, with two web apps and an API:
| Tool | What it does |
|---|---|
| Viewfinder | Starts from images. It can build a plausible scene around a single photo, or reconstruct a real space from up to 64 photos. Then you move the camera, set paths and render. |
| Chisel | Starts from geometry. You (or an agent) block out the scene from planes, boxes and basic shapes, style it with text or reference images, and every camera view updates as you edit. |
| Splats to Mesh | Converts Gaussian splats into polygon meshes (GLB) for games, Blender and engines. |
| Relight | Changes the lighting of a splat scene. |
| API | Endpoints such as atlasGenerate ,atlasChisel ,atlasMasked ,images2PosedRGBD andsplats2Mesh . |
Outputs are keyframes (stills), video clips, and 3D Gaussian splats exportable as .spz or .ply.
I used Chisel for this experiment.
Here's the prompt I started with:
A vast outdoor Ghibli-style animated landscape: snow-capped mountain ranges in the distance, rolling lush green meadows and hills below with wildflowers, soft painterly clouds and warm golden light. On a hilltop stands an ancient Mughal-style palace blended with Tudor architecture: red sandstone walls with half-timbered Tudor gables, granite foundations and terraces, white marble domes, chhatris, arched jharokha balconies and minarets, with a winding stone path and gardens leading up to it. Hand-painted watercolor look, whimsical and serene.
I deliberately picked something hard: two architectural vocabularies that never meet in the real world (Mughal domes, pishtaq arches and chhatris on one side; Tudor half-timbered gables and jettied upper storeys on the other), a painterly style, and a big outdoor landscape with depth.
Chisel has a built-in agent (you can pick the model; mine ran on "Gemini 4 Argon" from the model picker). It doesn't jump straight to pixels. It reads the prompt and the reference image, then writes a step-by-step build plan:
Then it builds actual 3D geometry for each step: walls, domes, booleans for openings, curves for paths and tree avenues, scatters for 95 wildflower clusters.
Under the hood, every camera view starts as plain geometry. These are two of the masks Chisel produced from the blockout, before any style was applied:
The palace blockout as a silhouette mask: Tudor wings, minarets and the onion dome.
A low-angle mask of the central dome. This shape is what Atlas "paints" into marble in the final render.
The finished blockout had:
This was the most interesting part to watch. After each step the agent takes a capture from a camera, inspects it, runs a layout check and fixes what's wrong. Some real examples from my session log:
This self-correcting loop is what makes Chisel feel like a junior 3D artist instead of a slot machine. It isn't perfect (two runs timed out on the model and I had to hit Continue), but every fix is grounded in actual 3D geometry, so it sticks.
With the blockout done, Chisel renders each camera through Atlas using render prompts. The agent wrote three lighting variations:
with geometry adherence set to "fine" so the arches, domes and timbered gables keep crisp profiles. Iteration 3 ("Bright midday") gave me 8 renders at 1280×720, one per camera:
Establishing valley view. The grey bastions became red sandstone, with the marble pishtaq, Tudor wings and terraced gardens below.
Mughal marble dome next to Tudor gables: the two architectural styles meeting on one terrace.
Three-quarter view of the bastion, with the minarets, dome and Tudor wings on the upper deck.
East Tudor wing on the sandstone bastion, with snow-capped peaks in the distance.
The upper garden gateway, looking up at the marble facade and a Tudor wing.
Boxwood parterre terrace, stone stairs and the winding path, with the mountain range behind.
The winding stone path climbing past the reflecting pool toward the palace.
The Charbagh reflecting pool. That cypress the agent kept moving is finally out of the water.
What impressed me: the grey boxes became red sandstone, white marble and timber framing, the hill became a wildflower meadow, and the watercolor style held across all eight shots. The minarets are in the same place in every image because they come from the same 3D layout.
Then I asked the agent in plain English:
i want a camera path which shows the front view of the palace to render video
It read the existing camera paths, noticed the active one cut through the western hillside and trees, and replaced it with a front approach that glides over the winding path and Charbagh gardens while keeping the bastions, Tudor gables and central dome centred. It sampled frames along the path to check ground clearance, found the last keyframe clipping the chhatri, and pulled it back wider.
The result: a 240-frame fly-through at 24 fps (10 seconds), which you can export as MP4 or GIF at 8/12/24/30 fps.
The 10-second front-approach fly-through rendered by Atlas, compressed to a GIF for this post.
You also get a keyframe timeline with easing curves, so you can tune the camera speed by hand like in a normal animation tool.
Finally, the output panel offers Splat creation (5,000 credits in my session). This turns the generated views into a 3D Gaussian splat, a scene made of millions of tiny coloured, semi-transparent blobs that renders in real time in a browser or engine. You can download it as .spz (compact) or .ply (wider compatibility).
Total hands-on input from me: one prompt, a reference image, one sentence asking for a video path, and a couple of "Continue" clicks.
splats2Mesh exports GLB with controls for region, max face count, and textures vs vertex colours vs untextured.
import * as THREE from "three";
import { SplatMesh } from "@sparkjsdev/spark";
const scene = new THREE.Scene();
const camera = new THREE.PerspectiveCamera(60, innerWidth / innerHeight, 0.1, 1000);
const renderer = new THREE.WebGLRenderer();
renderer.setSize(innerWidth, innerHeight);
document.body.appendChild(renderer.domElement);
// the .spz you downloaded from Atlas
const palace = new SplatMesh({ url: "./palace.spz" });
scene.add(palace);
renderer.setAnimationLoop(() => renderer.render(scene, camera));
Caveat: splats are not game-ready geometry on their own. For gameplay you'll want the collider/mesh export, and expect some cleanup.
The same endpoints the apps use are available over HTTP:
curl --request GET \
--url 'https://api.atlas-beta.worldlabs.ai/api/v2/assets/<asset_id>' \
--header "WLT-Api-Key: $WLT_API_KEY"
Useful endpoints include atlasChisel (layout → images), atlasMasked (edit only one region), images2PosedRGBD (camera poses + depth from photos) and splats2Mesh (GLB export). This opens up pipelines like "an LLM writes the layout → Atlas renders it → splat to mesh → drop into the engine."
| Atlas (Chisel / Viewfinder) | Text/image-to-video (Veo, Sora, Runway, Seedance) | Real-time world models (Genie 3, Oasis, Odyssey) | Image-to-3D object tools (Meshy etc.) | Manual 3D (Blender / Unreal) | |
|---|---|---|---|---|---|
| Output | Stills, video, 3D splat , mesh | Video clip | Interactive stream | Single 3D objects | Anything |
| Consistency across shots | High : all from one 3D layout | Low to medium: each clip re-imagines the scene | Medium: can drift or forget after a while | n/a | Perfect |
| Camera control | Exact keyframed paths | Prompted or limited | Live (keyboard/mouse) | n/a | Exact |
| Layout control | Graybox geometry + agent | Text prompt | Prompt/image | Per object | Full |
| Exportable 3D asset | Yes (SPZ/PLY/GLB) | No | Mostly no | Yes (objects only) | Yes |
| Time to first result | Minutes to hours | Minutes | Seconds | Minutes | Days to weeks |
| Skill needed | Low | Low | Low | Low | High |
To be fair:
What sold me on Atlas wasn't one pretty image. AI image tools have done that for years. It was getting eight pretty images, a 10-second fly-through and a 3D world that all agree with each other, built from a layout I could inspect and edit.
For game prototyping, previz, environment concept art and consistent video B-roll, that's a real workflow change. For final game assets and anything with characters in motion, you'll still pair it with traditional tools and video models.
If you try it, I'd love to see what you build. Drop your scenes in the comments! 🏰
Built with World Labs Atlas (Chisel), November 2026. All renders and video are my own outputs from the session described above.