Comparison
QR Code for PDF: When to Link the File and When to Link a Page
A direct PDF works for a short manual, price list or resource people need to save. A landing page works better for navigation, several languages, calls to action and frequent content changes.
What actually happens when a phone opens a PDF
The decision is easier once you picture the experience rather than the file. A scan that leads straight to a PDF does not open a web page — it downloads a document and hands it to a viewer.
That viewer shows the page at the size it was designed for, which is almost always A4 or Letter. On a phone held at arm’s length, ten-point body text is somewhere near unreadable, so the reader pinches, zooms, and then drags horizontally to follow each line. There is no reflow. A two-column layout is worse still.
None of this makes PDFs wrong. It makes them wrong for some jobs and fine for others.
When a direct PDF is the right answer
Link the file directly when the document is genuinely the thing the person wants to walk away with:
- It is short, and designed to be legible at phone size rather than shrunk from print.
- People want to keep it — a spec sheet, a certificate, a warranty document, a manual they will consult offline later.
- It is stable, and will not change for months.
- It has to be printable or archivable exactly as laid out.
- The file is small. A twenty-megabyte brochure on mobile data is a download most people abandon.
When a page is clearly better
Point at a page instead as soon as any of the following is true:
- There is more than one document, and the visitor has to choose.
- More than one language is involved — a page can offer the choice; a PDF forces you to guess.
- The content changes: prices, menus, schedules, availability.
- You want to measure anything beyond the scan. A page reports what people did; a file download does not.
- The visitor needs context before committing to a download, or an action afterwards — booking, ordering, contacting you.
- The audience is on phones with poor connections, where a page loads and a large file does not.
A middle option people forget
The choice is not binary. A lightweight page that summarises the useful part and offers the PDF as a download underneath satisfies both groups: the person who wanted a quick answer gets it without downloading anything, and the person who wanted the document still gets the document.
This is usually the right answer for manuals, price lists and anything technical, where a minority genuinely wants the file and the majority wants one number out of it.
Make the code dynamic whichever you choose
This is the part that matters most and gets decided by default. If the printed code encodes the file URL directly, you are married to that URL forever — and file URLs are unusually fragile, since they change whenever the document is re-uploaded, renamed, versioned or moved to different storage.
A dynamic code lets today’s PDF become next quarter’s revised PDF, or become a page, without touching anything already printed. Given that the whole PDF-versus-page decision often gets revisited once real usage data arrives, printing a static code effectively locks in a choice you have not finished making.
Prepare the file so it survives the phone
If you are linking a PDF, a few minutes of preparation changes the experience substantially.
Compress it — most print-ready PDFs are many times larger than they need to be for screen reading, and size is the main reason people abandon the download. Give it a descriptive filename, because that name is what appears in the download and later in the reader’s files; `menu-autumn-2026.pdf` is findable and `final_v3_web.pdf` is not. Confirm the text is real text rather than a scanned image, so it can be searched, selected and read by a screen reader. And if it is more than a few pages, make sure the internal structure gives the viewer a usable outline.
Test it the way a stranger would
The destination is where most of these codes fail, and your own browser is the least reliable place to check.
Open it on a phone, in a private window, on mobile data rather than office Wi-Fi, using a device that has never opened it before. Confirm it is publicly reachable — no login, no expiring share link, no file that only resolves inside your network. Time the download honestly. Then read a price or a specification from it at normal holding distance without zooming, and see whether that was reasonable.
If it was not reasonable, that is the answer to the PDF-or-page question.
FAQ
Frequently asked questions
Should a QR code link to a PDF or a web page?
Link the PDF when the document itself is what people want to keep — a spec sheet, warranty or manual — and it is short, small and stable. Use a page when there are several documents or languages, when the content changes, when you want to measure what people did, or when the reader needs an action afterwards. A page summarising the content with the PDF offered underneath is often better than either.
Can I replace the PDF later without reprinting the QR code?
Only if the code is dynamic. A static code encodes the file URL in the pattern, so a re-upload, rename or move breaks every printed copy. With a dynamic code you repoint it at the new file — or at a page instead — and everything already printed keeps working. File URLs change more often than people expect, which makes this the default choice for PDFs.
Why is my PDF hard to read after scanning?
Because a PDF opens at the size it was laid out for, usually A4 or Letter, and does not reflow to the screen. Body text designed for print is close to unreadable on a phone, so the reader has to zoom and drag line by line. If people need to read rather than keep the document, that is the signal to point the code at a mobile page instead.
How large should the PDF be?
As small as you can make it while staying legible — most print-ready files are several times larger than screen reading requires. File size is the main reason people abandon a download on mobile data, and a scan that ends in an abandoned download is a scan wasted. Compress it and test the download on mobile data rather than Wi-Fi.
Can I track how many people opened the PDF?
You can count scans of the code, but not what happened afterwards — a file download is not a page and reports nothing back. If you need to know whether people read it, opened a particular section or went on to act, point the code at a page carrying the content or offering the file, and measure there.
NEXT STEP