Contact

Email us

Write to [email protected]. That is the whole channel — there is no account, no ticket system, and no support plan.

We read everything that arrives, and we answer in the order it makes sense rather than the order it was sent. If a report turns out to be a bug, it gets fixed and you will hear that it was.

What to include

A short message with four things in it is enough for almost anything:

What you were doing

The action that led to the problem, in a sentence.

What you expected

And what happened instead.

Browser and device

The browser, roughly the device, and whether it is desktop or mobile. This matters more than usual here, because the converter is the browser doing the work.

What the page said

The exact error text, copied, if there was one. Error messages in this tool are deliberately specific, so the wording is the most useful part of the report.

Please do not attach your model. We do not need the file to diagnose a problem, and we would rather not hold a copy of your design — see the privacy policy for why that matters here. If a specific mesh is genuinely the only way to reproduce something, say so and we will tell you what we would need and how to send it.

How long it takes

A bug report with the details above is usually answered within a few days. Feature requests and questions may take longer, and we will tell you if something is not going to happen rather than leaving it hanging.

We do not operate a support desk, so there is no guaranteed response time and no escalation path. If a problem is affecting work you are being paid for, say so in the first line.

Why there is no form

A contact form has to send the message somewhere. That somewhere is a third-party service, and the moment you add it, this site has a company in the middle of a conversation that is otherwise just between you and us — and a privacy policy that has grown a paragraph explaining what that company does with your email address.

The site has no backend at all, so a form here would mean adding one. Amailto: link is the option that keeps theprivacy policy short and true, so that is the one we chose. Your email goes through your own mail provider, exactly as it would if you wrote to anyone else.

Reporting a bug

Security issues are treated differently and take priority. If you find one:

• write to us directly rather than opening a public issue, and say clearly that it is a security report;
• give us enough to reproduce it — the steps, the input, what you observed;
• give us reasonable time to fix it before disclosing it publicly. We would rather hear about it first, and we will not treat a good-faith report as hostile.

The converter handles untrusted STL files, which is a rich source of parsing bugs. If you can make it do something other than print, that is worth telling us about even if it looks harmless.

Privacy requests

Access, deletion, correction and objection requests under the UK GDPR, EU GDPR or the CCPA go to the same address. Most will have an unusual answer, because this site holds almost no personal data: there is no account and no stored model — page visits are measured with Google Analytics. The exception is web server logs held by the hosting provider, and we will forward your request to them and help.

Who to contact instead

We can only speak for this site. If you are trying to:

• report a problem with a downloaded model — tell whoever published it, not us;
• get help with your printer — your printer's manufacturer, or the community around its firmware;
• report a vulnerability in a third-party slicer — go straight to that project's own security process;
• ask about a copyright or trademark claim — we will route it to the right party, but expect it to take longer.

If you are not sure, write anyway. We would rather answer a question that turned out not to be ours than have you go without an answer.