A QR code that opens a PDF is one of the most common ways to get a document from paper onto a phone. Restaurants use it for menus, manufacturers for manuals, schools for handbooks, and event teams for programmes. The code itself takes a minute to make. The problems show up weeks later, when the document changes and the code is already printed on a thousand flyers.
This guide covers how to prepare the PDF, how to choose the right kind of code, and how to swap the file later so the printed code keeps working.
Why codes that point straight at a file link break
The quickest method is to upload a PDF to a cloud drive, copy its share link and turn that link into a QR code. It works on day one. It tends to fail later for one of three reasons:
- The file moves or is renamed. Many storage services tie the share link to a single file. Upload a corrected version as a new file and the old link still opens the old document, or nothing at all.
- Permissions change. A drive cleanup, a staff member leaving, or a switch to company-only sharing can put a sign-in screen in front of every person who scans.
- The link is too long. Long share URLs produce dense QR patterns with small modules, which are harder to scan from a distance or when printed small.
None of these problems shows up when you test the code at your desk. They show up once the code is in the field, which is when they are most expensive to fix.
Static and dynamic codes
A static QR code stores the destination address directly in its pattern. Once printed, that address cannot change. A dynamic QR code stores a short redirect address instead, and the destination behind it can be edited at any time. For a PDF that will be revised (a price list, a timetable, a menu or a manual) a dynamic code is the safer choice, because the file can be replaced without touching anything that has been printed.
The trade-off is that a dynamic code depends on the redirect service staying active. Treat it as a maintained account with a named owner, not something set up on a personal trial and forgotten.
Step 1: Prepare the PDF for phones
Most people who scan will open the file on a phone, often over mobile data. A few checks make a large difference:
- Keep the file small. Under 5 MB opens quickly on most connections. Scanned documents are usually the largest; re-export them at a lower resolution or run them through a PDF compressor.
- Check readability on a small screen. A landscape A3 poster saved as a PDF is unreadable on a phone. A single-column layout with a body text size of at least 11 pt is easier to read.
- Make the text real text. If the PDF is a scan, run text recognition (OCR) so readers can search, copy and zoom cleanly. Plain-text conversion tools are useful here for checking what a screen reader or search box will actually see.
- Use a clear file name and title. The document title often appears in the phone’s viewer bar. “Spring-menu-2026.pdf” tells people they are in the right place; “scan0042.pdf” does not.
Step 2: Check who can open it
Open the file link in a private browser window, signed out of every account. If you see a sign-in prompt, a “request access” page or a download warning, so will everyone who scans. Fix the sharing settings, or host the PDF somewhere that serves it publicly.
Step 3: Create the code and test it properly
Create the code with a generator that can either host the PDF or point to a public PDF address. For example, QR code for PDF takes an upload of up to 10 MB or a link to a file you already host, and lets you change the file later from a dashboard. Whatever tool you use, test the code before anything goes to print:
- Scan it with at least two phones, one iPhone and one Android, using the built-in camera apps.
- Test on mobile data with Wi-Fi switched off.
- Print a test copy at the real size and scan it from the distance people will actually stand.
Step 4: Print checklist
- Size. A common rule of thumb is a code width of about one tenth of the scanning distance. A code read from 50 cm should be around 5 cm wide; one on a poster read from 2 m needs about 20 cm.
- Quiet zone. Leave a clear margin around the code, at least four modules wide. Text or borders that crowd the code are a common cause of failed scans.
- Contrast. Dark modules on a light background. Inverted or low-contrast colour schemes scan poorly on older phones.
- A short label. A line such as “Scan for the full manual (PDF, 2 MB)” sets expectations and increases scans.
Step 5: Replace the file when it changes
With a dynamic code, updating the document is a matter of uploading the new PDF, or changing the destination address if you host the file yourself. The printed code then opens the new version. Two habits help:
- Keep a version date inside the document, for example on the cover or in the footer, so staff and readers can tell at a glance that they are looking at the current file.
- Re-scan after every change. Upload errors and permission slips happen; a ten-second scan catches them before customers do.
Common mistakes
- Linking to a shared folder instead of the file, which forces readers to hunt for the right document.
- Putting a 40 MB scanned brochure behind a code on a train platform poster.
- Printing a static code for a document that changes every season.
- Using a share link that only works for people in your organisation.
A PDF QR code is simple to make. Making one that still works six months later comes down to a small, phone-friendly file, open access, a properly tested print, and a code whose destination you can change.