3D Terrain

Blog › STL vs OBJ vs GLB — Which Terrain Export for Which Job

STL vs OBJ vs GLB — Which Terrain Export for Which Job

November 9, 2026 · 3 min read

Export a terrain model and the app offers three model formats from the same mesh: STL, OBJ and GLB (plus 3MF for multicolour prints). They contain the same terrain — surface, boundary walls, flat base, buildings, and a route if you draped one — but they answer different questions. Picking wrong costs an hour of re-importing.

The decision table

STLOBJGLB
What it isBinary triangle soup, one solidClassic ASCII/geometry formatglTF 2.0 binary, one mesh
UnitsMillimetresMillimetresMetres (glTF spec)
Watertight solidYes — walls, flat base, skirt geometryGeometry only — no solid guaranteeGeometry only
MaterialsNone (slicer decides)None in current export — assign in Blender/CADPBR-ready container
Opens inEvery slicer: Bambu, Prusa, Cura, OrcaBlender, Maya, CAD tools, MeshLabUnity, Unreal, Godot, three.js, Blender
Best for3D printingSculpting and CAD round-tripsWeb embeds and game engines

STL: the print format

STL is the only one of the three that guarantees a printable solid: the terrain surface is closed by boundary walls and a flat base, so slicers compute layers immediately — no repair pass, no non-manifold surprises. It ships with two scale modes: fit the long edge to a 180 mm print bed, or lock a fixed map ratio from 1:5,000 to 1:50,000. In fixed-ratio mode a building's exported height is its real height, which makes city prints geographically honest.

Buildings and draped routes travel inside the STL, embossed into the terrain — a printed route needs no post-processing.

OBJ: the editing format

OBJ is the oldest format in the room and every 3D tool speaks it. The terrain export writes geometry with a header crediting the data sources, ready for Blender sculpting, CAD site models or MeshLab inspection. The current export is geometry-first — no material file ships with it — so import, assign your own materials, and work. If your destination is a CAD package that chokes on glTF, OBJ is the reliable middleman.

GLB: the engine format

GLB is glTF 2.0 in a single binary file: one mesh, Y-up, metres. Unity, Unreal, Godot, three.js and Blender all import it directly — drop it into a scene and it is correctly sized with no unit conversion. For web work it is the smallest pipeline: export, load, done. A 16-bit heightmap pairs naturally with it when a game needs the terrain as an editable landscape instead of a static mesh.

The slicer maths you will actually use

STL arrives at its chosen print scale, but rescaling is uniform and the proportions survive. The only formula worth keeping:

uniform scale % = (desired long edge in mm ÷ exported long edge in mm) × 100

  exported at 180 mm, want 90 mm  →  50 %
  exported at 180 mm, want 250 mm →  139 %

Because the scale is uniform, the vertical character you set with the Relief slider is preserved exactly — a Matterhorn printed at 40 percent size is still the Matterhorn, just quieter.

One more format worth knowing

If your printer does multicolour, there is a fourth option in the same panel: 3MF export splits the model into separate parts — terrain, buildings and route — so a multicolour print assigns different filaments per part without painting anything by hand. For single-colour prints, ignore it; for a city with red buildings on tan terrain, it is the whole show.

The one-line summary

Printing → STL. Editing in Blender or CAD → OBJ. Dropping into an engine or a web page → GLB. All three come from the same terrain, the same region, the same five minutes — the format is just the last question, not the first.

Try it while it's fresh

The whole tool runs in your browser — pick a region, shape the relief, export. No account, nothing to install.

Open the terrain app
← Elevation Profiles for Hike Planning: Read the Climb Before You Hike ItThe Matterhorn in 3D: a Five-Minute Case Study →
Contact: admin@3dterrain.cloud · Terms of Service · Privacy Policy · Pricing