VRM version converter — 1.0 ↔ 0.x, in the browser
VTubeMe VRM Version Converter — convert VRM 1.0 to VRM 0.x (and 0.x to 1.0) online, in the browser. VRoid Studio 2.x writes VRM 1.0, VSeeFace and 3tene read VRM 0.x only, and Desktop Mate wants 1.0 — so drop the file and its own version decides the direction. Humanoid bones (including the thumb chain the two versions name differently), expressions, look-at, spring bones with their colliders and MToon materials carry over, geometry is untouched, and anything a version genuinely cannot express is listed on the result instead of dropped silently. You only pay for successful conversions.
Why the two VRM versions don't mix
VRM 1.0 is not a newer flavour of the same file — it renames the humanoid bones, restructures expressions and look-at, and moves spring bones into a different extension, so an app that reads one version simply does not see the other. That split runs straight through the VTubing ecosystem: the most popular exporter writes 1.0 while some of the most popular apps read 0.x. The usual fixes are Unity with UniVRM, which only goes 0.x → 1.0, or a Windows desktop tool. Here it is a pure metadata and extension rewrite of a file you already have — no GPU, no install, no Blender add-on, and the mesh comes out byte-for-byte the model you put in.
Which app reads which version, what changes inside the file, and what is lost in each direction is laid out in full on our VRM 0.x vs VRM 1.0 compatibility matrix.
Frequently asked questions
How do I convert VRM 1.0 to VRM 0.x online?
The VTubeMe VRM Version Converter does it in the browser: drop the .vrm above and it reads the file's own version and rewrites it to the other one, so there is no wrong direction to pick. A 1.0 file comes back as 0.x for VSeeFace, 3tene and the older VRM apps, and the result previews in 3D before you download it.
My VRoid Studio export won't open in VSeeFace — is it the VRM version?
Almost always, yes. VRoid Studio 2.x writes VRM 1.0 and VSeeFace reads VRM 0.x only, so the file is fine and the version is the mismatch. Run it through the VTubeMe VRM Version Converter and load the 0.x result — humanoid bones, expressions, look-at, spring bones with their colliders and MToon materials come across, and the geometry is untouched.
Desktop Mate needs VRM 1.0 but my model is 0.x — can I upgrade it?
Yes — VTubeMe converts in both directions. Desktop Mate's Custom Avatar Loader wants VRM 1.0 while most models in circulation are 0.x, so drop the 0.x file and it comes back as 1.0. The same rewrite applies: bones (including the thumb chain the two versions name differently), expressions, look-at and spring bones carry over.
What is lost when converting between VRM 1.0 and 0.x?
Geometry, materials and rig are not touched — this is a metadata and extension rewrite, not a re-export. What can genuinely differ is what one version has no room for: 1.0's license fields have no 0.x equivalent, and an expression or constraint 0.x cannot express has nowhere to go. VTubeMe lists anything like that on the result screen instead of dropping it silently, so you see the tradeoff before you download.
How much does it cost?
Your first conversion is free. After that, credit packs: 3 for $7.99 or 8 for $14.99, shared with the FBX converter and optimizer. A credit is only spent on a successful conversion — failures refund automatically, and if the 3D preview shows a broken result you can refund self-serve before downloading.
I have an FBX or GLB, not a VRM
This tool only changes the version of a file that is already a VRM. To make a VRM out of a rigged FBX, GLB or glTF, use the converter next door — same pipeline, same credits. Drop a plain GLB here by mistake and we say so straight away, offer to convert it as a model instead, and spend no credit on it. Open the FBX to VRM converter →