The right interchange format depends on the engine that receives it: Unity recommends FBX, Godot recommends glTF, and Unreal Engine accepts FBX, glTF and USD in its import pipeline. This guide goes over what the official documentation of all three engines says, then shows how to keep a single original in your library and produce the right format on demand.
The question comes up with every pack you buy: the vendor delivers an FBX, your project runs on Godot, and a colleague is prototyping in Unreal. Should you convert everything? Keep three copies? The answer is simpler than it seems, and it fits in one table.
These three formats were not created for the same purpose, which explains the engines' preferences.
.gltf (text, with its files alongside) and .glb (binary, a single file)..usd, .usda, .usdc and, in its packaged form, .usdz.The table below only includes what the engines' documentation states in black and white. A tick means that support is explicit and built into the engine.
| FBX | glTF / GLB | USD | |
|---|---|---|---|
| Unity | Yes ‘best practice’ according to the manual | Official glTFast package | USD Importer package, in pre-release |
| Unreal Engine | Yes static meshes, skeletons, animations, morph targets | Yes .gltf and .glb | USD Importer plugin, to be enabled |
| Godot 4 | Yes via the ufbx library | Yes recommended | Not in the list of formats |
A pattern emerges: FBX works everywhere, glTF is Godot's native format, and USD remains mostly an Unreal affair.
Unity's manual lists four standard formats it reads directly: .fbx, .dae, .dxf and .obj. It is very clear about its preference: it recommends using .fbx whenever possible. Native files from applications such as Blender or Maya are converted to FBX on import, and the manual advises against using them in production, recommending that you export an FBX instead.
For other formats, Unity relies on official packages:
com.unity.cloud.gltfast) imports and exports glTF files, both at runtime and in the editor. Its documentation states support for the full glTF 2.0 specification and for the URP, HDRP and Built-In render pipelines.com.unity.importer.usd) reads .usd, .usda, .usdc and .usdz files. Its documentation presents it as a pre-release package.In practice: for Unity, keep the FBX delivered by the vendor. It is the most direct route.
Unreal is the most versatile of the three.
.gltf and .glb files ‘in the same way as other content types’, through the Content Browser or File > Import Into Level, via the Interchange framework's import window..usd, .usda, .usdc and .usdz files can then be opened in the USD Stage panel, or imported as native assets (meshes, skeletons, materials, textures) with Import Into Level.In practice: FBX remains the safe choice for an animated character. glTF works very well for environments and props, and USD becomes interesting if your pipeline already relies on that format.
Godot 4's documentation is the most clear-cut. In its list of available 3D formats, glTF 2.0 is the only one marked ‘recommended’, as .gltf or .glb. It adds that .glb is the most compact option, and that .gltf is useful for versioning a scene description as text or for keeping textures separate from the material.
The other formats listed:
.blend, which Godot has Blender export to glTF in the background, provided Blender 3.0 or later is installed.In practice: for Godot, a GLB is the ideal format. An FBX also imports directly, with no prior conversion.
The temptation is to store every asset three times, once per engine. That is exactly what makes a library bloat and muddles versions. The rule from the guide to organising game assets applies here: keep the original, convert on demand.
| Situation | Recommended format |
|---|---|
| Rigged, animated character for Unity or Unreal | The pack's source FBX |
| Static environment piece or prop for Godot | GLB |
| Asset to version as text in Git | glTF (.gltf + .bin + textures) |
| Prop for the web or a lightweight prototype | GLB |
| AR demo or presentation on Apple devices | USDZ |
| Part for 3D printing | 3MF or STL |
Before converting anything, check two things on the original: that its textures display (if not, see finding an FBX's missing textures), and, for a character, that the skeleton and clips are really there (see checking an FBX's animations and skeleton).
Eyemesh reads 17 input formats, including FBX, GLB, glTF, OBJ, USD, USDZ, DAE and Unity packages, and converts each of them to GLB, glTF, USDZ, OBJ, STL or 3MF, right on your Mac.
Each output format stores textures in its own way:
.gltf, its .bin geometry and a textures folder alongside. Handy for a Git repository..mtl file and a textures folder, so the maps stay linked.Materials exported to GLB and glTF follow the format's PBR model, with base colour, metallic, roughness, normal, occlusion and emission slots. And if you reattached textures by hand in Eyemesh, those fixes are applied to the exported file: the GLB comes out textured, even if the original FBX pointed to a path that could not be found.
For a single asset, open it and choose the format. For a whole pack, select several files and choose a target format: Eyemesh queues them and processes them one after another, showing the status of each task. Eyemesh always asks where to save, the converted file keeps the source's name, and your originals are never modified. Once the batch is finished, a click on Show in Finder takes you to the results.
Detailed step-by-step guides exist for the most common cases: converting an FBX to GLB, an FBX to USDZ, or a Unity package to GLB to reuse an asset bought on the Unity Asset Store in Godot, as far as its licence allows (see tracking your asset licences).
glTF 2.0, the only format that Godot's official documentation marks as ‘recommended’. .glb is the most compact variant, .gltf the most practical for versioning. Godot also imports FBX via the ufbx library.
Unity's manual lists FBX, DAE, DXF and OBJ as standard formats. For glTF, Unity offers the official glTFast package, which you add through the Package Manager.
Yes, once the USD Importer plugin is enabled. .usd, .usda, .usdc and .usdz files open in the USD Stage panel, or can be imported as native assets with Import Into Level.
No. Keep the original FBX in the library: all three engines import it. Convert when a project needs it, for example a batch of environment pieces as GLB for Godot.
GLB if you want a single file with its textures embedded. glTF if you prefer separate, readable files you can version: Eyemesh then writes the .gltf, the .bin and a textures folder.
Yes. GLB and USDZ embed them in the file, glTF and OBJ write them to a folder alongside. Textures you reattached by hand in Eyemesh are taken into account in the export.
Keep your originals, and produce the GLB, glTF or USDZ your engine needs in a few clicks, for one file or a whole folder. 7-day free trial.