Let's talk

Get in touch with the Qrfast.io team about a bug, a feature request, or a question about QR codes. We read and answer every message.

Email is the fastest way

Write to [email protected]. It reaches the person who maintains the site, not a ticket queue, and every message is read.

We aim to reply within one to two business days. Occasionally it is slower — this is an independently run site, not a support department — but nothing is ignored.

What to include so we can actually help

Most questions we receive are about a code that will not scan, and almost all of them are answerable straight away if the message includes a few specifics. Without them, the reply is usually a request for more information, which costs you a day.

If a code will not scan, tell us:

Before writing, it is worth checking the four things that cause most scanning failures. They are covered in more detail in each type's guide:

  1. The quiet zone was cropped. QR codes need four modules of blank margin on every side. Design layouts remove it constantly.
  2. Contrast is too low. Dark on light, with a real difference in brightness — not just in colour. Convert your design to greyscale to check.
  3. The code is too small for the payload. Longer data means a denser grid. A vCard with every field filled in needs more physical space than a short URL.
  4. It was printed on gloss. Specular highlights from overhead lighting wipe out sections of the code. Matte laminate solves it.

If a WiFi code connects to nothing, the cause is almost always a special character in the network name or password — a semicolon, colon, comma, backslash or quotation mark. Tell us which characters appear in yours.

Bug reports

If something on the site is broken, please include the browser and version, the device, and what you were doing when it happened. A screenshot helps. If your browser's console shows an error, that is the single most useful thing you can send.

Feature requests

We do read these, and the content types on the site exist partly because people asked for them. It helps to describe the problem rather than the solution — what you are trying to accomplish and where the current tool falls short — because that often reveals a better fit than the specific feature requested.

Questions we can answer here

"Can I use these codes commercially?" Yes, with no attribution, licence or payment. The codes you generate are yours. The QR specification is an open ISO standard and requires no licence.

"Can you edit a code I already printed?" No — codes generated here are static, so the data lives in the pattern itself. Nothing we do can change a code already in the world. If you need an editable destination, point the code at a short URL on your own domain and change the redirect there.

"Do you store what I encode?" No. Codes are generated in your browser and your input is never transmitted to us. The privacy policy explains this in full.

"Can you tell me how many people scanned my code?" No, and nobody else can either unless the code routes through a redirect they control. Because our codes point directly at your content, there is no intermediate step where a scan could be counted.

Business and press

For partnership enquiries, press questions, or anything commercial, use the same address and put the subject in the first line so it gets to the right place quickly.

What we cannot help with