What is a VRM?
VRM is a portable, rights-aware avatar file format for 3D characters.
It packages the model, rig, facial expressions, physics, thumbnails, and license metadata into a single file so your identity travels with you across VRM-compatible apps—including MEs.
Why VRM matters (for creators, brands, and fans)
Bring-your-own identity
One file, many places. VRM is built on glTF, making it broadly interoperable across engines and the web.
Expressive by design
Preset facial expressions (blendshapes/visemes), look-at/gaze, and first-person settings deliver believable performance out of the box.
Rights & safety inside the file
Creator, copyright, and usage permissions live in the VRM’s metadata. Marketplaces (like MEs) can read and display this so buyers understand exactly how they may use an avatar.
Evolving and standardizing
VRM 1.0 is officially released, and the VRM Consortium is collaborating with Khronos to push international standardization—good news for long-term compatibility.
One file, many places. VRM is built on glTF, making it broadly interoperable across engines and the web.
Expressive by design
Preset facial expressions (blendshapes/visemes), look-at/gaze, and first-person settings deliver believable performance out of the box.
Rights & safety inside the file
Creator, copyright, and usage permissions live in the VRM’s metadata. Marketplaces (like MEs) can read and display this so buyers understand exactly how they may use an avatar.
Evolving and standardizing
VRM 1.0 is officially released, and the VRM Consortium is collaborating with Khronos to push international standardization—good news for long-term compatibility.
What’s inside a VRM file
・Geometry & materials: mesh, textures, shaders/material settings
・Humanoid rig: standardized bone names for easy motion retargeting
・Expressions: blendshape presets (smile, blink, visemes for lip-sync)
・Physics: spring bones for hair, accessories, and cloth-like motion
・Gaze & first-person: look-at settings; configure head masking for FPV
・Thumbnail & metadata: author, version, license & allowed uses
・Humanoid rig: standardized bone names for easy motion retargeting
・Expressions: blendshape presets (smile, blink, visemes for lip-sync)
・Physics: spring bones for hair, accessories, and cloth-like motion
・Gaze & first-person: look-at settings; configure head masking for FPV
・Thumbnail & metadata: author, version, license & allowed uses
(Actual support for individual features varies by app.)
Using VRMs in MEs
This is some text inside of a div block.
Licensing & responsible use
Every avatar on the Marketplace lists a license summary, and the original license is embedded in the VRM file itself. Before buying or deploying, check:
・Commercial use allowed?
・Redistribution or modification terms?
・Sensitive-use restrictions (e.g., political/violent/sexual contexts)?
・Attribution required?
・Redistribution or modification terms?
・Sensitive-use restrictions (e.g., political/violent/sexual contexts)?
・Attribution required?
Respecting creator licenses is core to MEs. If a listing’s summary and the file’s embedded license seem to differ, the license embedded in the VRM governs; contact support info@o-me.io.
FAQ
Can I use a VRM in other platforms?
Many apps support VRM directly or via import tools. Some (like VRChat) require import via Unity/UniVRM; others (like certain VTuber tools) may need VRM 0.x. Check each app’s docs.
How is VRM different from FBX/GLB?
FBX/GLB are generic 3D formats. VRM is purpose-built for humanoid avatars and includes avatar-specific features and license metadata.
What about performance on lower-end devices?
Good optimization matters more than file extension. Use sensible polycounts, atlased textures, and clean rigs.
