Contact
One address, and a real person reads it.
Especially useful to hear about
- A code that doesn’t scan. The most valuable bug report this site can get. Tell us the type, roughly what you entered (never send a real password), which phone and app failed, and the printed size if it was printed. Payload correctness is the one thing that has to be right.
- Something on the site that isn’t true. There are factual claims across these pages about QR behavior, sizes and standards. If one is wrong, we would rather fix it than keep publishing it.
- A QR type worth adding. Particularly if you have a concrete use for it.
- Accessibility problems. If something is unusable with a keyboard, a screen reader or at high zoom, that is a bug and will be treated as one.
Things we can’t help with
- Recovering or editing a code you already made. We have no record of it. Codes are built in your browser and never sent here, so there is no account, no history and nothing to look up — which is the same property that stops anyone else seeing your codes. Make a new one.
- A code from another service that stopped working. That is usually a dynamic code whose redirect was switched off, and only the provider that issued it can restore it. What that means and why.
- Telling you where a code you received leads. You can check that yourself with the scanner, which decodes on your device and shows the destination without visiting it.
Before you write about a code that won’t scan
Most reports come down to size, quiet zone or contrast, and the size guide covers all three with a calculator. If you have been through that and it still fails, that is genuinely worth an email — send the details above and we will look at it.
Response times
This is a small free tool, not a company with a support desk. Replies are usually within a few days. Bug reports that affect whether codes scan jump the queue.