VRM 0.x or 1.0: which version to use, and how to switch
Use VRM 0.x unless the app you are heading for asks for 1.0. VSeeFace reads only 0.x, and the other common VTubing apps read both. The mesh and the textures are the same in both versions; what changes is how the avatar layer is written. This page lists who reads what, the differences that matter, and how to convert a file from one version to the other.
Written against the VRM 0.x and 1.0 specifications, the support pages of VSeeFace, Warudo and VNyan, and our own version converter, 13 November 2026.
Which apps read which version
The practical rule comes from one app. VSeeFace loads VRM 0.x and refuses 1.0, and it is still what many people start with. Everything else on the list takes both, so a 0.x file opens everywhere and a 1.0 file opens almost everywhere.
VRChat is not on the list on purpose: it does not load .vrm at all. An avatar goes there as an FBX through Unity and VRChat's own SDK.
| App | Reads |
|---|---|
| VSeeFace | VRM 0.x only |
| Warudo | VRM 0.x and 1.0 |
| VNyan | VRM 0.x and 1.0 |
| Unity with UniVRM | Both, through separate VRM0 and VRM1 menus |
| Blender with the VRM add-on | Both; exports either |
What differs between 0.x and 1.0
The extension. A VRM is a glTF binary with an avatar extension. In 0.x that extension is called VRM; in 1.0 it is VRMC_vrm, with separate extensions for spring bones, materials and constraints. An app written for one does not find the other, which is why a wrong-version file is refused outright and not merely shown badly.
The facing direction. A 0.x avatar faces −Z in glTF space and a 1.0 avatar faces +Z. A tool that converts the version without turning the model leaves it standing with its back to the camera.
The expressions. The presets were renamed: A, I, U, E, O became aa, ih, ou, ee, oh; Joy became happy, Sorrow became sad, Fun became relaxed; 1.0 added surprised. The shape keys underneath are the same; only the names an app looks up have changed.
The required bones. 0.x requires seventeen humanoid bones, including chest and neck. 1.0 requires fifteen and makes those two optional. A rig with one spine bone passes as 1.0 and fails as 0.x.
Spring bones and licence. 1.0 stores hair and cloth physics in its own extension and adds capsule colliders. The licence block has more detailed fields in 1.0, for example who may use the avatar and whether changes may be shared.
How to tell which version a file is
The file name does not say, and both versions use the .vrm ending. Three ways to find out, fastest first.
- Drop the file on the VRM viewer. It opens in the browser, nothing is uploaded, and the info panel shows the declared version.
- Drop it on the VRM version converter. The page reads the version and offers the other one.
- By hand: a .vrm is a GLB. Open it in any glTF inspector and look at the extensions list:
VRMmeans 0.x,VRMC_vrmmeans 1.0.
Converting a finished file
You do not need to go back to the program that made the avatar, and you do not need Unity.
- Open the VRM version converter and drop the .vrm. A 1.0 file is offered as 0.x, a 0.x file as 1.0.
- The file is rewritten on our server: the avatar extension, the expression names, the spring bones and colliders and the licence fields are written in the other version's terms, and the model is turned to face the right way. Meshes, bones, weights and textures are not touched.
- Check the result in the 3D preview and read the notes under it. Anything the target version has no field for is listed there, so you know what was left out before you download.
Exporting the right version in the first place
In VRoid Studio, the export dialog has an Export Format choice between VRM0.0 and VRM1.0. New models default to VRM1.0 since July 2025, so pick VRM0.0 for VSeeFace. In Blender, the VRM tab has a Spec Version setting on the armature. In Unity, UniVRM has one menu per version, VRM0 and VRM1, and a model set up for one is exported from that menu.
If the avatar is going to several apps, export 0.x. It is the version every app in the table reads, and converting up to 1.0 later is one step.
Questions
- Can I convert VRM 1.0 to 0.x without Unity?
- Yes. The version converter does it on our server, so there is nothing to install. UniVRM in Unity migrates 0.x up to 1.0 but has no step back down, so for 1.0 to 0.x a converter is the short way.
- Is VRM 1.0 better quality than 0.x?
- No. The mesh, the textures and the skeleton are identical. 1.0 describes expressions, spring bones and the licence in more detail, which only matters to apps that use those details.
- Why does VSeeFace say my file is not a valid VRM?
- Most often it is a VRM 1.0 file. VSeeFace reads 0.x only. Convert the file to 0.x and it loads.
- Does converting lose anything?
- Only what the target version cannot store, and the converter lists it. Going from 1.0 to 0.x that is mostly the newer constraint and look-at settings; geometry and textures are never changed.
- Can one file be both versions?
- No. A .vrm declares one version. Keep two files if you use apps that need different ones.
- Should I convert my old 0.x avatars to 1.0?
- Only when an app asks for it. A 0.x file keeps working in every app that reads VRM today.
Switch the version now
Drop a .vrm and get it back in the other version, with the expressions, spring bones and licence carried over and the model facing the right way. Free, no account, the files are deleted after 3 days.
Open the VRM version converterSwitch a VRM between the two versions when an app refuses one of them. Geometry is untouched; the page lists what did not carry over.