To export a Blender model with textures, use File > Export > glTF 2.0 and set Format to glTF Binary (.glb). That writes the mesh, materials, and image textures into one file. If the destination needs FBX, use File > Export > FBX, set Path Mode to Copy, and turn on Embed Textures next to it. FBX carries the images, but its material model is much simpler than Blender's, so expect to reconnect some maps after import.
Both exports only work cleanly when the material is built from Image Texture nodes going into a Principled BSDF. Procedural textures and complex node setups do not survive the trip. The rest of this guide covers what to check before exporting, the settings for each format, and why a model can still arrive grey. We checked the steps against the Blender 5.2 LTS manual and the Blender 5.3 Python API. The Blender 5.3 Pipeline & I/O notes list no FBX export changes, so the FBX steps match 5.2 and 5.3.
glTF or FBX: which format keeps textures?
| Option | What you get | Textures | Best for |
|---|---|---|---|
| glTF Binary (.glb) | One file | Packed inside the file | Web viewers, sharing, most real-time tools that read glTF |
| glTF Separate (.gltf) | A .gltf, a .bin, and image files | Written as separate images in a folder you choose | When you want to edit the textures after export |
| FBX, Path Mode Copy + Embed Textures | One .fbx | Embedded in the binary file | Unity, Unreal, and DCC apps that expect FBX |
| FBX, Path Mode Copy, Embed off | An .fbx plus copied images | Copied next to the file and referenced with relative paths | When the target app should import textures as separate assets |
Our default is glTF when the target reads it. Blender's glTF exporter understands the Principled BSDF directly and writes a metallic/roughness PBR material, the same model Blender uses. FBX predates that model, so Blender converts the material on the way out.
Before you export: check the material
Most "exported without textures" problems start in the .blend file, not the exporter. Check these first.
- Every texture must load. If anything shows pink, Blender cannot find the image, and the exporter cannot copy it either. Fix it with our guide to pink textures in Blender.
- Use Image Texture nodes. The glTF exporter "will construct a glTF material based on the nodes it recognizes in the Blender material." It finds base color by looking for a Base Color input on a Principled BSDF and uses an Image Texture node connected to it. Our guide on how to add a texture in Blender shows that basic setup.
- Bake anything procedural. Noise, Voronoi, color ramps, and mix chains are not images, so there is nothing for the exporter to write. Bake them to image textures first. Our guide on how to bake textures in Blender covers each PBR map.
- Keep normal maps in Tangent Space. The glTF manual says the Normal Map node "must remain on its default property of Tangent Space."
- Make sure the model has UVs. Image textures need a UV map. If you have not unwrapped yet, see how to UV unwrap in Blender.
- Check color space. Base color stays sRGB. Roughness, metallic, and normal maps should be Non-Color. Our PBR texture color space guide lists each map.
How to export a Blender model with textures as glTF (.glb)
- Select what you want to export. Or skip this and export the whole scene.
- Open the exporter. Choose File > Export > glTF 2.0 (.glb/.gltf).
- Pick the format. In the Format dropdown, choose glTF Binary (.glb). The manual says this "produces a single .glb file with all mesh data, image textures, and related information." Choose glTF Separate if you want the images as their own files; its Textures field sets the folder, relative to the .gltf file.
- Limit to your selection if needed. In the Include options, restrict the export to selected objects if you only want those.
- Check Materials. Leave the Materials option on Export. The API describes this as "Export all materials used by included objects." Placeholder and No Export leave the textures out.
- Check Images. Automatic keeps PNGs as PNG, JPEGs as JPEG, and WebPs as WebP, and writes other formats as PNG. None exports materials without textures, so make sure it is not set to that.
- Apply modifiers if needed. Apply Modifiers exports the mesh after all modifiers are calculated. Leave +Y Up on unless you know the target needs otherwise; the manual describes it as the glTF convention.
- Export. Then open the .glb in another app, or import it back into a new Blender file, to check that every map arrived.
Which maps does glTF export?
The core glTF 2.0 material has slots for base color, metallic-roughness, normal, occlusion, and emissive textures, per the glTF 2.0 specification. A few details matter for PBR sets:
- Metallic and roughness share one image. glTF stores roughness in the green channel and metallic in the blue channel of the same texture. Our ORM texture guide explains that layout.
- Ambient occlusion needs a custom node group. The Principled BSDF has no AO input. The manual says the exporter looks for a node group named glTF Material Output and reads occlusion from its red channel.
- Emission comes from the Principled BSDF. Connect an Image Texture to its Emission input.
- Height has no slot. Core glTF has no height or displacement map. If your look depends on displacement, bake it into the mesh or a normal map. Our post on normal maps vs height maps covers the difference.
- Tiling can come along. The manual says a UV Map node and Mapping node in front of the texture are exported with the
KHR_texture_transformextension. Not every app reads that extension, so check scale in the target.
How to export a Blender model with textures as FBX
- Select the objects. Turn on Selected Objects in the exporter if you only want these.
- Open the exporter. Choose File > Export > FBX (.fbx).
- Set Path Mode to Copy. The manual says Copy will "copy the file on exporting and reference it with a relative path."
- Turn on Embed Textures. It sits next to Path Mode. The Blender API notes it embeds textures in the binary FBX file "only for 'Copy' path mode." With any other Path Mode, it has no effect.
- Set the transform options. Forward and Up convert the axes for the target app. Blender uses Y forward and Z up. Apply Scaling controls how unit and custom scale are written.
- Apply modifiers. Apply Modifiers exports the evaluated mesh. The API warns that it prevents exporting shape keys.
- Export. Then import the file in the target app and check each map.
If you would rather keep the textures as loose files, leave Embed Textures off. Path Mode Copy still copies the images next to the FBX and points to them with relative paths. Send the folder, not just the .fbx.
Why does my exported model have no textures?
| Symptom | Likely cause | Fix |
|---|---|---|
| FBX arrives grey | Path Mode not set to Copy, or Embed Textures off and the images were not sent | Export again with Copy and Embed Textures, or send the image folder |
| Base color arrives, other maps missing | FBX's simpler material model did not map every Principled input | Reconnect roughness, metallic, and normal in the target app |
| Procedural material arrives blank | No image to export | Bake the material to image textures, then export |
| Textures pink in Blender before export | Missing image files | Relink them with Find Missing Files |
| .glb has materials but no images | Images set to None | Set Images to Automatic |
| Texture scale wrong after import | Mapping node not read, or object scale | Check KHR_texture_transform support, apply scale before export |
| Normal map looks inverted in the engine | OpenGL vs DirectX green channel | See OpenGL vs DirectX normals |
What the FBX exporter does not keep
The Blender manual is direct about this. It says Blender "now only supports complex node-based shading," while FBX has "a fixed pipeline-like support of materials," so the exporter converts between them. In the export compatibility section, Material textures appear in the list of missing features. The manual does not list which Principled inputs survive.
So we treat an FBX material as a starting point. The mesh, UVs, and image files come across reliably. The material wiring often does not. In practice that means opening the material in the engine and connecting each map yourself:
- In Unity, see how to make a material in Unity.
- In Unreal Engine 5, see how to make a material in Unreal Engine 5 and the PBR texture import settings each map needs.
That is also why we keep the separate texture files even when we embed them. Rebuilding a material is quick when the maps are in a folder with clear names.
Exporting twirl materials from Blender
twirl's public library materials download free without an account, as separate albedo, normal, roughness, metallic, and height maps. Because they are ordinary image files, they export like any other Image Texture: albedo to Base Color, roughness and metallic as Non-Color, normal through a Normal Map node. The height map is the one that will not travel through glTF, as covered above. If you need test assets for an export pipeline, the wood and metal categories are a good mix of non-metal and metal maps.
FAQ: exporting Blender models with textures
Does glTF embed textures?
Yes, when you choose glTF Binary (.glb). The single .glb file contains the mesh data and image textures. glTF Separate writes the textures as separate image files instead.
How do I embed textures in an FBX from Blender?
Set Path Mode to Copy, then turn on Embed Textures next to it. Embedding only works in Copy mode.
Why does Blender not export my procedural material?
Exporters write image files. A procedural material has no image to write. Bake it to image textures, connect those to the Principled BSDF, then export.
Should I use FBX or glTF for Unity and Unreal?
Use what your project expects. FBX is the traditional choice for engines. Either way, plan to check the material after import, and with FBX, plan to reconnect some maps.
Can I export Blender materials to another 3D app exactly?
Not with node setups beyond the basics. glTF and FBX each have their own material model, and Blender translates to it. A Principled BSDF with image textures translates best.
How do I send a .blend file with its textures?
That is a different task from exporting. Pack the images into the .blend, or keep relative paths and send the folder. Our pink textures guide covers both.
