Issue Description
When exporting a scene to FBX in KeyShot, users may notice that no separate folder with textures is created. Only the FBX file itself is generated, which can lead to confusion for workflows expecting individual texture files alongside the FBX.
Environment
-
KeyShot (any version)
-
Window/MacOS
Cause
This behavior is by design:
-
Textures are embedded in the FBX file itself, so no separate folder is created during export.
-
Only textures directly connected to the Diffuse input are included. Textures routed through Utility nodes may not be exported.
-
UV mapping may differ if a UV Map was not used in the scene.
This ensures that the FBX file contains all necessary data to render the model in other applications but does not produce external texture files by default.
Resolution / Workarounds
1. Use “Localize Scene Contents”
If you need the textures as separate files:
-
Go to File → Localize Scene Contents.
-
Choose a local folder to save the textures and scene assets.
-
Export the FBX afterward.
This ensures that all textures used in the scene are available as separate files for external workflows.
2. Verify Diffuse Connections
Only textures directly connected to the Diffuse input will be included.
If your material uses Utility nodes or procedural setups, ensure any textures you need for export are connected to Diffuse, or use the Localize Scene feature.
Additional Notes:
If the issue persists, please contact KeyShot Support with screenshots, system information, and the license type currently activated on each device.