Splats to Mesh converts an Atlas Gaussian splat into a GLB mesh with real geometry, so you can use the world in Blender, Unity, Unreal and other tools that don't render splats well. You choose how the mesh is textured, how many faces it keeps and which part of the scene to extract. This guide covers the options and the import steps for each tool, as of November 2026.
Why convert a splat to a mesh
A Gaussian splat is the highest-fidelity output of Atlas. It looks right, but most game engines, physics systems and DCC tools expect triangles. World Labs lists Splats to Mesh as a launch tool for "games and interactive environments", and the matching API task is splats2Mesh. The task overview describes it as converting a splat into a GLB mesh, with optional texture or vertex colors and optional collider boxes.
Use a mesh when you need:
- collision and physics in a game engine;
- editable geometry in Blender or another DCC tool;
- a format that every engine imports without a splat plugin.
Keep the splat when visual quality is what matters. Meshes derived from splats carry some reconstruction artifacts.
Step 1: Start from a clean splat
Mesh quality depends on the splat, and the splat depends on your views. Before reconstructing:
- cover every area you will look at, including floors and the far side of objects;
- remove views where objects change shape or position;
- expect trouble with thin structures, glass, sky and foliage.
A refined splat costs 5,000 credits ($5) through the API. The output is an SPZ file, which is the input splats2Mesh expects. See Viewfinder for building the scene.
Step 2: Choose the mesh options
These are the main request fields from the splats2Mesh API reference:
| Option | Values | Default | What it does |
|---|---|---|---|
textureMode | image_texture, vertex_color, none | image_texture | image_texture projects rendered views onto a UV atlas; vertex_color bakes per-vertex colors; none leaves the mesh untextured |
textureSize | Integer, 1 to 8192 | 4096 | Width and height of the texture atlas in pixels (image_texture mode only) |
targetFaces | Integer, 1 or more | Not set (keep every face) | Decimates the extracted mesh to at most this many faces |
colliderBoxes | Options object | Not set | Fits upright boxes around the mesh for collision, returned as a second GLB |
orientedBoundingBox | Box in Three.js coordinates | Not set (whole scene) | Extracts only the region inside the box |
cameras | Camera list, or a strategy such as auto_anchors, manual_anchors or exterior_sphere | Service default | Cameras used to render the splats for texturing |
Choosing values:
- Texture size. One rendered view plus its border has to fit in the atlas, so
textureSizemust be at least 2% above the render size in use. Start with the 4096 default. Go to 8192 for hero assets viewed up close. - Vertex color suits very dense meshes and quick previews, since it needs no UVs. Color detail is limited by vertex density.
- Face budget. Pick
targetFacesbased on your engine budget. A target above the extracted count does nothing. - Collider boxes stay upright and turn only around the vertical axis. They work for walls, floors and furniture blocking, not for exact collision.
Step 3: Run the conversion
In the web app, run Splats to Mesh on your splat. Through the API, submit the task with the splat's asset ID:
curl --request POST "$WLT_API_BASE_URL/tasks:splats2Mesh" \
--header "WLT-Api-Key: $WLT_API_KEY" \
--header "Idempotency-Key: mesh-job-001" \
--header "Content-Type: application/json" \
--data '{
"splatAsset": { "assetId": "asset_your_splat_id" },
"textureMode": "image_texture",
"textureSize": 4096,
"targetFaces": 500000
}'
The response is an operation. Poll GET /operations/{id} until done is true, then read response.mesh. The targetFaces value above is only an example. See the Atlas API guide for authentication and polling.
Step 4: Download the GLB
A finished operation returns:
mesh: the GLB mesh;colliderBoxes: a second GLB with one node per box, if requested;anchorPositions: the anchor points used to place render cameras, in Three.js coordinates.
Output URLs from tasks work for 24 hours. After that, use the asset ID to create a fresh read link, which lasts 15 minutes.
Prefer a hosted pipeline? Our photos to 3D app goes from photos to a splat and a GLB and is paid with this site's credits.
Step 5: Import the GLB
GLB is the binary form of glTF 2.0, so the import steps are the standard ones for each tool.
Blender
- Open Blender and choose File, then Import, then glTF 2.0 (.glb/.gltf).
- Select the mesh GLB and import it.
- If you requested collider boxes, import the second GLB too. It lines up with the mesh.
- In Material Preview or Rendered view, check that the texture is assigned.
- Save as a
.blendfile to keep working.
Blender 5.3 can also import the original .spz or .ply splat natively, which is handy for comparing the mesh with the splat.
Unity
- Install a glTF importer. Unity's glTFast package (
com.unity.cloud.gltfast) is the common choice. Add it from the Package Manager. - Drag the GLB into your Assets folder. glTFast imports it as a prefab with meshes and materials.
- Drag the prefab into your scene.
- For collision, add a Mesh Collider to the mesh, or import the collider boxes GLB and add Box Colliders to its nodes.
- Check scale against a 1-unit cube.
Unreal Engine
- In the Content Browser, choose Import, or drag the GLB in. Recent Unreal versions import glTF and GLB files directly.
- Accept the import options. The mesh, materials and textures are created as assets.
- Drag the static mesh into the level.
- For collision, generate simple collision in the Static Mesh Editor, or use the collider boxes GLB.
- Large meshes are good candidates for Nanite if your project uses it.
Coordinates and scale
World Labs says Atlas outputs use the OpenGL/Three.js right-up-back (rub) convention unless the schema says otherwise, and splats2Mesh regions and anchors are in Three.js coordinates. glTF is also Y-up, so Atlas meshes should import upright. If a scene comes in flipped, convert once at import rather than rotating objects one by one.
Scale follows the scene's units. Atlas scenes from a single photo have estimated scale, and the docs warn that estimated geometry does not guarantee measured dimensions. Check sizes against a known object before using them for layout.
Fixing common mesh problems
| Problem | Likely cause | Fix |
|---|---|---|
| Holes in thin parts | Chair legs, wires and railings reconstruct poorly | Add views of those parts, or model them by hand |
| Floating blobs | Sky or poorly covered regions | Crop with orientedBoundingBox, delete floaters in Blender |
| Blurry texture | Texture too small for the area covered | Raise textureSize, or mesh a smaller region |
| Doubled surfaces | Views disagreed before splatting | Fix the input views and reconstruct |
| Engine slows down | Too many faces | Set targetFaces lower |
What it costs
Mesh export costs 500 credits ($0.50) per world, according to the Atlas API pricing table in the World Labs console (checked November 14, 2026). Atlas credits are 1,000 per $1. For comparison, Marble's API charges 3,500 credits ($2.80 at Marble's rate) for an HQ mesh export. The two products use separate credit rates, so don't carry the number across. Our pricing calculator helps estimate the splat side.
Next steps
- Build a better splat with the Viewfinder guide.
- Automate the pipeline with the Atlas API.