anytools

all tools

3D tools 4

Convert 3D models between the formats assimp reads, inspect mesh statistics, and strip authoring metadata before sharing a file. Everything runs through assimp compiled to WebAssembly on your own machine.

1→1Convert 3D modelTurn an OBJ, STL, PLY, FBX, DAE, 3DS or 40-odd other 3D formats into glTF or GLB.Takes one file1→13D model mesh infoRead vertex/face/material counts and the bounding box out of an OBJ, STL, FBX, DAE or 40-odd other 3D formats, via assimp's import side, the wide side of the engine model-convert also uses.Takes one file1→1Strip 3D model metadataRemove 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.Takes one file1→1Convert STL between ASCII and binaryConvert an STL 3D model between its ASCII (text) and binary encodings. Both describe the same triangle mesh, so this is a direct parse-and-rewrite with no 3D engine involved.Takes one file

Questions

Which model formats are supported?

Whatever assimp reads, which is around forty formats including OBJ, STL, FBX, DAE, PLY and glTF. Conversion runs through assimp compiled to WebAssembly, in the page.

Is my model uploaded?

No. Everything happens on your device, which matters for work under NDA or for a scan of something you would rather not put on a server.

What does stripping metadata remove?

The generator string, copyright field, node and mesh names, and any glTF extras. Geometry is kept, and the GLB is rebuilt with its binary chunk intact so the mesh survives.

Can I check a model before printing it?

Mesh info reports vertex and face counts and the bounding box, which is enough to catch a model at the wrong scale or one that arrived empty.