Contact
Get in touch
Bug reports and API questions are the most useful things you can send. Feature requests are welcome too.
Before you write
If your code will not scan, the answer is usually one of three things, and checking them takes about a minute: contrast between foreground and background, whether the quiet zone survived your layout, and whether a logo is covering more than about a quarter of the width. Our troubleshooting guide walks through all six causes in the order worth checking.
If a code decodes but the phone does nothing useful, the problem is the payload rather than the code. Scan it with a plain reader that shows raw text and check the string character by character — a missing https:// is the most common culprit.
What we can help with
Every message is read by someone who works on the generator. We usually reply within a few working days.
- A code that will not scan. Tell us the content type, the design settings, the device that failed, and whether it was on screen or in print. That is usually enough for us to reproduce it.
- Something wrong in a guide. Corrections are welcome, and we publish them rather than quietly editing.
- API questions. Include the full request URL or JSON body and the response you got back.
- A feature you need. Particularly a content type or design option we do not support yet.
- Copyright and legal notices. See our Copyright & DMCA policy for what belongs where.
What we genuinely cannot do
We cannot recover a code you have lost, because we never had it. Nothing you create here is stored on our side — it is generated in your browser and discarded when you close the tab. If you still know the content and the design settings, regenerating takes about thirty seconds.
We also cannot tell you where somebody else's QR code leads, change a code that has already been printed, or help with a code made on a different site.
API questions
The endpoint takes the same options as the visual editor and returns SVG. If you are getting a 400 back, the response body names the specific parameter that failed, which is usually faster than asking us. Unknown values for shape options fall back to the default rather than erroring, so a typo produces a plain code rather than a failed request.
What to include
For a scanning problem, tell us the content type, the design settings you used, the device that failed and whether it was on screen or in print. For an API question, include the full request URL or JSON body. That is usually enough for us to reproduce it without a back-and-forth.
Reporting a code that will not scan
Include the content type, the design settings you used and the device that failed. Most reports turn out to be one of six causes — the troubleshooting guide covers them all and may save you the wait.
What we can and cannot help with
We can help with anything about the generator, the API, or the guidance we publish. We cannot recover a code you have lost, because we never had it — nothing you create here is stored on our side. Regenerating it takes about thirty seconds if you still know the content and the design settings.
Corrections are genuinely welcome
If a code behaves differently on your hardware than our published testing predicts, that is the single most useful message you can send us. We test rendered files with one decoder; we cannot test every phone, printer and material combination that exists. Real counter-examples change what we publish.
Privacy
Only what you type into this form is submitted. There is no analytics script and no third-party form processor on this page.