![Uploading fbx/glb files with embedded texture data is not recommended]({"bg": "//theme.zdassets.com/theme_assets/11838850/4c35b2598e2ddcc195bbf2ad2b14cb82d978f423.svg"})
![Uploading fbx/glb files with embedded texture data is not recommended]({"bg": "//theme.zdassets.com/theme_assets/11838850/7539c0fd1e38086be710c91e34815e3f92d81f64.png"})
Embedded texture data refers to a capability of certain file formats to bundle geometry data and one or more texture files into a single file. Examples of file formats that support this capability are FBX and GLB (gltf).
In general, we do not recommend using capability when uploading fbx or glb files to Nira, particularly if you plan to upload updated or corrected versions of assets. Instead, it's best to exclude the texture data from the fbx or glb file and upload the texture data as separate png or jpg files.
Why?
Embedded texture data interferes with accelerating uploads, which is described here. Basically, when using embedded texture data, you will be continuously re-uploading texture data even if you only wish to update some geometric data of an asset. Generally speaking, bundling textures and geometry into a single file is not an efficient way to store files within an asset system like Nira that supports updates/tweaks to particular textures/geometry files over time.
Embedded texture data support:
| File Format | Embedded Textures Supported? |
| FBX | Y |
| GLB |
N |