VRM Viewer for Windows

Inspect VRM avatar assets

Tridi Viewer opens .vrm files locally on Windows. Review the avatar's core geometry, hierarchy, materials, textures, skinning, morph targets, and available animation data.

VRM builds an avatar-focused specification on top of glTF 2.0 and adds conventions and extensions for humanoid setup, expressions, toon materials, spring bones, and other runtime behavior. Tridi Viewer uses the representable core glTF scene, which is useful for asset diagnosis but intentionally narrower than full VRM execution.

Common VRM viewing use cases

• Review avatar geometry, node hierarchy, textures, and core PBR material data.
• Inspect skinning, bone structure, UV sets, and supported morph targets after export.
• Check how much of an avatar remains usable in a generic glTF-based rendering path.
• Separate missing core model data from VRM-specific shading, physics, or expression behavior.

Supported VRM data

• glTF 2.0 triangle geometry, nodes, and hierarchy.
• Core PBR materials with supported PNG, JPEG, or WebP textures.
• UV0 and UV1, four-influence skinning, and supported morph targets.
• Supported transform, skeletal, and morph animation channels.

Use the inspection views for core data

The Objects panel exposes the imported glTF node hierarchy, while Materials, Textures, UV View, Solid Wireframe, and render passes help diagnose geometry and surface data. Animation controls can play supported core channels when present. These views do not evaluate avatar permissions, humanoid conformance, look-at behavior, or application-specific runtime rules.

If the avatar appears without its intended toon look or secondary motion, that can reflect unsupported VRM extensions rather than missing mesh data. Compare the same file in a conforming VRM application when extension behavior is part of the acceptance criteria.

VRM support boundaries

VRM MToon shading, spring physics, and expression execution are not implemented. Humanoid mapping, first-person settings, look-at behavior, constraints, and VRM-specific metadata are not presented as complete runtime features. Unsupported extensions fall back to usable core glTF data when the file provides it.

Draco- or Meshopt-compressed geometry and KTX2/Basis textures require a supported fallback. For a broader explanation of core resource and extension handling, see the GLB and glTF viewer guide.

Format reference: the VRM Consortium publishes the versioned VRM specifications and their glTF extension definitions.

Related viewer guides