This is the version for beginners: no history of the format, no explanation of the black-and-white squares, just the four decisions that decide whether your first QR code actually works. Most bad first codes don't fail at the making, they pick the wrong content type, print too small, or skip testing before a hundred copies go out the door.
The steps below follow the same order MakeQR's own generator asks for: what the code should do, how permanent it needs to be, and what to check before trusting it on paper. It's aimed at someone making their very first code for a flyer, a recipe card, or a classroom handout.
Making your first QR code
Decide what the code should actually do
A website link, a WiFi network, a contact card, or plain text are the common starting points. Picking the matching field matters more than anything else — a WiFi password typed into a plain-text field, for instance, won't offer to join the network the way the WiFi type does.
Fill in only that field, completely
A URL needs the full address including https://. A WiFi code needs the exact network name and password, matching case. A contact card needs at least a name and one way to reach you.
Leave it static unless you'll need to change it
Static is free, needs no account, and never expires — the destination is baked into the pattern. Only pick dynamic if you expect to change the link later and don't want to reprint.
Scan it yourself before you trust it
Use your own phone's camera on the on-screen preview. This catches a typo in a link or a mistyped WiFi password before it's printed anywhere.
Download the right file for where it's going
PNG is fine for a document or a home printer. SVG is the better choice for anything going to a print shop or getting resized, since it won't blur when enlarged.
The mistake that causes most first-code problems
The most common beginner mistake isn't a broken code — it's the right code for the wrong content type. Typing a WiFi password into a plain-text or URL field produces a code that a phone reads as text or tries to open as a web address, instead of offering to join the network. The same goes the other way: pasting a long block of text meant to be read, like a recipe or a set of instructions, into the URL field, where it either fails outright or produces an unreadably dense pattern. Matching the content to its purpose-built field is the one step worth double-checking before anything else.
Static or dynamic, decided in one sentence
If the answer to "will this destination ever need to change after I print it" is no, pick static — it's free, permanent, and there's nothing more to set up. If the answer is yes, or you're not sure, pick dynamic: it needs a free account with a verified email, the first two codes stay free forever, and it shows a running scan count. WiFi passwords and contact cards can't be dynamic either way, since the content is written directly into the pattern rather than pointing at a link.
What actually ends up inside the code
Whatever you typed, in a format that particular content type uses. A URL becomes a plain web address. A WiFi network becomes a short string with the network name, password and security type packed together. A contact card becomes a small block of structured text a phone's address book understands. None of it is compressed or encrypted — anyone who reads the pattern reads exactly what you typed.
https://example.comHow big to print it
A rough rule covers almost every case: the code should be about a tenth of the distance it will be scanned from. A business card or a recipe card, read up close, can be as small as 20 mm. A poster meant to be read from across a room needs to be much bigger, closer to 200–300 mm.
Print it at least 20 mm (2.0 cm) wide
Mistakes first-timers make
Shrinking it to fit a tight corner
A code squeezed down to fill leftover space on a business card often ends up too small to focus on, especially once it's printed rather than viewed on a screen.
Skipping the test scan before a big print run
A typo in a link or a mistyped password is invisible until someone actually scans it. Test it yourself first, every time.
Choosing dynamic out of habit
Dynamic makes sense for a link that might change. For anything permanent — a fixed recipe, a one-time flyer — static does the same job for free and uses none of your two forever-free dynamic slots.
Low-contrast colors chosen for looks
A light gray pattern on white looks clean but frequently fails to scan in print. MakeQR flags this before download, so don't override the warning just for style.
The simplest static-versus-dynamic rule for a first code
Default to static. It costs nothing, needs no account, and covers the overwhelming majority of first codes — a flyer, a recipe, a one-off event. Reach for dynamic only once you hit a real reason: a link you expect to change, or wanting to see a scan count. Both of your first two dynamic codes are free forever if you do.
How dynamic QR codes workTypical first codes
- A garage sale flyer linking to a photo album of the items.
- A recipe card linking to the full recipe with step photos.
- A classroom worksheet linking to a short instructional video.
- A small business's first flyer linking to an online booking page.