One API call returns a Rust map as a 3D model. You host the file and show it however you like — this page is doing exactly that, with the real file the API returns.
A single .glb file: the terrain as a 3D mesh at real world scale,
with the map image baked on as its texture. It opens in Blender, Unity, Godot
and Windows 3D Viewer, and loads in any web 3D library.
The ground under each monument is levelled the way the game does it, so buildings you place sit flat instead of half-buried. Monument positions come from a separate call and use the same coordinates, so they drop straight in.
curl -o map.glb -H "Authorization: Bearer $YOUR_KEY" \
"https://rust-mapmaker.com/api/maps/by-seed/4500/100513556/terrain.glb"
Address a map by seed and world size — what is already in your server config — or by its id. There is also a lookup that takes a server's IP and port and returns whatever map it is running right now, so an embed like this one can follow a wipe on its own.
<script type="module" src="model-viewer.min.js"></script>
<model-viewer src="map.glb" camera-controls auto-rotate></model-viewer>
Two lines for a viewer you can drag and zoom. This page uses three.js instead, because it wanted fly controls and its own sky — that version is about fifty lines and is in the docs.
The buildings on this page are not in the file. The
export is terrain only — the mesh plus the map render baked on.
You can still render the monuments: one API
call returns signed URLs for the whole model library, served from us and
loaded straight into a GLTFLoader. Positions come from
the markers endpoint in the same
coordinate space.
Hit the Textured button above to see the difference.
There are two model libraries and they are interchangeable — same keys,
same geometry, same coordinates, so switching is one word in the URL.
monuments-tex carries the game’s own baked textures, so a
monument looks like it does in Rust; monuments is the untextured
set, for when you would rather shade the buildings yourself. This page is
loading whichever one the button is set to, live.
You pull the file once and serve it yourself, so a thousand visitors cost you nothing more, and none of that traffic touches us.
Read the API docsAll of it is live on paid plans: the 3D export, the image and heightmap exports, the server lookup, catalogue search, uploads — and generation itself, both plain and fully custom, so a map can be queued, polled and exported without anyone opening the site. The docs are the accurate picture at any moment.