To create a QR code for a PDF you host the file somewhere, then encode that file's link in the QR code. A QR code cannot contain the PDF itself — the format holds roughly 3 KB of text at most, thousands of times smaller than any real document. Every "PDF QR code" is a link to a hosted file.
At a glance
- The QR code stores a link, never the file. Any tool claiming to embed the document itself is describing the link.
- Use a dynamic code so you can replace the PDF later without reprinting. This is the single most common regret with printed PDF codes.
- Decide whether scanning opens the file straight away or shows a landing page first. They suit different jobs.
- Keep the file small. People scan on mobile data, often on a poor connection.
- For menus and anything read on a phone, a mobile-friendly web page usually beats a PDF. Reach for a PDF when the document must be printed or kept as-is.
Why the QR code can't contain the PDF
A QR code is a container for text, and a small one. At the largest standard version with the lowest error correction, it tops out around 2,953 bytes — under 3 KB. A one-page PDF with a logo is typically 100 KB to several megabytes.
So the pattern holds an address, and the file lives somewhere else. Everything below is really about where that file lives and who controls it.
This also explains a practical point: because the encoded text is just a URL, the length of that URL affects the pattern's density. A long hosting URL with a signed token produces a visibly denser code that is harder to scan when printed small. A short link keeps it sparse.
Where to host the file
Three options, with real trade-offs.
Your own website. Upload the PDF, link to it. Free if you already have hosting, and you keep full control. You must keep the URL alive forever, because a printed code pointing at a deleted file is dead. If you take this route, use a URL on your own domain — that way you can redirect it later if the file moves.
A cloud drive. Fast, but risky for print. Sharing links can change when permissions are edited, some services interstitial with a sign-in prompt, and a "view only" link may open a preview rather than the document. Fine for internal use, poor for anything printed.
A QR platform that hosts the file. The file is stored for you and the code points at a short link on the platform's domain whose destination you can change at any time. You get to swap the file later without reprinting, plus scan analytics. The trade-off is the one common to all dynamic codes: it depends on the provider staying alive.
How to create the QR code
- Choose the PDF QR type, not a plain URL type. File types usually get extra handling — proper content headers, a viewer, and a download option.
- Upload the file.
- Choose direct or landing page — see the next section.
- Download the code in a print format. Use SVG or PDF for print, never a small PNG. A vector file stays sharp at any size; a 300px PNG blown up to poster size will not scan. Check this before you commit to a platform — vector export is commonly a paid feature, and on PixlQR it is included on Plus and during the trial, while the free plan exports PNG.
- Print a test at the real size and scan it from the real distance.
Test on both iPhone and Android. They hand PDFs to different viewers, and a file that opens cleanly on one can prompt a download on the other.
Direct file or landing page?
Most PDF QR tools offer both. The choice matters more than it looks.
Direct sends the scanner straight into the PDF. Fewest taps, fastest to the content. Best when the document is the point — a menu, a spec sheet, a form someone needs right now.
Landing page shows a branded page first, with the document title, a preview and a download button. Better when you want context, branding, or a next step beside the file. Also more forgiving: if someone's browser handles PDFs badly, they still get a clear download button rather than a blank screen.
One catch worth knowing before you pick a hosting route: the landing page is only available for files uploaded to the platform. In PixlQR, a PDF linked from an external URL always opens directly, because a file on someone else's server cannot be wrapped in a branded page. If the landing page matters to you, upload the file rather than linking it.
| Direct | Landing page | |
|---|---|---|
| Taps to content | Fewest | One more |
| Branding | None | Yes |
| Behaviour on awkward browsers | Can look broken | Always a working download |
| Best for | Menus, spec sheets, forms | Brochures, reports, lead magnets |
Rule of thumb: if the reader is standing up and in a hurry, go direct. If they are sitting down and evaluating something, use a landing page.
File size matters more than you think
People scan on mobile data, often on a weak connection, sometimes in a basement restaurant.
- Under 1 MB is comfortable
- 1–5 MB is usually fine on decent signal
- Over 10 MB will lose people, and there is no way to tell how many
Before uploading, compress the PDF, downsample images to screen resolution rather than print resolution, and drop embedded fonts you do not need. A menu does not need 300 dpi photography.
Watch out for: the export you send to a printer is the wrong file to put behind a QR code. Keep two versions — the print master and a compressed screen version.
Hosting platforms also cap what you can upload, and the cap is usually tier-based rather than technical. PixlQR allows 5 MB per file on the free plan and during the trial, and 50 MB on Plus. Worth checking before you build a workflow around a 20 MB brochure.
When you should not use a PDF at all
This argues against the thing this article is about, which is exactly why it is here.
A PDF has a fixed page size. Phones do not. That mismatch means pinch-zooming, horizontal scrolling, and text too small to read — the everyday experience of scanning a restaurant menu QR and getting an A4 document.
Use a web page instead when the content is read on a phone and changes often. Menus, price lists, event schedules and product information are almost always better as a mobile-friendly page.
Use a PDF when the document must keep exact formatting, needs to be printed or saved, must stay a fixed legal record, or is genuinely a document — a manual, a contract, a whitepaper, a spec sheet.
The QR code works identically either way. Only the reading experience changes.
Mistakes that waste a print run
- Using a static code for a document that will be updated. The most expensive mistake here. Menus, price lists and brochures all change.
- Linking to a cloud drive whose permissions or URL can change.
- Uploading the print-resolution file. See above.
- Exporting the QR as a small PNG for a large print. Use SVG or PDF.
- Not testing on a real phone, from real distance, on the real printed material.
- Deleting or moving the source file later without a redirect in place.
Frequently asked questions
Can a QR code store the PDF itself so it works offline? No. The format holds under 3 KB. Offline access requires downloading the file first.
Can I change the PDF later without reprinting? Yes, if you used a dynamic code — upload the replacement and every printed code serves the new file. Not with a static code, unless the URL is on a domain you control and you can redirect it.
Why does my PDF download instead of opening? That is the browser's decision, based on the response headers and its own settings. Platforms that support PDF types usually serve the right headers so it previews. A landing page avoids the ambiguity by giving people an explicit choice.
Is there a page limit? Not from the QR code. Practical limits come from file size and patience.
Can I track how many people opened the PDF? You can track scans of a dynamic code. Whether someone then read page 4 is not something a QR code can tell you.
Try it yourself
Upload a PDF, get a code, and swap the file later without reprinting anything.
Create a PDF QR code — free plan, no card required.
Read next
Try it: build a QR code here
An interactive builder loads in this space. If it stays empty, enable JavaScript to use it — or create an account and build your QR code in PixlQR.