glTF to FBX.

Maintained by Bake3D · Updated 8 October 2026

A .gltf is more than one file

glTF comes in two forms. A .glb packs everything into one file. A .gltf is a text file that points to other files by name: a .bin with the shape and animation data, and the texture pictures (glTF 2.0 specification). Many downloads come as a .zip with a scene.gltf, a scene.bin and a textures folder.

Most converters ask for one file, so they choke on the .gltf. This one takes all of them at once. Drop the files, the folder or the .zip, and it finds every file the .gltf asks for, then writes one FBX.

How to convert glTF to FBX

1. Drop the .gltf together with its .bin and texture files on the box above. You can also drop the whole folder or the .zip you downloaded. On a computer, Choose a folder picks a folder in one go.
2. Pick the animation frame rate: 24, 30 or 60 frames per second.
3. Read the report. The files read line lists every file the .gltf used. Missing files and unused files are named too.
4. Watch the preview. It is the FBX that was just written, read back by three.js, and it plays each take.
5. Download the .fbx file.

Click Try a sample .gltf with .bin to see it work. The sample is the Bake3D fox as a .gltf, a .bin and a JPEG texture.

How the files are found

The .gltf names each file by a path, like textures/fur.jpg. The tool looks for that exact path in what you added. If a folder was renamed or the capitals differ, it looks again ignoring capitals, then by file name alone.

A missing .bin stops the conversion, because the shape is inside it, and the message names the file you need. A missing picture does not stop it. The FBX is written without that texture, and the report names the picture. Addresses on the web are never fetched: the tool reads only the files you give it.

What the FBX keeps

The FBX is written by the same writer as our GLB to FBX converter, so it keeps the same things:

• The skeleton, with the same joint names and parents.
• The skin weights, from the same bind pose.
• Every animation, as its own take with the same name and length. Each joint gets a key on every frame, at the frame rate you pick.
• The node tree, so a prop held in a hand stays in the hand.
• The base color and its texture, packed inside the FBX.

The FBX is binary FBX 7.4, in centimetres with Y up. glTF uses metres, so the converter writes centimetres and says so inside the file. Apps that read the unit show the model at the same size.

What it does not keep

• Morph targets, also called blend shapes or shape keys.
• Cameras and lights.
• Vertex colors and a second UV set.
• Normal, roughness, metal, emissive and occlusion maps, and texture tiling.
• Points and lines.

Files packed with Draco or meshopt compression cannot be read. Export them again without compression, or open them in Blender and export FBX from there. The report names anything in your file that was left out.

Open the FBX in your app

Unity. Drag the FBX into your Assets folder. On the Rig tab pick Generic for creatures and objects, or Humanoid for people. The Animation tab lists every take.

Unreal Engine. Import the FBX as a skeletal mesh with animations turned on. Each take becomes an animation sequence.

Blender. Use File, Import, FBX. Each take becomes an action.

Not sure the .gltf is complete? Open it in our free glTF viewer first. It shows the model with its bones and lists any missing files. After converting, the FBX viewer plays each take of the FBX.

How we checked it

Automated tests take a test scene with a turned and scaled rig, a skinned tail, two materials, a PNG texture, a camera and two animations. They split it into a .gltf, a .bin and a .png, add an unrelated text file, then convert. The FBX came out byte for byte the same as the one our GLB to FBX tool writes from the original GLB. Other tests check a missing .bin, a missing picture, a .bin shorter than the .gltf says, a web address and a glTF 1.0 file.

We opened the sample fox in Blender 4.4 after conversion. It had all 29 bones, all three takes and its 2048 × 2048 texture. It stood in the same pose as the original fox at rest and at 0, 0.5 and 1 second into each take. That check found a real problem: Blender placed the fox’s skin 72.5 cm off in FBX files from our writer, because the fox’s first joint is not its root joint. We fixed the writer, and the GLB to FBX tool has the fix too. We have not yet tested Blender 5’s new FBX importer, Unity or Unreal Engine with these files.

Common questions

Why does it say a .bin file is missing?

The .gltf keeps its shape in a separate .bin file, and that file was not added. Drop the .gltf together with its .bin, or drop the whole folder or .zip.

Do I need to add the textures?

Only if you want them in the FBX. Without them, the FBX keeps the material colors and the report names each missing picture.

Can I convert a single GLB here?

Yes. A GLB works too. Our GLB to FBX converter does the same for one file, and its guide on how to convert GLB to FBX covers the settings in Blender.

Which frame rate should I pick?

Pick 30 for most games and apps, 24 for film and 60 for fast action. The FBX gets a key on every frame at that rate, so each take plays the same in any app.

Is my file uploaded?

No. The converter runs in your browser. Nothing is sent to Bake3D or anyone else.

Can Bake3D make the animations for me?

Bake3D does not animate models you upload. It makes a new character from a picture, rigs it and animates it, from a walk to a motion you describe in a sentence. See the AI 3D animation generator or play the free demo.