Contact

What is genuinely useful to report

A code that does not scan

The most valuable report of all, and the one where detail matters most. Please include:

• Which tool you used and what you typed (with anything private replaced by a placeholder).
• The device and operating system version that failed.
• Which scanner — the built-in camera, or a named app.
• Whether it was on screen or printed, and at what size.
• Whether a different device succeeded on the same code.

That last point is the one people leave out and the one that separates a format bug from a print-size problem.

A format that decodes wrongly

If a Wi-Fi code fails to join, a vCard imports with fields in the wrong places, or an event lands on the wrong date, tell us the exact input and the exact wrong output. These are escaping bugs and they are fixable.

A threshold you think is wrong

The print-size thresholds and the logo budget are published on their pages precisely so people who print for a living can argue with them. If your press holds finer detail than we allow for, or your thermal printer needs more room than we say, we would like to know — with the substrate and the device, ideally.

Things we cannot help with

• Codes made on other sites. If a code from another generator has stopped working, it is almost certainly a dynamic code whose redirect has lapsed. This article explains what happened, but only the company that issued it can restore it.
• Recovering data from a damaged printed code. We have no record of anything generated here.
• Bulk generation as a service. Local CSV batch generation is on the roadmap; we do not run it for people.

Feature requests

Welcome, with one standing exception: dynamic codes with scan tracking. That would require a redirect server, which is the exact dependency this site exists to avoid. Everything else — new payload types, better export options, batch generation from a local file — is fair game.