GLB to FBX.

Maintained by Bake3D · Updated 25 September 2026

What this converter keeps

Most free GLB to FBX converters keep the shape and throw away the rest. This one keeps what you need to animate:

• The skeleton. Every joint becomes an FBX bone, with the same names and the same parent and child order.
• The skin weights. Each point on a skinned mesh still follows the same bones by the same amounts, from the same bind pose.
• Every animation. Each glTF animation becomes its own FBX take, with the same name and length.
• The scene layout. Every node keeps its place, so a prop under a moving hand still moves with it.
• Static meshes and material slots. A mesh with two materials keeps both slots.
• The base color. The color and its texture image are packed inside the FBX, so you only have one file to move around.

How to convert GLB to FBX

1. Drop a GLB file, or a glTF file with embedded data, on the box above. Files up to 64 MiB work.
2. Pick the animation frame rate: 24, 30 or 60 frames per second.
3. Read the report. It lists the meshes, joints and animations it found, and anything the FBX cannot hold.
4. Download the .fbx file.
5. Import it into your app and play each take once to check it.

Your file never leaves your computer. The whole conversion runs in your browser, with no upload and no account.

What changes on the way

Units. FBX files usually measure in centimetres, while glTF uses metres. The converter writes centimetres and says so inside the file. Apps that read the unit, such as Blender, show the model at the same size as the GLB.

Up axis. The FBX keeps glTF’s Y up, the same as Unity, Maya and most FBX files.

Animation keys. Every animation is baked, which means each bone gets a key on every frame. Linear, step and curved (cubic) keys all turn into the same shape of motion. Every joint is keyed in every take, like Blender’s “Key All Bones” option. So switching from one take to another never leaves a bone in the old pose.

Materials. FBX has no single standard for modern materials. The converter keeps the base color and its texture. Normal, roughness, metal, emissive and occlusion maps are not included, so reconnect them in your app if you need them.

Skinned meshes. In glTF, a skinned mesh ignores its own node position. The converter places each skinned mesh at the top of the FBX scene, at the exact spot the skin was bound. The skeleton itself keeps its place in the hierarchy.

Names. Very long names are cut to 60 characters, and repeated names get a number, such as Bone.001, because many apps need unique bone names.

What this converter does not keep

• Morph targets, also called blend shapes or shape keys.
• Cameras and lights.
• Vertex colors and a second UV set.
• Texture offsets and tiling.
• Points and lines. Only triangle meshes are converted.

The report beside the download names anything from your file that was left out, so nothing disappears quietly.

Open the FBX in your app

Blender. Use File, Import, FBX. Each take becomes an action named after the object and the take, such as Armature|Walk. Blender’s importer starts the animation on frame 1 by default. Choose a take in the Action Editor.

Unity. Drag the FBX into your Assets folder. Unity reads FBX on its own. On the Rig tab, choose Generic for creatures and objects, or Humanoid for human characters. The Animation tab lists every take.

Unreal Engine. Import the FBX as a skeletal mesh and turn on importing animations. Each take becomes an animation sequence.

Godot. Godot 4.3 and newer can read FBX, but it recommends glTF. If Godot is your target, keep the GLB.

When to use Blender instead

Use Blender to convert when your file has morph targets you need, advanced materials, cameras or lights, or Draco compression. Import the GLB into Blender, then export FBX. Our guide on how to convert GLB to FBX lists the export settings that matter. To learn more about the source format, read what a GLB file is.

Common questions

Does the FBX keep my animations?

Yes. Every glTF animation becomes its own FBX take with the same name and length. Motion is baked with a key on every frame at the frame rate you pick, and every joint is keyed in every take.

Why does the preview look plain?

The preview shows the FBX that was just written, read back by three.js, without decoding the images. The base color textures are still inside the downloaded file. Open it in Blender or your engine to see them.

Why is my model 100 times too big or too small?

The FBX is in centimetres and declares it. Apps that ignore the file’s unit, or that were set to metres, can show a 100 times jump. In Unity, check Convert Units on the model’s import settings. In other apps, look for a unit or scale option on import.

Is my file uploaded anywhere?

No. The converter runs entirely in your browser. The file is read, converted and saved on your computer, and nothing is sent to Bake3D or anyone else.

Can I convert FBX back to GLB?

Not with this tool. Blender can import FBX and export GLB. For a static FBX with no rig, our FBX to OBJ converter and OBJ to GLB converter work in your browser too.

What do the tests cover?

Automated tests convert a test scene with a rotated and scaled rig, a three-joint skin and a static mesh with two materials. It also has an embedded texture, a morph target, a camera and two animations with step, linear and cubic keys. The tests read the FBX back with three.js and compare every vertex with the original glTF, at rest and on several animation frames. The largest gap allowed is 0.1 mm. They also convert the Bake3D sample fox, with 28 joints and 60,000 triangles, and check that the same input always gives the same bytes. We also imported the output into Blender 4.4. The fox, the sample tentacle and the test scene matched the original shape at rest and in the middle of every take. We have not yet run these files through Unity or Unreal Engine ourselves.