VRM in Blender: import, what breaks, and the fixes

Blender does not read .vrm on its own. With the free VRM format extension it does, and most of what then looks wrong is not damage but a difference between what a VRM app shows and what Blender shows by default. This page walks through the import, the five things people report as broken, and the way back out to VRM or FBX.

Written against Blender 4.2 to 4.5 with the VRM format extension 4.x, on VRM 0.x and 1.0 files from VRoid Studio and our own converter, 10 November 2026.

Install the extension

The add-on is listed on the Blender Extensions platform as VRM format, by saturday06, MIT licensed, for Blender 4.2 and later. Older Blenders install the same add-on from a zip.

  1. Blender 4.2+: Edit → Preferences → Get Extensions, search VRM, click Install. Offline: download the zip from vrm-addon-for-blender.info and use Install from Disk.
  2. Blender 2.93 to 4.1: Edit → Preferences → Add-ons → Install, pick the zip, then enable Import-Export: VRM format (set the filter to Community if it is hidden).
  3. A VRM tab appears in the 3D viewport sidebar (press N), and File → Import and File → Export gain a VRM (.vrm) entry.

Import and what you see

File → Import → VRM (.vrm). You get one armature with the humanoid bones, the meshes parented to it with their skin weights, the textures packed into the .blend, and each material set up as an MToon node group when the file used MToon, or as a Principled BSDF for PBR materials. The VRM expressions (blink, the vowels, joy, angry and the rest) are bindings: to shape keys on the meshes, and in VRM 1.0 files also to material colours and texture offsets. The shape keys arrive on the meshes; the bindings sit in the VRM tab, and an expression that binds a material shows up there, not as a shape key.

Spring bones (hair, skirts, tails) are imported as data on the armature, but Blender does not simulate them the way a VRM app does: the hair hangs still while you pose. That is not a broken file. The extension's documentation describes spring bones in Unity's terms and offers no preview of their motion; export keeps the spring data, and the next app swings it again.

Five things that look broken

The ones that come up.

  1. The avatar looks dark or washed out. MToon is a toon shader; Blender's default Filmic or AgX view transform grades it like a photograph. Render Properties → Color Management → View Transform: Standard, as the extension's MToon page recommends. Outlines show only in Blender 3.3 and 3.5 or later.
  2. Pink or grey surfaces. Pink means a missing texture image: the file referenced one it did not contain, or the .blend was saved without packing. Grey on every surface usually means Solid shading; switch the viewport to Material Preview.
  3. It faces the wrong way, or the arms go the wrong way when posed. VRM 0.x avatars face −Z in glTF space, VRM 1.0 avatars face +Z, and the file does not say so; the version does. Blender's importer handles the rotation, but a script or a retargeting tool that reads bone axes must branch on the version, or one of the two will raise an arm where it should lower it. Nothing to fix in the mesh.
  4. It stands in an A-pose and the tool wants a T-pose, or the other way round. The rest pose is whatever the author exported. Posing the armature is harmless. Changing the rest pose (applying a pose as the new rest) has to carry every shape key along, so do it before you edit expressions, and test each expression afterwards. The extension can also export VRM 0.x from a T-pose it builds for you.
  5. Bone names are not the ones my rig expects. VRM stores a map from its humanoid slots (hips, spine, leftUpperArm …) to whatever the bones are called; the names in the file may be VRoid's, Mixamo's or Japanese. The VRM tab shows the map, and the extension can assign the humanoid slots automatically for the common naming schemes. Rename nothing by hand until you have looked there.

Export back to VRM

File → Export → VRM (.vrm). The exporter checks the humanoid map first and refuses to write a file where a required bone (hips, spine, head, the limbs) has no slot; fill the map in the VRM tab, and set the metadata there too: title, author, licence, what the avatar may be used for. A VRM without a licence is a VRM nobody can legally use.

Choose the version to write for the app you target. VSeeFace reads VRM 0.x only; other apps state on their own pages which version they take. If you end up with the wrong one, the VRM version converter switches a finished file between the two and lists what did not carry over.

What you wantExport
VSeeFaceVRM 0.x
VRoid Hub, UniVRM 1.x projects, three.js appsVRM 1.0 or 0.x; the app's page says which
Unity or Unreal game projectFBX, via the VRM to FBX converter
A file to share, with its licence readableVRM; verify in the viewer

When Blender is the detour

Often the real goal is not Blender at all. For a game engine, the VRM to FBX converter writes a binary FBX with the rig, blend shapes and textures as separate images, which Unity and Unreal import directly; Blender's FBX exporter, for comparison, maps only Principled BSDF materials with image nodes, so MToon node groups come out without their textures. For the other direction, a finished .blend goes to VRM with the Blender to VRM converter without installing anything.

Questions

Which Blender versions work?
The Extensions platform lists the add-on for Blender 4.2 up to the current release; the project's own site has zips for 2.93 to 4.1. Blender 2.8x is not supported.
Can I edit the shape keys and keep the expressions?
Yes. The expressions reference shape keys by name, so edit the shapes freely; rename or delete one and the VRM tab will show the expression pointing at nothing.
Why does the hair not move when I play an animation?
Spring bones are data for the runtime, not a Blender simulation. The exported file still has them; the VRM app moves them.
Can I export FBX from Blender instead of VRM?
You can, but MToon materials are node groups the FBX exporter does not map, so the FBX comes out without their textures. Export the VRM and use the VRM to FBX converter, or rebuild the materials as Principled BSDF with image nodes first.
Does the extension change my file's licence?
No. The metadata you import is the metadata you export, and our VRM converters keep the licence a file already declares; an FBX has no field for it. Check the licence in the VRM tab or in the viewer before you redistribute a modified avatar.

Need the FBX, not the Blender project?

Drop the .vrm and get a binary FBX with the rig, the blend shapes and the textures, ready for Unity or Unreal. Free, no account, the files are deleted after 3 days.

Open the VRM to FBX converter

A VRM as a binary FBX with its rig, blend shapes and textures, for Unity, Unreal or Blender.

Related tools