Back to blog

Missing Textures in an FBX: How to Find Them on Mac

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.

In this guide

  1. Why an FBX shows up without textures
  2. Diagnose the problem in two minutes
  3. Fix it at the source, in the export software
  4. What Eyemesh does automatically when a file opens
  5. Remap textures one by one
  6. Make the fix last
  7. Frequently asked questions

Why an FBX shows up without textures

Four causes account for the vast majority of cases.

The FBX keeps paths, not images

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.

Embedded media and the .fbm folder

FBX 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.

The textures were never delivered

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 name no longer matches

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.

Diagnose the problem in two minutes

Before fixing anything, look at what the model's folder contains:

What you seeProbable causeNext step
A FileName.fbm/ folder next to the FBXEmbedded media, extracted during an importThe images are in that folder
A Textures/, Maps/ or Materials/ folder in the packStored paths that no longer matchReattach the images to their location
Images with similar but different namesTextures renamed after exportManual or suffix-based remapping
No images anywhere in the packTextures not deliveredGet the source files from the author

Standardised suffixes such as _BaseColor, _Normal, _Roughness or _AO then make reattaching almost automatic.

Fix it at the source, in the export software

If you control the export, the most durable fix is to deliver an FBX that finds its textures on its own.

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.

What Eyemesh does automatically when a file opens

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.

  1. Embedded textures first. If the image is stored in the FBX, it is read directly from the file. A self-contained FBX shows up textured, no questions asked.
  2. A name-based search around the model. Eyemesh does not rely on the folder stored in the FBX: it looks for each texture's name in the model's folder, in the usual subfolders (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.
  3. The original path as a last resort. If the image is still at the stored absolute location and is accessible, it is used.
  4. Suffix-based matching. If the exact name still cannot be found, Eyemesh recognises each image's type from its suffix (_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.

Remap textures one by one

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.

  1. Choose the textures folder with ‘Select a folder’. Eyemesh immediately searches it for each missing image. If they are all found, the fix is applied straight away.
  2. Reattach the rest by hand. The ‘Missing textures’ list shows each texture by the name the FBX expects. For each one, a menu offers every image in the folder. Because each reference in the FBX is tied to a specific channel of its material (base colour, normal, roughness, metallic, occlusion, emission or opacity), the image you pick takes the exact place of the one that was missing.
  3. Set aside what you do not need. The ‘Don't use’ option disables a dead reference, an old specular map you no longer need, for example.
  4. Replace what has already been found, too. The ‘Remap textures’ section lets you point a resolved texture to another image, to test a colour variant, for example.

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.

Make the fix last

A fix made once should stay made.

Once the textures are in place, MatCap or untextured mode helps you spot an incomplete PBR set.

Missing textures in an FBX: frequently asked questions

Why does my FBX show up grey?

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.

How can I tell whether the textures are embedded in the FBX?

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.

What is in the .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.

Does remapping modify my FBX file?

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.

Can I fix an entire pack at once?

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.

My textures were renamed. Can Eyemesh still find them?

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.

Find your textures in a few clicks

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.

Download on the Mac App Store · See all features

All articles