Blender FBX export with textures: which settings keep them (tested in Godot 4.7)
We exported two textured cubes from Blender 4.2 LTS and 5.2 LTS with each FBX path setting, moved the files to a clean Godot 4.7 project as if on another computer, and checked which textures arrived.
Short answer. With Blender's default FBX settings the textures are not inside the file: the
FBX only points to where the images were on your disk, so on any other computer (or engine project) the materials come in
without textures. Set Path Mode: Copy and click the Embed Textures button next to it: in our test
that was the only setting that brought both textures across. Copy without embedding writes a .fbm folder
next to the FBX, but it left out the image that was packed inside the .blend.
What we measured
Two cubes, each with an Image Texture node in Base Color: one image saved as a PNG file next to the .blend, and one image packed inside the .blend (loaded from a PNG, packed with Pack, and then the PNG deleted, so the only copy of that image lives inside the .blend). We exported with each setting below from Blender 5.2.4 LTS and 4.2.23 LTS and read every FBX (its Video and Texture records: path and embedded bytes). Then we hid the original folder, copied each export folder alone into an empty Godot 4.7.2 project, imported it and checked whether each mesh's material had its color texture. Both Blender versions gave the same results. Scripts: exportar_texturas.py, medir_texturas.gd, medir_texturas.sh.
| FBX export setting | Image saved as a file: in the FBX | Image packed in the .blend: in the FBX | Written next to the FBX | Godot on another computer: file image | Godot: packed image |
|---|---|---|---|---|---|
| Defaults (Path Mode: Auto, Embed Textures off) | not embedded; absolute path to the original | not embedded; absolute path to the original | nothing | no texture | no texture |
| Path Mode: Relative | not embedded; relative path to the original | not embedded; relative path to the original | nothing | no texture | no texture |
| Path Mode: Copy | not embedded; path into modelo.fbm/ | not embedded; path into modelo.fbm/ | modelo.fbm/ folder with tex_archivo.png | texture found | no texture |
| Path Mode: Copy + Embed Textures on | embedded in the FBX | embedded in the FBX | nothing | texture found | texture found |
"Auto" wrote absolute paths here because the images were not inside the export folder (Auto only writes a relative path for images in the export folder or below it); either kind of path fails as soon as the FBX travels without the images. The Embed Textures button only works together with Path Mode: Copy.
Why the packed image is the one that gets lost
An image packed into the .blend has no file on disk. With Copy alone, Blender copied the PNG that exists on disk into
modelo.fbm/ but did not write the packed one there, and the FBX still pointed to it, so Godot reported the image as
missing. Embedding writes the image bytes into the FBX itself, so it does not matter where they came from.
Settings we use when the FBX leaves Blender
- Path Mode: Copy and Embed Textures on (the small button to the right of Path Mode).
- Check the file size: our embedded FBX was 3392 bytes larger than the default export, which held no image data at all.
- Procedural textures (Noise, Voronoi…) are not images and are never exported; bake them first. Our GLB measurement shows the same for glTF.
Checking exports automatically
We make ExportProof, a Blender add-on that exports every selected mesh to its own GLB, FBX or OBJ file and
re-imports each one to check triangles, size, and that UV maps and materials were not lost entirely. Its Unity and Unreal
presets already export FBX with Path Mode: Copy and Embed Textures on, and since version 1.2.0 an FBX fails verification with
textures not embedded when one of its images would not travel with the file (the same cases as the table above).
ExportProof on Gumroad · USD 7
More measured guides: FBX scale and rotation for Unity · Blender to Godot · GLB modifiers and materials.