VRM to glTF Converter
FileFlip converts VRM to glTF entirely inside your browser, using Assimp compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert a VRM file to glTF?#
- Drop your VRM file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to glTF and the conversion starts on its own. FileFlip downloads 11.2 MB of WebAssembly the first time and nothing after that, then runs Assimp on your own machine.
- Save the glTF file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting VRM to glTF lose quality?#
Not in the sense of pixels or samples. Converting VRM to glTF rebuilds the file in glTF's own model rather than re-encoding it, so everything glTF can represent comes through exactly and anything it cannot has to be dropped. Expect the geometry to be exact, and anything the target has no place for, such as a rig, to be left behind.
Is it safe to convert VRM files online?#
Yes, because nothing is uploaded. FileFlip converts VRM files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What VRM to glTF actually does to the file#
Converting VRM to glTF runs on Assimp, downloads 11.2 MB of WebAssembly the first time and nothing after that, rebuilds the file in the target's own model.
| Engine | Assimp |
|---|---|
| Conversion path | One step: VRM → glTF |
| Downloaded to your browser | 11.2 MB, once, then cached by your browser |
| Quality | Rebuilt in the target's model |
| You get back | One file, or a ZIP when the source carries separate materials or buffers |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Materials | Sometimes | Survives for some files and not others. |
| Textures | Sometimes | Survives for some files and not others. |
| Skeleton and animation | Sometimes | Survives for some files and not others. |
Worth knowing before you start:
- the result is a single file when the model has no external materials or buffers, and a ZIP when it does
What is a VRM file?#
A VRM file is a glTF 2.0 binary file with a defined VRM extension added on top, first released by Dwango in 2018 for its VirtualCast platform and now maintained by the VRM Consortium, which pins down how a humanoid avatar's bones, blend shapes and licence terms are encoded so the same avatar loads correctly in different applications.
Use VRM when an avatar needs to move between VTubing, streaming and social VR applications with its rig and expressions intact.
Convert VRM to glTF or GLB when the avatar only needs to render as a generic mesh and the humanoid bone mapping and expression presets aren't needed.
What is a glTF file?#
A glTF file is a JSON scene description, developed by the Khronos Group and first released in 2015, that lists a model's meshes, PBR materials, animations and scene hierarchy while its binary geometry and textures sit alongside it in separate buffer and image files.
Use glTF's JSON form when a pipeline needs to inspect or hand-edit the scene structure directly, since it's plain, indexed JSON.
Convert glTF to GLB when the model needs to travel or load as a single file instead of a folder of JSON, buffers and textures.
VRM to glTF questions people ask#
What is a VRM file?
A VRM file is a humanoid avatar model built on glTF 2.0, adding a standardised bone mapping, facial expression presets and an embedded usage licence so the same avatar behaves consistently across VTubing, streaming and virtual-world applications. Dwango released the format in 2018.
What's the difference between VRM and glTF?
VRM is glTF 2.0 with an additional extension layered on top, so every VRM file is technically a valid glTF binary underneath. What VRM adds is the humanoid-specific data glTF doesn't define on its own: a standard bone naming scheme, blend-shape expression presets, spring-bone physics and licence metadata.
What apps can I open a VRM file with?
VRoid Studio and VSeeFace both open VRM files natively, and Blender reads and writes them through the community VRM Add-on. Most VTubing software and social VR platforms accept VRM as an avatar import as well.
What's the difference between glTF and GLB?
glTF is a JSON text file that references its geometry buffers and textures as separate files, while GLB packs that same JSON, the buffers and the textures into a single binary file. Both describe the identical data model; GLB just bundles everything one file needs to travel as one upload.