Where the archive goes
The file you choose is handed to JavaScript in this tab. It is unzipped in memory, converted, and released when the tab closes or reloads. No copy is written to a server, a database or a queue.
What the page can read
The converter reads the model XML, build items and the declared unit. It does not inspect or transmit colour assignments, print settings or part names beyond what is needed to merge the geometry.
What the host sees
The page request exposes the usual metadata to the host: IP address, user agent, URL and time. Access logs may retain it. The 3MF itself is not part of any request.
Analytics
No analytics script is loaded on this build. If one is added later, this page will say what it records before it ships.
Storage
The tool keeps working state in memory only. There is no file cache, no IndexedDB copy and no service-worker stash; a reload discards the mesh.
Your controls
You can close the tab to clear the mesh, use a private window to keep the visit out of shared history, or disable JavaScript to prevent conversion entirely.
What the archive can contain
A 3MF is a zip package, so it may also hold thumbnails, relationship files, texture parts and print tickets. The converter reads the model XML and the build items needed to build the mesh; the other package entries are not extracted, displayed or transmitted. Closing the tab releases the archive and the mesh. The test fixtures on this site are small synthetic files, not customer models.
What leaves the tab
The conversion result stays in this tab until you download it. The browser writes the download to the folder you choose; the host serves the page code and cannot see the file, its name or its contents. Closing the tab before saving discards the result and it must be produced again. Nothing is queued, and there is no recovery copy on the server.
Contact
Questions or a correction: editor@3mftostl.io. Changes are dated at the top.