How to convert FBX to VRM, and what the rig must have
To convert an FBX to VRM you need a humanoid skeleton in the file and one of three tools: an online converter, Unity with UniVRM, or Blender with the VRM add-on. The format is the easy part. What decides whether the avatar works is the rig, the version you write and the shape keys the face has. This page covers all three routes and the checks that come before them.
Written against the VRM 0.x and 1.0 specifications, UniVRM on Unity 2022.3, the VRM format extension 4.x on Blender 4.2 to 4.5, and our own converter, 12 November 2026.
What a VRM needs that an FBX does not have
A VRM is a glTF binary with an avatar layer on top: a map from its own humanoid bone slots to the bones in the file, a set of named expressions, optional spring bones for hair and cloth, and a metadata block with the author and the licence. An FBX carries a skeleton and shape keys but says nothing about which bone is the left upper arm or which shape key is a blink. Converting means filling in that layer.
The humanoid map is the part that fails. VRM 0.x requires seventeen bones: hips, spine, chest, neck, head, and on each side the upper arm, lower arm, hand, upper leg, lower leg and foot. VRM 1.0 requires fifteen of them and makes chest and neck optional. A rig with a single spine bone between hips and head passes in 1.0 and is refused in 0.x, which is the most common reason one tool accepts a model that another rejects.
| Part of the VRM | Where it comes from in the FBX |
|---|---|
| Humanoid bone map | The skeleton, matched by bone name or assigned by hand |
| Expressions | Shape keys (blend shapes) on the face mesh |
| Materials | The FBX materials, rewritten as MToon or PBR |
| Spring bones | Nothing: set up after the conversion |
Check the rig first
Open the FBX in any viewer that lists bones; the FBX viewer does it in the browser. You are looking for three things. There must be a skeleton at all: a sculpt or a scan exported as FBX is only a mesh. The skeleton must be a biped with the bones in the table above. And the mesh must be skinned to it, so that moving a bone moves the body.
A mesh without a skeleton needs rigging before any converter can help. Mixamo's auto-rigger takes a humanoid mesh in a T-pose and returns a rigged FBX, free with an Adobe account. In Blender, Rigify builds a rig you fit by hand. A quadruped, a prop or a creature with extra limbs has no place in the humanoid map and cannot become a VRM.
Route 1: the converter
The shortest route, and the one to try first, because a refusal tells you exactly what the rig is missing.
- Open the FBX to VRM converter and drop the .fbx. If the textures are separate files, zip the model with its texture folder and drop the zip. Up to 100 MB.
- The file is opened in Blender on our server, the bones are mapped onto the VRM humanoid, the materials are rewritten and the shape keys become expressions. Most files take under a minute.
- Look at the result in the 3D preview, pull the expression sliders, then download the .vrm. If a required bone was not found, the page names it instead of writing a broken file.
Route 2: Unity with UniVRM
The reference route. It takes longer and gives you every setting the format has.
- Create a 3D project in Unity 2022.3 LTS and import the UniVRM package from the releases page at github.com/vrm-c/UniVRM. A VRM0 and a VRM1 menu appear.
- Drag the FBX and its textures into the Assets folder. Select the model, open the Rig tab in the Inspector, set Animation Type to Humanoid and press Apply. Open Configure and check that every solid circle on the body diagram is green.
- Put the model in the scene at the origin, select it and choose the export entry in the VRM0 menu. UniVRM exports from a T-pose; the dialog's Force T Pose option makes one if the model stands differently. Fill in the title, the author and the licence fields; the exporter refuses a file without them.
- UniVRM writes a first .vrm. Drag that file back into the project: the prefab it creates carries the components you edit next, the blend shape clips for the expressions and the spring bones for hair and skirts.
- Assign your shape keys to the clips (A, I, U, E, O, Blink, Joy, Angry, Sorrow, Fun), add spring bones where you want movement, and export again from the same menu. That second file is the one you use.
Route 3: Blender with the VRM add-on
For people who model in Blender and do not want Unity on the machine. The VRM in Blender guide covers the installation and the panel in detail.
- Install the VRM format extension (Edit → Preferences → Get Extensions, search VRM). File → Import → FBX, pick the file.
- Select the armature and open the VRM tab in the sidebar (press N). In the Humanoid section press Automatic Bone Assignment, then fill any slot it left empty. Required slots are marked.
- In the same tab, set Spec Version to the VRM version you want, bind your shape keys to the expressions and fill in the metadata: title, author, licence.
- File → Export → VRM (.vrm). The exporter stops with a list if a required bone has no slot or the model is not in a pose it can use.
Which version to write: 0.x or 1.0
Write the version the target app reads. VSeeFace reads VRM 0.x and nothing else. Warudo and VNyan read both. A file in the wrong version is not broken, it is simply refused, and the VRM version converter switches a finished file between the two without touching the mesh.
The versions differ in more than a number. A 0.x avatar faces −Z and a 1.0 avatar faces +Z. The expression names changed (A became aa, Joy became happy, Sorrow became sad, Fun became relaxed), and 1.0 added surprised. Spring bones moved to a new extension with capsule colliders. If you have no reason to prefer 1.0, 0.x is still the version that loads everywhere.
Why the face does not move
Face tracking drives expressions, and expressions are built from shape keys. An FBX whose head has no shape keys converts to a VRM that tracks the body and the head rotation but never blinks or opens its mouth. No converter can invent them; they have to be sculpted in Blender or come with the model.
When the shape keys exist, the names decide how much work is left. Shapes named in the ARKit style (eyeBlinkLeft, jawOpen) or the VRoid style (Fcl_MTH_A, Fcl_EYE_Close) are wired to the standard expressions by our converter. Anything else arrives as an expression under its own name, and you bind it to blink and the five vowels in Unity or Blender.
Questions
- Can I convert FBX to VRM without Unity?
- Yes. The online converter and Blender with the VRM add-on both write a VRM without Unity. Unity with UniVRM is still the route with the most settings, which matters when you want to tune spring bones by hand.
- Why does the converter say a bone is missing?
- Because the humanoid map has a required slot with no bone in it. In VRM 0.x that is often chest or neck on a rig with a short spine. Add the bone in Blender and weight nothing to it, or write VRM 1.0, where those two are optional.
- Does the model have to be in a T-pose?
- For UniVRM, yes: it exports from a T-pose and can force one. The Blender add-on can build a T-pose for a VRM 0.x export. Whatever the route, a T-pose rest pose is the safe choice, because that is what VRM apps assume.
- Will my animations come along?
- No. A VRM is an avatar, not a clip; animation in the FBX is dropped and the rig arrives in its rest pose. A motion goes into a separate .vrma file, which the FBX to VRMA converter writes.
Try the short route first
Drop the FBX, or a zip of the model with its textures. The bones are mapped, the shape keys become expressions and the result is shown in 3D before you download it. Free, no account, the files are deleted after 3 days.
Open the FBX to VRM converterA rigged FBX, GLB, glTF, Blender file or archive becomes a VRM: bones mapped to the humanoid, materials and textures carried over.