An FBX that shows up grey has almost never lost its textures: it simply no longer knows where to find them. The format does not always store its images inside the file. More often, it keeps a path to them, and that path does not always survive the trip from one machine to another. The good news: once the cause is identified, the repair takes a few clicks with Eyemesh.
This guide is part of our method for organising your 3D game asset library, where stray textures are among the most common problems.
Four causes account for the vast majority of cases.
By default, an FBX does not contain its textures. The documentation for Autodesk's FBX plug-in explains it clearly: on export, the file stores the relative path and the absolute path of each associated media file. The absolute path is the one on the artist's machine, something like C:\Users\artist\Projects\Barrel\textures\Barrel_BaseColor.png. On your machine, that folder does not exist. The relative path works as long as the original folder structure is respected, but all it takes is a renamed or moved textures/ folder for it to lead nowhere.
.fbm folderFBX export also offers to embed media in the file. The textures then travel with it, at the cost of a heavier file. On import, Autodesk's plug-in extracts this media into a <fileName>.fbm folder placed next to the FBX. If you find a Barrel.fbm/ folder in a pack, it is the trace of that extraction: the images it contains are the model's.
This is the simplest cause: the FBX arrived on its own, without its images. You then need to ask the author for them or go back to the pack's original files.
The textures are there, but not under the expected name: Barrel_diffuse.png became T_Barrel_BaseColor.png after export, or the PNGs were converted to TGA.
Before fixing anything, look at what the model's folder contains:
| What you see | Probable cause | Next step |
|---|---|---|
A FileName.fbm/ folder next to the FBX | Embedded media, extracted during an import | The images are in that folder |
A Textures/, Maps/ or Materials/ folder in the pack | Stored paths that no longer match | Reattach the images to their location |
| Images with similar but different names | Textures renamed after export | Manual or suffix-based remapping |
| No images anywhere in the pack | Textures not delivered | Get the source files from the author |
Standardised suffixes such as _BaseColor, _Normal, _Roughness or _AO then make reattaching almost automatic.
If you control the export, the most durable fix is to deliver an FBX that finds its textures on its own.
.blend file with broken links, the File > External Data > Find Missing Files menu recursively searches the folder you point it to and restores the links.On the engine side, Unity applies a search logic you can take advantage of: when importing a model, it first looks for a Textures subfolder next to the mesh, then in the parent folders, before searching the entire project. Storing the images in a Textures/ folder at the model's level, or above it, therefore makes its job easier.
When you do not control the export, which is the case for every pack you buy, everything happens at the moment the file opens. Eyemesh reads FBX files with ufbx, the library that Godot's FBX importer has also used since version 4.3, and runs several searches in a row without you having to do anything.
textures, Textures, tex, maps, Materials, texture), in any subfolder whose name contains ‘texture’, and in neighbouring folders of the same kind. It works its way up the folder tree like this, as far as the folder you opened._BaseColor, _Diffuse, _Albedo, _Normal, _Roughness, _Metallic, _AO, _Emissive, and their short variants such as _nrm or _rough) and matches it against the model's name. If there is only one image of a given type, that one is used.When you open a single FBX on its own from the Finder and it references external textures, Eyemesh lets you know with an ‘External textures detected’ window: a click on ‘Open Folder’ gives it access to the model's folder, and the search starts.
Once the model is displayed, a glance is enough to see where it stands. Next to the file name, a red badge flags a missing texture, an orange badge remapped textures, and a blue badge textures that are all in order.
For the cases automatic matching cannot settle, a click on the badge opens the Texture management window, described in detail on the materials and textures page.
Two special cases are covered. A model that has textures but no base colour referenced gets a Base Color row so you can add one. A model that has UVs but no textures shows ‘Assign textures’: you choose one image per material.
And for a whole pack, there is no need to repeat the operation file by file. In selection mode, the Actions > Remap textures menu applies the same fix to all the selected files, or to the whole folder if nothing is selected.
A fix made once should stay made.
textures/ subfolder of the collection. The model opens there textured, even if the original pack moves.Once the textures are in place, MatCap or untextured mode helps you spot an incomplete PBR set.
Because the images for its materials cannot be found where it expects them. An FBX usually stores a path to its textures rather than the textures themselves. If that path points to the artist's machine or to a renamed folder, the model shows up without its material.
Open it in Eyemesh: embedded textures show up straight away, with no access request and no red badge. A file noticeably heavier than its neighbours is also a good clue.
.fbm folder next to an FBX?The media embedded in the FBX, extracted during an import. Autodesk's FBX plug-in copies it into a folder named after the file followed by .fbm. These are the model's textures: you can point the remapping to that folder.
No. The fix is saved in Eyemesh's cache, never in the FBX. To get a file that contains its textures, export it to GLB or USDZ.
Yes. Switch to selection mode, choose the files, then Actions > Remap textures. The fix applies to the whole selection, or to the whole folder if no file is selected.
Often, yes: Eyemesh recognises each image's type from its suffix and matches it against the model's name. For the rest, each texture's menu in the Texture management window lets you pick the right image in one click.
Open your FBX packs in Eyemesh: embedded textures read straight away, automatic search around the model, remapping per texture or in batches, without ever touching your files. 7-day free trial.