Renderloom Scene to GLB
Export a Renderloom or Form Studio scene as a glTF 2.0 GLB with PBR materials.
How it works
Convert a Renderloom scene, Kerfwise Form Studio project or render recipe into one GLB file: a node per solid grouped by tag with its position and rotation, metallic-roughness materials from colours and finishes, and optionally a Material Nodes PBR texture set (base colour, normal, occlusion-roughness-metallic) on all solids, one tag or one solid. The file is re-read by a strict GLB parser before download.
- The scene root node converts Renderloom millimetres with Z up to glTF metres with Y up (scale 0.001, −90° about X). Below it, one group node per tag holds one node per solid.
- Each solid node carries its translation and its Z rotation and X/Y tilts as one quaternion (Z · Y · X, the Form Studio order), so the mesh is the untransformed extruded footprint.
- Colours are converted from sRGB to linear factors. Finishes map to metallic/roughness: matte 0/0.85, satin 0/0.45, metal 1/0.3.
- Material Nodes textures are evaluated by the same engine as the app and stored as PNG: base colour (sRGB), normal (+Y, OpenGL style) and one ORM image bound as occlusion (R) and metallic-roughness (G, B).
- After writing, the GLB is parsed again (header, chunks, buffer views, accessors, min/max, indices, hierarchy, textures) and its world-space geometry is checked for closed solids.
Solids are exported as separate closed meshes with flat normals; no boolean union, cameras, lights or animation. Textured solids get planar (top/bottom) and perimeter (side) UVs; tangents are left to the viewer (glTF MikkTSpace default).
Sources
- glTF 2.0 specification (Khronos Group) (Khronos Group)
Part of Renderloom
-
Renderloom 3D scene & material studio
Shape a scene. Find its light. Keep every idea editable.
How to export a Renderloom scene as GLB with PBR materials
Turn a Renderloom scene, Kerfwise Form Studio project or render recipe into one glTF 2.0 GLB file with a node hierarchy, metallic-roughness materials and optional PBR textures.
What it is for
Renderloom Scene to GLB writes a scene as one binary glTF 2.0 file. Each solid becomes a node with its own position and rotation, grouped under one node per tag. Colours and finishes become metallic-roughness materials, and you can add a Material Nodes texture set (base colour, normal and occlusion-roughness-metallic) to all solids, one tag or one solid.
The file is read back by a strict GLB parser before you download it, and the report shows what that parser found. Renderloom's GLB export dialog uses the same engine.
Worked example
The first example exports the Studio corner scene without textures. The summary reads "18 solids in 3 tag groups, 328 triangles, 9 materials; 18 of 18 solids are closed." The re-read table lists 22 nodes (scene root, three tag groups and 18 solids), a hierarchy depth of 2 and bounds from −2.4, −0.04, −1.8 to 2.4, 2.2, 1.8 metres. The file is 30,032 bytes.
The second example applies the Oak planks Material Nodes preset at 128 × 128 pixels to every solid of the Courtyard pavilion, repeating every 800 mm. It reports 7 solids, 84 triangles, 1 material and 3 textures; the file grows to 210,060 bytes because the three PNG maps are stored uncompressed.
How to read the result
Nodes counts the root, tag groups and solids. Closed solids says how many solid meshes have no open or non-manifold edges after reading the file back; every Renderloom solid should be closed. Bounds are in metres with Y up, as glTF defines them.
Tips and common mistakes
- Renderloom works in millimetres with Z up; the GLB root node scales by 0.001 and rotates −90° about X. Do not rescale the model again after import.
- Finishes map to fixed values: matte (metallic 0, roughness 0.85), satin (0, 0.45), metal (1, 0.3).
- Textured solids get planar UVs on top and bottom and perimeter UVs on the sides; tangents are left to the viewer, as glTF allows.
- Solids stay separate meshes without boolean union; cameras, lights and render settings are not exported.
- To apply a saved Texture Lab material, use the GLB dialog in the Renderloom app; this tool offers the Material Nodes presets.
FAQ
Why does my scene look tiny or lie on its side in another program?
It should not: the root node already converts millimetres to metres and Z up to Y up. If you rescale or rotate the model again after import, undo that step. Programs that ignore node transforms are rare; Blender, three.js and Godot respect them.
Can I use my own photo-based Texture Lab material?
Yes, in the Renderloom app: the GLB dialog lists your saved Texture Lab materials next to the Material Nodes presets. This tool page only offers the presets, because the Texture Lab source image lives in your browser.
Why are the texture images so large?
The PNG maps are written without compression so the same bytes come out of the app, the tool and the API. A 256-pixel set adds about 800 KB; choose 128 pixels for small files or recompress the images in another program.
Guide last updated:
For scripts and AI agents
- JSON API:
POST https://renderloomsceneglb.usefulweb.app/api/v1/calculate(same calculation as this page) - Interface description: OpenAPI 3.1 · AI guide: llms.txt
- MCP server (Streamable HTTP):
https://renderloomsceneglb.usefulweb.app/mcp· tool namerenderloom_scene_glb
Example request
curl -s -X POST https://renderloomsceneglb.usefulweb.app/api/v1/calculate \
-H 'content-type: application/json' \
-d '{}'