Contact

For support, feedback, or corrections, email us and include a few details so we can help quickly.

We read every message. If the issue is about a specific calculator, include your inputs, the result you expected, and your browser/device when possible, plus a screenshot if you can.

Before you email

• Check units first (feet vs inches, sq ft vs m²). Most issues are unit mix-ups.
• If you used a default waste factor, try adjusting it to match your layout complexity.
• For bag/box materials, confirm the yield/coverage on your specific product label.
• If something looks wrong, include a shareable link so we can reproduce it.
• If you have them, include photos or links for packaging and coverage details.

We don’t provide professional engineering, legal, or contractor services.

For urgent or safety-critical work, consult a qualified local professional.

For general planning questions, we can point you to the most relevant calculator or guide.

To help us respond faster

• The page link and what you expected vs. what you got.
• Your measurements and units (and any assumptions like thickness or waste).
• The material type (and product label or listing link if you have one).
• Your region if local codes, packaging, or supplier conversions differ.
• Optional: screenshots and your device/browser.

Common topics

• Calculator questions (units, rounding, waste, and assumptions).
• Bug reports (broken inputs, wrong links, or layout issues).
• Content corrections (coverage rates, packaging conventions, or missing steps).
• General feedback on what would make the site more useful.

What happens after you email us

We review your report and classify it as a bug, assumption mismatch, or clarification request.

If details are missing, we reply with a short follow-up checklist.

When confirmed, we update the page and prioritize higher-impact fixes first.

How we prioritize reports

• Highest priority: safety, code-compliance, or major material over/under-order risk.
• Medium priority: defaults, assumption mismatches, and unclear explanations.
• Lower priority: copy polish and non-blocking UI improvements.