Creating a QR code is genuinely quick. The part worth slowing down for is not the generating — it is the two choices made just before, because those are the ones that decide whether the code you print stays useful.

Step 1: decide what the code should do

A QR code is a way of writing a short piece of text in squares. What the phone does after reading it depends entirely on what that text is. The common ones:

If you are pointing at a web page, use a link code. Almost everything else people want — a menu, a form, a video, an app download, a review page — is a link with a specific destination.

Step 2: decide whether it should be static or dynamic

This is the decision that matters most, and the one most people make by accident.

A static code has the destination written into the pattern itself. It works forever, with no service involved — and it can never be changed. Getting the URL wrong, or moving the page later, means reprinting everything.

A dynamic code has a short redirect address in the pattern, and the real destination lives on a server. You can change where it points at any time, and every copy already printed follows within seconds. You also get scan counts, because the redirect is a moment the request passes through somewhere countable.

The rule of thumb: anything going to a printer should be dynamic. Anything you are sticking on one laptop lid can be static. Static vs dynamic QR codes works through the trade-off properly.

The one that catches people: a Wi-Fi QR code is inherently static. The phone needs the actual credentials to join a network, not a link to go and fetch them. Change the Wi-Fi password and the code has to be regenerated — there is no way around that.

Step 3: generate it

Paste the destination in, pick the type, and the code appears. At this point it already works. Everything after this is about making it survive contact with the real world.

Step 4: test it before you do anything else

Scan it yourself, with a phone that is not the one you built it on, before it goes anywhere. Test from the actual camera app rather than a scanner app — that is what your audience will use. If the code is going on something printed, print one at final size and scan that, because a code that reads perfectly on a bright screen can fail on matte paper under a shop light.

Step 5: brand it, but not too much

Adding a logo and colours is fine and generally helps — a code that looks deliberate gets scanned more than one that looks like spam. Two limits worth respecting:

There is more detail in QR code design best practices.

Step 6: download the right file

Download SVG for anything printed. It is vector, so it is sharp at any size, from a business card to a billboard. Download PNG for screens and for tools that will not accept SVG. A PNG that looks fine in a browser can print visibly soft, because the printer wants far more detail than a monitor does.

Check the downloaded file rather than the preview for watermarks. Some generators add branding only at export.

Step 7: size it for the distance

The working rule is 10:1 — the scanning distance divided by ten is the minimum width of the code. A poster read from two metres needs a code about 20cm across. A table card read from 30cm needs about 3cm. Leave the quiet zone — the clear margin around the pattern — at roughly four modules wide; crowding it is one of the most common reasons a technically valid code will not scan. Best QR code size for printing has the full table.

What people wish they had done differently

Almost always the same three things: they used a static code and the page moved; they printed it too small for where it ended up; or they never tested a physical copy and found out from a customer. None of those are hard to avoid — they are just easy to skip.

If you want to try the mechanics rather than read about them, the free QR code generator makes a working code without an account.