VRM 0.x vs VRM 1.0: Which File Do You Have, and Which Desktop Pet Opens It?

VRM 0.x and VRM 1.0 are two versions of the same 3D avatar format. 0.x uses the MToon shader; 1.0 uses MToon10 and adds capsule colliders, per-joint SpringBone tuning and MatCap masking. The practical problem: not every desktop pet opens both — and most people discover this the annoying way, by exporting a model, dropping it into an app, and watching it fail.

This guide gives you a 30-second way to identify which version your file is, a plain-English summary of what changed, and a dated table of what desktop pets actually support.

Download AniMate Waifu What is a VRM model?

The 30-second check

You don't need any special software. Open your .vrm file in a text editor (VS Code, Notepad++, or TextEdit in plain-text mode) and search (Ctrl/Cmd + F) for VRMC_vrm. Found it → VRM 1.0. Not found, but "VRM" appears in the extensions list → VRM 0.x. The file is a glTF 2.0 container: most of it is binary, but the JSON header names the format extension in plain text.

You can also go by where the file came from:

Source	Likely version
VRoid Studio, dress-up feature export	VRM 1.0 — VRoid's FAQ states "You can only export in VRM version 1.0" for this path
VRoid Studio, classic model editor	Whatever you picked in the export dialog — VRM0.0 or VRM1.0
Booth / VRoid Hub	Check the product page — most list it
A commission	Ask the artist; they have the export settings

What actually changed in 1.0

VRM 1.0 is not a reskin. It is a revised standard that fixes issues in 0.x and adds capabilities:

	VRM 0.x	VRM 1.0
Shader	MToon	MToon10
Base	glTF 2.0	glTF 2.0
SpringBone colliders	Sphere / plane	Adds capsule colliders
SpringBone tuning	Per-chain	Per-joint (SpringBoneJoint)
MatCap masking	—	Supported in MToon10
Status	Legacy, still everywhere	Current standard

The shader change is the one you will notice when something goes wrong: a 1.0 model loaded by an app that only understands MToon can come out with wrong skin tone, flat lighting, or missing material effects.

Which apps open which — verified 2026-08-28

Only rows we could confirm against a primary source are listed, with the check date. Dates matter here — re-verify before you rely on any of this.

App	Platforms	VRM 0.x	VRM 1.0	Source
AniMate Waifu (first-party)	Windows 10/11 · macOS (Apple Silicon)	Yes	Yes	Product facts, 2026-08-28
A popular free, open-source desktop pet	Windows	Yes	No — "coming soon" per its own store page	Store listing, 2026-08-28
VRoid Studio (export side)	Windows / macOS	Optional in the classic editor	Only output of the dress-up export	pixiv VRoid FAQ, 2026-08-28

Apps we could not confirm are deliberately absent — several well-known pets do not state their VRM version support publicly at all. Absence of a statement is not absence of support, but we will not guess. Search "does [app] support VRM 1.0" and you will find blog posts and AI-written roundups repeating each other, sometimes claiming support the app's own page does not. A dated table with sources beats a confident claim.

If you have a VRM 0.x model

You are in the easy position — 0.x is what most desktop pets were built around, and it works in AniMate Waifu.
Consider keeping a 1.0 copy too if your source is VRoid Studio and you might move between apps. Keep both exports.
Do not convert unless you need to. 0.x is not broken; it is just older.

If you have a VRM 1.0 model

It works in AniMate Waifu on both Windows and macOS.
If you are set on an app that only reads 0.x: reopen the .vroid source file and re-export as VRM0.0 from the classic editor. This only works if you kept the source — VRM files cannot be imported back into VRoid Studio.
No source file? Ask the creator for a 0.x export. Third-party converters exist; results vary, and bone and material definitions are where they usually break.

Why imports fail (and it is usually not the app)

One competitor's store page puts it well, and it applies to every VRM host: if a model does not load, it is usually corrupted, exported incorrectly, or missing a proper humanoid bone setup. In practice the order of causes is:

Wrong version for the app — a 1.0 file into a 0.x-only host. Check first; it is free.
Bone setup — custom or renamed bones are the usual culprit.
Shader mismatch — a MToon10 model in a MToon-only renderer loads but looks wrong.
Export settings — polygons, materials or bones trimmed too aggressively, or a truncated export.
Physics — SpringBone settings that do not survive the version the app expects.

Step-by-step fixes: the VRM import guide.

FAQ

Is VRM 1.0 better than 0.x?

It is newer and fixes real problems, but "better" depends on what you are opening it with. If your app only reads 0.x, then 0.x is better for you today.

Can I convert 0.x to 1.0?

Not reliably by renaming or with a one-click tool — the bone and material definitions differ. If you have the VRoid source, re-export. If it is a purchased model, ask the creator.

Which version does VRoid Studio export?

Both, depending on the path. The classic editor's export dialog lets you choose; the dress-up export produces VRM 1.0 only. Verified against pixiv's FAQ on 2026-08-28 — this has changed before, so check again when it matters.

My model loads but the skin looks wrong

Classic MToon/MToon10 mismatch: a 1.0 model rendered by an app built for 0.x. Export the other version and compare.

Does AniMate Waifu treat the two versions differently?

No. It detects the version and loads it — and once the model is in, the same dances, stages and interactions apply either way. You do not have to pick.

Question	Guide
Put your VRoid model on your desktop	VRoid model to desktop: full walkthrough
Live2D or VRM — which file do you have?	Live2D vs VRM
Best VRM desktop companions (2026)	Best VRM desktop companions
Import a VRM model step by step	VRM import guide

Both versions work here

AniMate Waifu opens VRM 0.x and 1.0 on Windows 10/11 and macOS (Apple Silicon) — free tier, one-time unlock for custom models. Export whichever version you like; it will load.

Download AniMate Waifu