QR codes are everywhere — on menus, business cards, posters, packaging and payment counters. Creating one is free and takes seconds. This guide shows how to generate a QR code for a URL, text, phone number or email, and how businesses can use them effectively.
What can a QR code contain?
A QR code can encode almost any short piece of information: a website link, plain text, a phone number that dials when scanned, or an email address. When someone points their phone camera at it, the content opens instantly — no typing required. That convenience is why QR codes have become a standard part of marketing and operations.
Create a QR code for free (no watermark)
The free QR Code Generator on apps2help.com creates clean, high-resolution QR codes you can download as PNG — no account, no watermark, and nothing uploaded. It runs entirely in your browser.
- Open the QR Code Generator.
- Choose the type: URL, text, phone or email, and enter your content.
- Download the QR code as a PNG and add it to your design, print or screen.
Smart ways businesses use QR codes
Offices and businesses use QR codes to link to digital menus, share Wi-Fi or contact details on business cards, drive print readers to a landing page, collect feedback, and simplify event check-ins. Because they are cheap to produce and easy to update (when pointing to a URL you control), they bridge physical and digital touchpoints efficiently.
Frequently asked questions
Do these QR codes expire? No — a static QR code encoding your link works permanently.
Is there a watermark? No watermark and no account required.
Is my data uploaded? No — the code is generated in your browser. See our Privacy Policy.
Get started: create your free QR code now.
Where a QR code earns its place in a small business
A QR code is only useful where the alternative is worse. Printing one on a shopfront window so passers-by can save your number beats asking them to type it. Putting one on an invoice so a client can open the payment page beats reading out an account number. Putting one on a website next to a clickable link achieves nothing, because the person is already on a device that can simply follow the link.
The practical test before you print anything: is the person holding a phone, and is the information they need awkward to type? If both answers are yes, a code helps. If either is no, it is decoration.
What to encode, and what it should point at
| Situation | Encode | Why |
|---|---|---|
| Shop window or signage | Website URL or vCard | Saves contact details in one tap |
| Invoice or bill | UPI or payment link | Removes transcription errors on account numbers |
| Business card | vCard | Details land in the phone book, not a photo roll |
| Restaurant table | Menu URL | Menu can change without reprinting |
| Event or workshop | Registration form URL | Captures details while interest is high |
| Product packaging | Support or manual page | Cuts support calls |
| Wi-Fi for customers | Wi-Fi credentials | No password read aloud across a counter |
Size, distance and the rule that governs both
The usable rule of thumb is that the printed code should be at least one tenth of the scanning distance. Someone scanning from half a metre needs roughly a 5 cm square. A poster read from three metres away needs a 30 cm square. A code on a shop window that people will scan from the pavement, perhaps two metres back, needs to be around 20 cm. Codes printed smaller than about 2 cm become unreliable on cheap phone cameras regardless of distance.
Leave a clear margin of white space around the code — roughly four modules, which in practice means a border about as wide as one of the corner squares. Codes butted up against text or a border fail far more often than people expect, and the failure is silent: the customer just gives up.
Error correction, and the trade-off nobody mentions
QR codes carry redundancy at four levels, from roughly 7% recovery up to about 30%. Higher redundancy means the code still scans when partly damaged, smudged or covered by a logo, but it also means more modules packed into the same square, so each module is physically smaller. On a small printed code, choosing the highest level can actually make scanning harder rather than easier. Use the higher levels for outdoor signage, stickers that will get scuffed, or when placing a logo in the centre. Use a lower level when the code is small, clean and indoors.
Static versus dynamic, in plain terms
A static code contains the destination itself. It works forever, needs no service, and cannot be changed. If you print a thousand flyers with a static code and then move the page, every flyer is dead.
A dynamic code contains a short redirect URL owned by a third party. You can change where it points and see scan statistics, but you are now dependent on that provider continuing to exist and continuing to honour their free tier. Plenty of businesses have discovered a year later that their printed codes now lead to an upgrade prompt.
For anything printed in volume, the safer pattern is a static code pointing to a short URL on your own domain, with a redirect you control. You keep the ability to change the destination without handing that control to anyone else.
A short checklist before you print
- Scan the final artwork with at least two different phones, one Android and one iPhone.
- Scan it at the actual distance and lighting the customer will face, including a night-time test for outdoor signage.
- Check the destination page works on mobile, loads quickly and does not demand an app.
- Print a caption. "Scan for our menu" converts far better than a bare square, because it tells people what they get.
- Keep the code dark on a light background. Inverted codes fail on many scanners.
- Test after printing, not just on screen. Ink bleed on absorbent paper can close the gaps between modules.
What tends to go wrong
The most common failures are mundane. Codes laminated with a glossy finish reflect overhead lights back into the camera. Codes printed on curved bottles distort beyond recognition. Codes placed above eye level on a wall force an angle the camera cannot correct. Codes linking to a page that redirects three times take long enough that people assume it is broken. And codes with no caption get ignored entirely, because nobody scans an unexplained square.
None of these are technology problems. They are placement and testing problems, and ten minutes of checking prevents all of them.