The 3mftostl.io Editor Team.

The record behind the byline

What the byline covers

The team maintains the 3MF reader, the merge step and the binary STL writer that make up the converter. It also builds the fixtures those steps are run against: seven conversion files, including a cube in millimetres and the same cube in inches, two plates that differ only in material assignment, a five-part plate, an open box and a mirrored transform, plus two packages that declare a required extension.

A run goes through the page's own file input in headless Chrome. The download is captured at URL.createObjectURL, so the saved STL is the exact blob the button hands over. A separate parser then reads the triangle count, bounding box, shell count, boundary edges and signed volume. Those readings are what the posts quote; the result panel is only the first check.

The copy is checked the same way. A claim about the container comes from the 3MF Core Specification, a claim about triangle storage comes from the STL layout, and a claim about a slicer comes from that slicer's documentation or its source. If none of those supports a sentence, the sentence is removed rather than softened.

How a page gets its numbers

1. Start from a primary source: a specification section, vendor documentation or source code.
2. Choose or build a fixture that isolates the claim. The fixture is published with the post.
3. Run the conversion in the built page, not in a sketch or a mock-up.
4. Read the result panel, then parse the exported file independently and compare the two.
5. Write the numbers with the run date and the fixture name. State in the method note what was not run.

This is why most posts end with a boundary sentence. When a claim would need a printer, a laser or a calibrated measuring tool, the post says the test was not run. The site has no print lab, and it does not borrow results from one.

What this team cannot show you

• No physical prints. No post on this site claims a printed part, a caliper reading or a light-box test.
• No personal credentials. The byline is organizational on purpose. The identity here is the domain, the email address and the test record, not a biography.
• No third-party benchmark. The converter is not compared against another converter unless a post records that run.
• No universal slicer result. Where a slicer is named, the version is named too. A different version can behave differently.

AI assistance, stated plainly

The posts are drafted with AI assistance. The AI is not the evidence. Every number has to survive against a cited document or a recorded run, and the method note at the end of a post records which of those applies. The illustrations are generated for the post they sit in and are not presented as test evidence. The screenshots are crops of the converter's result panel, and the numbers in their captions match the run that produced them.

Corrections

Send the URL, the sentence and the source that contradicts it to editor@3mftostl.io. A substantive correction is applied to the page and its date line is updated; nothing is silently rewritten. If a source moves or disappears, the link is replaced with an archived copy or the claim is removed. The same address reaches the people who maintain the converter, so a wrong number and a wrong conversion arrive in the same inbox.

Independence

There is no advertising, no affiliate link, no sponsored comparison and no paid placement on this site. The converter is free and the files stay in the browser. Outbound links go to specifications, vendor documentation and standards bodies because those are the sources the posts are checked against, not because anyone paid for them.

Review record

This page is maintained by the same byline. It is reviewed when the converter's defaults, the test fixtures or the editorial rules change. The standards it refers to are on the editorial page; the readings are on the test page.