Print QR codes people can actually scan

Prepare website QR codes for print: check destinations, preserve quiet zones, choose PNG or SVG, and test the actual sheet before printing a batch.

Prepared by UrlToFile Dev · Updated October 11, 2026.

A code that scans on your monitor can fail on a small, glossy or poorly printed label. Start with the destination, then check the exported file and a physical proof. This checklist is for static website codes created with URL to QR code. For plain text and other values, use the general QR generator.

1. Check where the code will take people

Open the destination yourself. Confirm the page is available to your audience without your account, has the right content and works on a phone. URLtoFile encodes the address you enter; it does not fetch the page or verify that the website is safe or reachable. Missing schemes become HTTPS, so inspect the normalized address in the result.

The QR image has no built-in expiry or editable destination. The website it points to can still move, require a login or stop working. Avoid temporary invitation links on permanent posters. URLtoFile short links and sharing invitations last two hours, with one optional 30-minute extension; placing one in a QR code does not extend that deadline.

2. Choose an export for the job

• One code in a designed poster: choose SVG when your layout app accepts vector artwork. It stays sharp as you resize it. PNG also works; use enough pixels for its intended printed size and avoid stretching it into a rectangle.
• A ready-to-print batch: choose Bulk URLs and Print sheet for four codes per A4 page, or PDF pages for one code per page. Review the PDF's page count before printing.
• Separate image assets: choose PNG archive to download the batch in one ZIP. Files follow the input order; keep a copy of your destination list so you can match each numbered image.

Pixel size is not print size. A 1024-pixel PNG can still become unreadable if you shrink it to a tiny label. There is no universal minimum physical size: the data density, printer, camera, distance and lighting matter. DENSO WAVE's module-size guidance explains why larger individual squares are generally easier to read.

3. Protect the empty border

The white space around the pattern is the quiet zone. QR codes require a clear margin at least four modules wide on every side, according to DENSO WAVE's code-area guidance. A module is one square in the pattern. URLtoFile includes this margin in its exports; keep it when placing the image in another document.

Use a dark pattern on white. Do not crop the border, place text over it or overlay a logo on the pattern. Extra error correction can improve resilience to some damage, but it can also make a code denser. It does not replace adequate size, contrast or testing. Start with Medium for an ordinary undamaged print and test the chosen output.

4. Practice with three known destinations

In URL to QR code, choose Bulk URLs and paste these three public URLtoFile pages, one per line. These are practice destinations, not sample customer or event data.

https://www.urltofile.com/guide/
https://www.urltofile.com/resize-image/
https://www.urltofile.com/qr-code-generator/

1. Keep the black pattern, choose 1024 px and Medium, then choose Print sheet.
2. Create the codes. Check that three previews appear in the same order as your list and that their normalized addresses are correct.
3. Download the PDF and confirm it contains one page with three codes. Labels can shorten long addresses; the QR pattern still encodes the complete address. Use the preview and your source list to verify the full destination.
4. Print one proof at the scale you plan to use. Scan all three codes with a phone and confirm the File guide, Resize image and general QR generator open respectively.

The URL tool accepts up to 100 HTTP/HTTPS addresses, 2,000 characters per address and 50 MB of generated PNGs per batch. It does not accept CSV headers, embedded passwords or spaces inside an address. If a line fails validation, fix the identified URL and create the batch again.

5. Test the physical proof before the full run

• Scan the actual printed sheet at the intended distance, not only the on-screen preview. Try a second phone if available.
• Check normal lighting and the material you intend to use. Glare, folds, blur and low ink can make an otherwise valid code hard to read.
• Check every destination before distribution. For repeated labels, test copies from different positions on the sheet.
• Add a human-readable destination or short explanation beside the code, outside its quiet zone, so people know what they are opening.

If it will not scan

The camera finds no code: restore the white border, use black on white, increase the printed size and export again from the original settings. Avoid screenshots and repeated image compression. If the address is unnecessarily long, use a shorter permanent address you control rather than a temporary short link.

The code scans but the page fails: open the displayed address manually. Check for a typo, changed page, login requirement or expired invitation. Printing a larger image cannot repair a broken destination.

The download is missing: check browser downloads and save the generated output explicitly. A download click confirms a request to your browser, not that a file reached disk. Reopen the saved PDF, PNG or ZIP before sending it to a printer.

Create website QR codes → · Create a text QR code → · More practical file guides →