Last updated:
What to contact me about
Email printnexus@hotmail.com for anything related to PrintNexus. Tool bugs, correction requests, editorial feedback, feature ideas, privacy questions, blog suggestions, 3D printing workflows, OpenSCAD tools, slicer questions, MakerWorld ideas, and general feedback are all welcome.
If something on the site is confusing, broken, outdated, or could be more useful, I want to hear about it.
Tool bugs
For tool bugs, include the URL where the issue happened, what you expected to happen, and what actually happened. Screenshots are helpful when the issue is visual or hard to describe.
If the bug involves a file tool, include the file type and any slicer, browser, or device context that helps explain the issue. You do not need to send the actual file unless it is necessary and safe for you to share.
Corrections and editorial feedback
If something is wrong, I want to fix it. Send the page URL, the specific line, claim, formula, or recommendation that needs review, and what you believe should be changed.
Editorial feedback is also welcome if a guide is unclear, missing an important edge case, or could explain a 3D printing workflow in a more useful way. For more detail on how content is reviewed and updated, read the editorial policy.
Feature requests
Feature requests are always welcome. Send ideas for new calculators, file tools, OpenSCAD tools, slicer workflows, MakerWorld tools, blog topics, reference pages, or improvements to existing tools.
The most useful suggestions explain the workflow, the problem you are trying to solve, and what result would save you time.
Privacy when sharing files
Please do not send private, client-owned, unreleased, or sensitive model files unless it is absolutely necessary and you are comfortable sharing them. A screenshot, file type, error message, or simplified sample file is often enough to understand the issue.
PrintNexus does not store uploads, and I do not collect or look at your files. When a tool can run safely in your browser, that is the preferred approach.
Response expectations
I read every message and try to respond as quickly as possible, usually within 24 hours. Some fixes or feature requests may take longer if they require testing, design changes, or updates to the underlying tool.