Contact STL Mesh
A small independent project. Email is the right channel for bugs, corrections, and questions the pages do not already answer.
Write to support@stlmesh.com. That address reaches Casey Marlin, who builds and maintains the site.
What to include in a bug report
The more specific the report, the faster I can reproduce it. Please include:
- The file format and a rough size — for example "binary STL, about 12 MB" or "GLB from an AI generator, a few hundred thousand triangles." Do not send the file itself.
- Your browser and operating system: Chrome on macOS, Firefox on Windows, Safari on iPhone, and so on. A version number helps if you have it.
- What happened, versus what you expected. "The preview stayed blank after I dropped a 3MF" is useful. "It doesn't work" is not.
If the page showed an error message, quote it. If the conversion finished but the result was wrong — empty STL, flipped normals, missing meshes — say which conversion you used (GLB to STL, 3MF to STL, and so on) and what the source contained: one mesh or many, with or without colors.
Do not email confidential models
This site never sees your files. They are parsed in your browser and never uploaded. Email is not the same environment. Do not attach client work, unreleased products, or anything confidential. Describe the file instead: format, approximate size, triangle count if you have it, and what went wrong. That is enough to investigate, and it keeps the model where it belongs.
If you need to illustrate a bug, a screenshot of the stats bar or of an empty preview is fine. A screenshot is not the model.
When to expect a reply
This is a small independent project, not a company with a support desk. I read every message and reply within a few days. If you have not heard back after a week, send it again — mail gets buried. Feature requests are welcome; I will tell you honestly if they are in scope. Requests to add STEP, FBX, or CAD formats are out of scope, as is anything that would require uploading a file to a server.
For who runs the site and how the tools work, see About.