How it is built
The page loads only the code it needs for this task, and that code runs in your tab. Reading, processing and writing happen on your device; no model content is sent anywhere.
How it is tested
The engine is checked against fixed fixtures: text and binary models, a model with quads, a model with inverted normals, files saved by real third-party exporters, and deliberately broken files that must fail loudly instead of producing a half-written result. Triangle counts and bounding boxes are compared after every change.
What it deliberately does not do
- It does not upload files for server-side processing.
- It does not claim output quality it cannot verify.
- It does not carry data the target format cannot store.
A flattened game asset often has open edges. Check it with a mesh report before sending it to a slicer.
Who runs it
This tool is maintained by an editorial team that builds small, single-purpose web utilities. The same team publishes other 3D tools, each with its own page and its own job. The tools are independent products; they are not endorsements of each other.
Write to [email protected] with the file's format and version, the triangle count you expected, and what the output looked like. A small anonymised sample speeds up the fix. Corrections are applied as dated revisions on the page that changed.
Privacy in one paragraph
Files are never uploaded. The page counts visits with an aggregate analytics script and stores no cookies for the tool itself. Full detail is on the privacy page.