How to Turn a Sketch into a 3D World with Atlas
Turn a rough layout sketch into an explorable 3D world with Atlas: block it out in Chisel, prompt the look, restyle it, then render video or splats.
A sketch is the fastest way to say where things go. Atlas by World Labs is good at the opposite half of the job: deciding what things look like. This post shows how to connect the two, going from a napkin floor plan or elevation to a rendered, explorable 3D world, using only steps World Labs documents as of November 2026.
In this post
- What "sketch to 3D" means in Atlas
- Step 1: Read your sketch as a layout
- Step 2: Block it out in Chisel
- Step 3: Frame the shot
- Step 4: Write the prompt
- Step 5: Render, inspect, iterate
- Step 6: Restyle without redrawing
- Step 7: Fix details with masks
- Step 8: From views to a world you can walk through
- An alternative route: sketch to concept image
- Costs and a sensible budget
What "sketch to 3D" means in Atlas
There is no documented "upload a drawing" button in Atlas. The tool built for this job is Chisel. World Labs describes it as a way to shape a world through controllable scene building and grayboxing. In the web app you place simple shapes, and Chisel renders a finished scene that follows their layout. World Labs' Atlas page adds that you can move things around and see every camera view update.
So the workflow is: your sketch becomes a blockout, the blockout becomes depth, and depth plus a prompt becomes a photoreal view. Under the hood this is the atlasChisel task. Its tutorial explains the logic in one line: depth guides layout, known pixels guide appearance, and the prompt fills in the rest.
That split is useful. Your sketch only has to be right about where and how big. Materials, light and detail come from text, and you can change them later without redrawing.
Step 1: Read your sketch as a layout
Before opening the app, mark up the sketch with what Chisel will need:
- The large forms. Buildings, walls, towers, rooms, terrain steps, big furniture. Ignore windows, trim and ornament.
- Rough dimensions. Even "about 10 m wide, 6 m tall" helps you keep proportions. Atlas works in consistent scene units. World Labs' chapel tutorial uses metres for both camera positions and depth.
- Where the viewer stands. Draw an arrow for the camera. A scene seen from a doorway needs different blocks than one seen from above.
- What must not change. If the courtyard must be square and the tower on the left, those go in the blockout. Anything left to the prompt is a suggestion.
A floor plan converts easily: each room or object becomes a box extruded to its height. An elevation or perspective sketch needs one more step, guessing depth, but the same rule applies. Block the big volumes and nothing else.
Step 2: Block it out in Chisel
Open Chisel and recreate your sketch with primitives. The docs mention that the Chisel editor shows each node's rotation in degrees, so you can type exact angles when a wall needs to sit at 30°.
Tips for a good blockout:
- Use distinct volumes for distinct things. A low wall and the ground should not merge into one slab. In World Labs' own example, a low solid wall came back as a fence because the depth alone didn't say "wall".
- Put boxes where you need furniture. The docs are explicit: if you need specific furniture positions or sizes, add that geometry to the blockout. A prompt alone won't place a sofa against the left wall.
- Leave the sky empty. Sky should be "no surface". A big sky dome is treated as real geometry and can distort the depth range.
- Keep it coarse. Extra detail in the blockout doesn't translate into better results. The prompt adds the detail.
Step 3: Frame the shot
Place a camera where the arrow on your sketch was. Chisel renders 1280 x 720 views and needs depth rendered at each target camera. The editor handles that. If you work through the API, you supply a linear-depth EXR or an inverted log-depth PNG with its near and far bounds.
Start with one camera. It is the cheapest test, and it tells you quickly whether the blockout reads the way you meant.
Step 4: Write the prompt
The prompt does what the sketch can't. Write it as a caption of the finished scene, not as instructions. A structure that works well:
- Subject and setting: "A small hillside monastery above a terraced olive grove"
- Materials: "whitewashed stone walls, terracotta roof tiles, weathered wooden doors"
- Light and time: "late afternoon sun from the left, warm haze"
- Mood and camera style: "documentary architectural photography, no people"
Name the objects your blocks stand for. If a box is meant to be a well, say "a stone well in the center of the courtyard". Depth tells Chisel there is something there, and the prompt tells it what.
Prompt enhancement is on by default and expands short prompts using the scene. Turn it off when you want the exact wording used, which helps when comparing versions. A Chisel caption costs 20 credits per request in Atlas Studio.
Step 5: Render, inspect, iterate
Render the single view and compare it with your sketch:
- Are the silhouettes right? Roof lines, tower heights, gaps between buildings.
- Did anything turn into something else? Walls into fences, steps into ramps.
- Did the model add things you didn't plan? Windows and doors are usually welcome. Extra buildings are not.
World Labs' tutorial warns that generated detail is not proof of geometric accuracy, and that depth guides generation without guaranteeing exact reproduction. When something is wrong, fix it at the right level:
| Problem | Fix it in |
|---|---|
| Object in the wrong place or wrong size | The blockout (then re-render depth) |
| Object is the wrong kind of thing | The prompt (name it explicitly) |
| Wrong materials or light | The prompt |
| Object should disappear | The blockout, or mask it out (see Step 7) |
Once one view looks right, add more cameras around the scene.
Step 6: Restyle without redrawing
This is where sketch-first work pays off. Keep the blockout, the cameras and the seed the same and change only the prompt. World Labs' tutorial takes a chapel from golden hour to a snowy blue-hour scene this way. The layout holds and everything else changes.
Useful variations from the same sketch:
- seasons: summer meadow, autumn leaves, winter snow;
- time of day: midday, golden hour, night with lit windows;
- style: photoreal, weathered and abandoned, freshly built;
- setting: the same building in a forest, on a coast, in a city block.
One rule: don't feed the previous render back in as a context image when restyling. The docs note that the old appearance competes with the new prompt. Use depth for layout and text for looks. For lighting changes specifically, see the Relight guide.
Step 7: Fix details with masks
For local changes, such as removing a fence or swapping a door, use a masked edit instead of re-rendering. Send the rendered view with a grayscale keep mask: white keeps pixels, black marks what to regenerate. Then describe the result you want.
From the docs:
- Cover the whole object plus its shadow and reflections. If remnants outside the mask still suggest the object, enlarge the mask.
- To remove an object completely, leave its old depth out. Otherwise the depth keeps the shape.
- To change only color or material, keep the depth with an all-white depth mask, so only the pixels change.
- If an object turns into a different object instead of disappearing, check the mask before adding more prompt words.
Step 8: From views to a world you can walk through
A single render is a picture. To make it a world, render several views around the scene, check that they agree, and turn them into a video or a Gaussian splat.
- Agreement matters most. If the well is round in one view and square in another, the splat will show a ghosted double. Remove views that disagree.
- Cover what you will look at. Areas no view shows come out blurry or invented.
- Move the cameras, don't just rotate them. Atlas needs camera translation to recover depth scale. The Chisel troubleshooting table says a one-view request with depth output is rejected unless you add at least two translated targets.
The splat step, posedImages2Splats, needs depth on every frame. A draft run (refine: false) costs 500 credits, so it's a cheap way to check that your Chisel views reconstruct cleanly before paying 5,000 credits for a refined run. Then open the result in Blender, on the web, or convert it with Splats to Mesh for a game engine. For camera paths and video, see the Viewfinder guide.
An alternative route: sketch to concept image
If you'd rather not block out geometry, there is a second documented path that starts from an image:
- Describe your sketch in text and generate a starting image with
atlasTextToImage. - Pose it (
images2PosedRGBD) to get a camera and depth. - Generate views around it with
atlasGenerate, as in Viewfinder.
This is quicker for mood and atmosphere, but you give up the layout control that makes the blockout route worth the effort. Atlas invents everything outside the first image.
Costs and a sensible budget
Published numbers as of November 2026:
| Item | Credits |
|---|---|
| Chisel caption (Atlas Studio) | 20 per request |
| Prompt enhancement (Atlas Studio) | 20 per request |
| Image edit (Atlas Studio) | 125 per request |
| Splat, draft | 500 |
| Splat, refined | 5,000 |
Through the API, Chisel costs 40 credits for the first output frame and 8 for each additional one, or 50 and 10 with depth (RGBD), per the Atlas API pricing table in the World Labs console (checked November 14, 2026). Calls to third-party models, such as the Chisel agent's, are billed at the provider's rate. A sensible order of spending: one-view tests until the layout reads right, then a ring of views, then a draft splat, then a refined one. Each step costs more than the last, so catch problems early.
If you want to skip the setup and go straight from photos to a splat and a GLB, our photos to 3D app runs that pipeline. For everything else, start at the Atlas World Model home page or the full step-by-step guide.