Making a VRM model for Desktop Mate

What VRM is, and why it matters here

VRM is an open file format for humanoid 3D avatars, built on glTF and designed so that one avatar file works across many applications. Two properties of the format matter for this workflow.

First, VRM standardises the skeleton. Every VRM model exposes the same named humanoid bones, which is what lets an application animate a character it has never seen before. Second, VRM carries licence metadata inside the file: whether commercial use is allowed, whether the character may be modified or redistributed, and who to credit. That data travels with the file wherever it goes.

There are two format generations in circulation, VRM 0.x and VRM 1.0, and they are not interchangeable at the loader level. This is the single most common cause of a model that simply refuses to appear.

Building the model in VRoid Studio

VRoid Studio is the usual starting point. It is free, it runs on Windows and macOS, and it is purpose-built for making VRM avatars without prior 3D modelling experience: you shape a face and body with sliders, draw or import hair and clothing textures, and let the application handle rigging.

1. Install VRoid Studio and start from one of the bundled base models rather than from scratch.
2. Shape the face and body, then build hair. Hair is where most of the polygon budget and most of the physics cost goes — a simpler hairstyle is a lighter model on the desktop.
3. Add clothing and textures. Anything you paint is baked into the exported file.
4. Keep the editable project file. VRoid's editable format is .vroid; .vrm is an export target only. If you lose the .vroid file you cannot get back to a fully editable model, even from your own export.

Exporting as VRM, and the version trap

In VRoid Studio, export with Export VRM from the model view. Current VRoid Studio releases export VRM 1.0.

That matters, because a large amount of older community material assumes VRM 0.x, and loaders have historically handled the two generations differently. The community avatar loader for Desktop Mate targeted VRM 1.0 in its later releases and added VRM 0.0 handling afterwards, so which files load depends on which loader build you have. Practical advice:

• Target VRM 1.0 for anything you make yourself. It is what current tools produce and what current loader builds expect.
• If a downloaded model will not load, check its VRM version before assuming the file is broken. Converting an old 0.x model to 1.0 is the documented fix and there are converters that do it.
• VRM 1.0 expects MToon10 shading. A model whose materials were not set up correctly can import without an error and still render invisible or untextured.

At export, VRoid also asks you to set the licence metadata. Set it deliberately even if you never plan to share the file — it costs nothing now and it is the field other people will read if the model ever leaves your machine.

Getting it into Desktop Mate

Here is the part that has to be said plainly: Desktop Mate has no publisher-supported way to load a custom VRM. The character list in the app is populated by DLC. Everything below relies on community code that infiniteloop does not support and did not sanction.

The best-known route is the Custom Avatar Loader by YusufOzmen01, a MelonLoader mod that adds a file picker for local VRM files. Two facts about it are important before you start:

• The repository was archived on 4 December 2025 and is read-only. It receives no fixes for new Desktop Mate builds.
• Its documentation targets MelonLoader 0.6.6 and .NET Desktop Runtime 6, which is an older stack than the current app.

If you proceed anyway, back up the Desktop Mate folder first, or at minimum know that Steam > Desktop Mate > Properties > Installed Files > Verify integrity is your recovery path. Install one thing at a time and launch between each step, so you know which change broke what. The safe install checklist checklist covers the general procedure, and the Custom Avatar Loader page has the loader's specific requirements and known failure modes.

When the model does not appear

• Nothing happens on the shortcut key. The loader is probably not running. Check MelonLoader's log for a load error rather than re-downloading the model.
• The file is rejected outright. Check the VRM version first. A 0.x file on a build that expects 1.0 is the usual cause.
• The character loads but is invisible or untextured. This is a materials problem, not a loader problem. Re-export with MToon materials rather than a generic shader.
• Hair or clothing behaves strangely. Spring-bone physics did not survive the export. Simplify the hair and re-export.
• It worked yesterday and not today. Desktop Mate updated. Remove the loader, confirm the clean app still starts, and only then decide whether to reinstall.

What you may do with the result

A model you built yourself in VRoid Studio from its bundled assets is yours to use. You set its licence at export and you decide whether anyone else may use it.

That changes the moment you import someone else's work. A downloaded hair preset, a texture pack, a converted model, or a character design that belongs to a company are all governed by their own terms, and packaging them into a VRM does not reset those terms. If you intend to share a model publicly, the safe test is whether you could name a permissive source for every part of it.

Making a VRM model for Desktop Mate FAQ

Sources and verification

• VRoid Studio official site ↗
• VRM format specification and documentation ↗
• Custom Avatar Loader repository (archived 4 December 2025) ↗
• MelonLoader documentation ↗
• Desktop Mate on Steam (App ID 3301060) ↗

Checked against the sources above on 2026-09-01. Desktop Mate, its DLC line-up, and community tooling all change; recheck the originals before acting on anything time-sensitive here.