Strip 3D model metadata
Remove authoring metadata (generator string, copyright, node/mesh names, and any glTF "extras" fields) from a 3D model before sharing it. Converts through assimp's import side to glTF/GLB first, so the input can be any of the 40-odd formats assimp reads, then edits the resulting scene JSON directly. Nothing is uploaded.
Runs on your device. The file is never uploaded.
Strip 3D model metadata deletes the glTF generator and copyright strings and every extras block anywhere in the scene. It renames each node and mesh to node_0 or mesh_0, and reports all three counts. Output is .glb unless you ask for .gltf, suffixed -stripped. Material names, animation names and texture file names are left exactly as they were.
Questions
What exactly does it strip?
Four things. The generator string and the copyright string in the glTF asset block. Every extras object anywhere in the scene graph, found by walking the whole document, since glTF lets any node, mesh, material or animation carry one and modelling software uses them for author names, file paths and project ids. And every node and mesh name, which is replaced with node_0, mesh_0 and so on. The summary tells you how many of each were removed.
Does my model come back in its original format?
No, and this is the thing to know before you use it. The file is imported through assimp and re-exported as glTF or GLB, chosen with the format option, which defaults to glb. So an FBX goes in and a GLB comes out, named with a -stripped suffix. The scene is rebuilt by the engine, so anything assimp does not carry across is gone as a side effect.
What metadata does it leave behind?
Material names, animation names, texture file names and anything embedded inside image data. The renaming pass covers nodes and meshes only, and image metadata is not examined. Run Strip EXIF metadata over any external texture images separately, and check the material list with 3D model mesh info if names there matter to you.
How is this different from Convert 3D model?
It is that conversion plus an editing pass. Convert 3D model imports and exports and hands you the result. This does the same import and export, then edits the resulting scene JSON to delete the identifying fields and rename nodes and meshes, and reports what it changed. If you only want a format change, use the converter.
Can I check what was removed?
The summary line tells you the counts: how many asset fields, how many extras blocks and how many node or mesh names were changed. To see the result itself, run 3D model mesh info on the stripped file and compare the mesh and material names against the original. Both tools run locally, so you can check without sending the model anywhere.
Is the model uploaded to be scrubbed?
No. assimp runs as WebAssembly in a Web Worker in this tab, with its wasm served from this site, and the JSON editing happens in the same worker. That matters for this tool in particular: the whole point is removing identifying information before you share a file, and uploading it first would defeat that.