VRM Viewer for Windows

Inspect VRM avatar assets

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

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 keeps representable scene data and selected VRM metadata available for diagnosis without presenting itself as a complete avatar runtime.

Common VRM viewing use cases

• Review avatar geometry, node hierarchy, textures, material setup, and retained toon-material intent.
• Inspect skinning, bone structure, UV sets, and supported morph targets after export.
• Check retained humanoid, expression, MToon, and spring metadata while separating metadata presence from runtime execution.
• Diagnose whether a visual difference comes from core model data or unsupported VRM-specific lighting, 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.
• Retained VRM humanoid, expression, MToon, and spring metadata where present.
• Authored MToon materials presented through Tridi's shared Toon shading path rather than the complete MToon lighting model.
• UV0 and UV1, four-influence skinning, supported morph targets, and supported transform, skeletal, and morph animation channels.

Use the inspection views

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

If the avatar differs from a dedicated VRM runtime, compare the same file in a conforming VRM application when source-specific runtime behavior is part of the acceptance criteria.

VRM support boundaries

Tridi does not implement the complete source-specific MToon lighting model. Shade and shift behavior, GI equalization, matcap, rim lighting, MToon UV animation, transparent Z-write, render-queue execution, VRM expression execution, and spring physics remain outside the current runtime behavior.

Humanoid, expression, MToon, and spring data can be retained as metadata without implying that every associated runtime rule is executed. 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