A Guide to Preparing Architectural Assets for glTF 2.0 in Blender

Blender’s official documentation on glTF 2.0, Collections and material assignment provides a basic workflow for preparing architectural assets for export. glTF 2.0 is a format used to transfer 3D models to web and native applications; Blender’s add-on supports data such as meshes, materials, textures, cameras, lights and animation. Since the documentation does not specify a particular Blender version, the steps below are based on the features described on its documentation pages.

1. Organize the scene with collections

In architectural scenes, keeping furniture, built-in fixtures, decor, lights and environmental elements in separate groups makes it easier to select objects while working and prepare different outputs. Blender collections group objects logically; they do not create parent-child relationships between them. An object can belong to multiple collections.

1. Sort objects into collections by function. For example, separating furniture from decorative objects in an interior scene makes it easier to hide or export these elements together when needed.

2. To put selected objects in a new collection, use Object › Collection › Create New Collection. You can also add objects to an existing collection or move them to another collection using the options in the Object › Collection menu.

3. To control visibility, decide whether to include the collection in the active View Layer. According to the documentation, when Include is disabled, the collection is excluded from rendering, the 3D Viewport and the Outliner in the active View Layer.

4. If you need to use the same assets in multiple scene setups, consider linking or appending collections between files.

Collection properties can help speed up repeated exports, not just organize the scene. You can add an exporter to the active collection and manage its options in the collection panel. In addition to glTF 2.0, the documentation lists exporters for Alembic, USD, Wavefront OBJ, Stanford PLY and FBX (Legacy). The File › Export All Collections option runs all exporters in the collections.

2. Assign materials to the right faces

If different parts of an object need different materials, use material slots. An object has one material slot by default; you can add more slots to assign different materials to different faces of the same mesh.

1. Select the object and create a base material in the Material Slots panel, or choose an existing one.

2. Switch to Edit Mode and use Face Select to select the faces that will receive a different material.

3. Create a new material or select an existing one in the material slot, then click Assign. You can use Select and Deselect to check which material the faces use.

4. If you’re using the same material on many objects, reuse it rather than creating copies. The documentation notes that in the 3D Viewport, Ctrl-L can link selected objects to the active object’s material.

Whether a material is linked through Data or Object affects the result. With Data, objects sharing mesh data also share the material; an Object link lets you assign different materials to objects that use the same mesh data. This distinction matters in scenes where repeated door, chair or light-fixture geometry needs different surface options.

3. Check glTF material connections

glTF’s core material setup uses a metal/roughness PBR workflow. Blender’s exporter generates materials from node connections it recognizes, so a material appearing correctly in Blender does not by itself guarantee that its setup is suitable for export. Key checks include:

If the metallic and roughness map is a single image, use a Separate RGB node to split the channels, then connect the green channel to Roughness and the blue channel to Metallic. The documentation says this setup matches the glTF standard and lets the exporter copy the image without converting it. If the image is connected differently, the add-on may try to adapt it during export, which can increase export time.

For materials that use textures, glTF requires images to be in PNG or JPEG format. Images in other formats may be converted automatically during export, which can take longer. For normal maps, also set the Image Texture node to Non-Color and leave the Normal Map node at the default Tangent Space; this is the normal map type the documentation describes as supported for glTF.

4. Check geometry and constraints before export

You can add the glTF 2.0 exporter from the Collections panel and manage repeated exports of the same asset. However, review the geometry and material requirements beforehand. Quads and n-gons are triangulated during glTF export. UV discontinuities and flat-shaded edges can increase the number of exported vertices. Curves and other non-mesh data are not preserved, so they must be converted to meshes before export.

You can enable GPU instancing for objects instanced within a collection. According to the documentation, the instances must be meshes, have no child objects of their own, and be children of the same object. This extension does not manage material differences; instances in the output may use the same materials. So check assets that need different surfaces before placing them in a single instancing setup.

Common mistakes

• Connecting the metallic and roughness channels in the wrong order, or forgetting to set the Image Texture to Non-Color.

• Leaving curves and other non-mesh data unconverted, even though they are not exported to glTF.

• Forgetting that quads and n-gons will be triangulated.

• Assuming that different materials will be preserved across instances when using GPU instancing.

• Overlooking the effect on export time of automatic conversion for texture formats other than PNG or JPEG.

For architecture, interior design and archviz teams, this preparation helps ensure more predictable delivery of assets intended for web or real-time visualization. Keeping collections organized makes it easier to manage scene components separately; checking material connections ensures that the exported surface data matches the channels glTF expects. Teams creating shared libraries should add instancing constraints and mesh conversion to their pre-delivery checklist.