Contact Gridfinity Generator

Reporting a wrong dimension

If a printed part does not match what the gridfinity generator promised, that is the most important kind of report we can receive. Include five things: the page you used, your exact parameter values, the measured size of the printed part (with calipers, in mm), your printer and slicer with the XY compensation settings, and a photo if the fit is too tight or too loose. With those we can tell whether the geometry, your printer's tolerance, or our documentation was at fault.

What happens after you report it

1. 1

   We reproduce it

   Reports are turned into assertions in our 58-check automated test matrix wherever possible, so a fixed bug can never silently return.

2. 2

   We fix the engine or the copy

   Geometry faults are fixed once in the shared engine — never patched per page — and wording faults are corrected across all 6 languages.

3. 3

   The page carries a new date

   Every corrected page gets a new visible updated date and a matching dateModified in its structured data, so readers can see the site is alive.

Requesting a new gridfinity generator feature

Feature requests are welcome and cheap to evaluate because the whole site shares one geometry engine: a compartment insert, a label ledge or a screw-down baseplate variant reuses the same profiles as the existing 13 tools. Tell us the tool you start from, the parameter you wish existed, and the real-world problem behind it — requests anchored in a concrete drawer or toolbox get built first.

Support email — coming, deliberately late

We are preparing a dedicated support email address for the gridfinity generator and will publish it on this page once the inbox process is ready. Until then, this page plus each tool's FAQ are the official channels. We would rather open a channel we can actually staff than display an address that swallows mail — an empty inbox harms trust more than a late one.

Before you write: the Gridfinity Generator checklist

Most questions reach us already answered by one of the 13 tool pages, so a two-minute check saves everyone a round trip. Re-read the FAQ on the gridfinity generator page you used, confirm your measurements against the dimensions table on that page, and skim the sources cited at its foot. If the question survives that check, it is genuinely ours to answer — and we want it.

• Dimension dispute: page URL, parameter values, caliper measurement, printer model, slicer XY compensation.
• Broken download: browser, operating system, and whether the file arrived truncated or not at all.
• Feature request: the tool you start from, the missing parameter, and the drawer or toolbox it serves.
• Content correction: the exact sentence, the page language, and the source that contradicts it.

Reports that follow this checklist let the gridfinity generator team reproduce an issue in minutes instead of guessing across email threads — and reproducible reports are the ones that become permanent assertions in the test suite, permanently improving every language version of the site.

What the Gridfinity Generator does with your report

Nothing disappears into a void. Every report received about the gridfinity generator is logged publicly in our changelog summaries: fixed dimensions, new presets, and translation corrections each get a line with a date. The Gridfinity Generator is a small project with an unambiguous scope — 13 browser tools for one storage standard — and that narrowness is what makes every report traceable to a visible outcome.

If you told ten people about a gridfinity generator bug and only one told us, the gridfinity generator would fix it for all ten. That asymmetry is why this contact page invests a thousand words in explaining how to write a report the Gridfinity Generator can act on.

Privacy in one paragraph

There is nothing to protect because nothing is collected: the gridfinity generator keeps every parameter, preview and download in your browser, sets no marketing cookies, and stores no files on any server. Questions about privacy therefore have refreshingly short answers.

Team availability: the Gridfinity Generator Team reviews reports in weekly batches. Since launch on October 19, 2026, the median first response has been under 7 days.