About IsItPrintable
Last updated: October 30, 2026
IsItPrintable is a browser-local toolbox for the work that happens before a 3D print: checking geometry, converting formats, repairing broken meshes, and estimating whether a model is ready for the printer.
What this site is for
The site collects focused tools for STL, OBJ, PLY, 3MF, GLB, glTF, STEP, IGES, and BREP files, plus a G-code analyzer. You can inspect a model, convert between formats, clean topology, fill holes, unify normals, check build-volume fit, overhang, wall thickness, and filament use, and generate a printability report.
Each tool is generated from the same local geometry kernel and runs in the browser. There is no account, no project workspace, and no server-side conversion queue.
Local processing, not uploads
Files are read with File.slice() and parsed in a dedicated Web Worker. Mesh operations, WASM modules, and downloads stay on your device. Nothing is uploaded to a server, and the Network panel should show no request carrying your model.
The viewer may keep a preview, full mesh, or independently indexed chunks in the browser's origin-private file system (OPFS). Those caches are local to the browser and can be removed by clearing site data.
Built for real print workflows
The toolset covers common preparation questions: does the model fit the bed, are there open edges or non-manifold junctions, where are the steep overhangs, how thick are the walls, and how much material and time should the print need?
Results are estimates from local geometry. They are a starting point for inspection, not a replacement for a slicer preview or a physical test print.
No account required
There is no sign-up, no profile, and no file library. The site is a static collection of pages and client-side tools, so you can open a tool and work without identifying yourself.
How the site is delivered
Pages are prerendered and served as static files. The CAD importer, boolean operations, and remeshing kernels run as locally served WebAssembly. When a tool needs more work, it uses a Web Worker rather than a server request.