Get in touch
Bug reports, corrections to a guide, or a question about how a payload is built — all of it goes to the same inbox.
We usually reply within two business days.
What to include
A useful report is short and specific. For a scanning problem, tell us the phone model and app you scanned with, the printed size of the code in millimetres, and whether it was on screen or on paper. For a rendering bug, name the browser and the settings you used — version, error-correction level, colours, output size.
If a guide sentence looks wrong, quote it and say what you expected instead. Corrections with a source are welcome; they are the fastest way to improve the site.
What we cannot do
- We cannot decode an image of a code for you. Any phone camera does that faster than we can.
- We cannot recover a code that was generated elsewhere, or tell you where a printed code points without you scanning it.
- We do not offer custom design work, logo placement or bulk code production.
Privacy of messages
Do not send WiFi passwords or other credentials in an email. If a bug only appears with a specific payload, describe its structure — length, character set, escaping — instead of the real secret. The privacy policy explains what happens to messages once they arrive.