3D tools

13 tools

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.

Convert & inspect7

1→1Convert 3D modelTurn an OBJ, STL, PLY, GLB, glTF, FBX, DAE, 3MF, 3DS or 40-odd other 3D formats into GLB, glTF, OBJ, STL, PLY or USDZ. Textures round-trip through glTF/GLB; OBJ, STL, PLY and USDZ output geometry only.1→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.1→1Inspect a glTF/GLB modelRun the Khronos glTF-validator over a glTF or GLB file and report every error, warning, info and hint it finds, alongside a resource summary (draw calls, vertex/triangle counts, materials, textures, animations). A model in another format is converted to GLB first, so the report describes that conversion's output rather than the original file's own bytes.1→1Measure a 3D modelRead the bounding box, volume, surface area and triangle count out of a 3D model, per mesh and as a whole. Volume assumes consistent outward-facing triangle winding.1→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.1→1Optimize a 3D modelShrink a 3D model: weld coincident vertices within a tolerance, simplify the mesh toward a target triangle fraction, and quantize vertex positions onto a coarser grid. No Draco compression, since three ships Draco's decoder but not its encoder, and the encoder three's own exporter points at is a CDN this project never fetches anything from.1→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.

Print prep1

1→1Check a 3D model for 3D printingCheck whether a 3D model is watertight (every triangle edge shared by exactly two triangles, counted by position rather than by vertex index, since STL is a triangle soup with no shared indices at all) and report its volume, surface area, bounding box in millimetres and inches, and smallest observed edge as a rough minimum-feature estimate.

Create3

·→1Text to 3DTurn typed text into an extruded 3D model, glyph outlines from opentype.js flattened to Bezier shapes and extruded to a chosen depth. Font is one of four bundled Liberation Sans faces.1→1Image to lithophaneTurn a photo into a lithophane: a solid panel whose thickness at every point comes from that pixel's brightness, thin where the photo is bright and thick where it is dark, so a light behind it reveals the image.1→1Extrude an SVG to 3DExtrude an SVG's filled shapes into a solid 3D model. Reads rects, circles and paths through three's own SVGLoader; text elements are not converted to outlines and are skipped, the same limitation the loader itself has. Runs in Node, the CLI and MCP as well as the browser.

1→1View a point cloudLoad a PLY or XYZ point cloud and report its point count, bounding box and whether it carries per-point colour, for the viewer on this page to orbit around.1→13D model turntable GIFRender a 3D model spinning through a full turn and save it as an animated GIF: N frames rendered offscreen with WebGL, encoded with the same GIF89a codec video-to-gif uses (median-cut palette, no dithering). Browser only, since WebGL needs a real GPU context Node has none of.

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.