If scanning a QR code opens a sign-in or “request access” screen, the phone has usually read the code successfully. Check the document link and its permissions next. Do not make a private document public just to remove an error.
Separate a scan failure from an access failure
| What the reader sees | What to check first |
|---|---|
| Camera does not recognize the QR | Contrast, blank border, focus, glare and printed size |
| Browser opens a sign-in or access request | Document permissions and the reader’s account |
| Browser opens a missing-file page | Deleted, moved, expired or incorrectly copied URL |
| Browser opens an old document | Encoded URL, document version and host caching |
| PDF opens but is hard to read | Document layout, text size and mobile alternative |
Compare the scanner’s destination with the intended sharing link. Avoid posting private links or screenshots containing access tokens when asking for help. For a code the camera cannot read, use the QR print sizing guide.
Test without the owner’s session
An owner can open a file that other people cannot. Open the intended link in a signed-out browser, then try it on a phone that is not signed in to the owner’s account. For restricted material, test using an authorized reader account instead. This checks access for the expected audience.
Google Drive’s sharing documentation distinguishes restricted files from files available to anyone with the link. Link access can work without a Google sign-in, but work or school administrators may limit external sharing. A QR code does not change these settings. Only an authorized owner or administrator should change access, and only for the intended audience.
Check the kind of link you encoded
A local file path is not a public web address. Temporary download links can expire. Use a stable HTTPS document address or approved sharing link, not an address copied from a local PDF viewer. Test that exact link before generating the code.
For a public brochure, a page on your own website can explain the download and offer accessible text. For a staff-only document, keep authentication and explain which account readers need. Never distribute confidential files through a public QR simply to make access easier.
Can you keep the printed QR?
Decode the printed QR and inspect its URL. If the address is correct and the problem is permissions, correcting authorized access at the host may resolve it without reprinting. If your host supports replacing the document at the same address, test that exact address after replacement. A new upload may receive a different address; do not assume it preserves the old link.
If the encoded URL must change, the static QR must change too. Generate and test a new code, then replace old prints. GenerateQR cannot edit a printed static destination or host a redirect for you. The static versus dynamic guide explains the distinction.
Proof the complete reader journey
Before approving a print run, check the final artwork at actual size, destination domain, document version, intended reader access and readability on a phone. Add a text URL beside the code as an alternative. Recheck after changing hosting, account ownership or file permissions.
If you need a new code, the PDF-link QR page explains destination and file choices. GenerateQR offers a free preview; one $4.97 payment buys one static QR in 4096px PNG, SVG and real PDF. That QR PDF is an export of the symbol, not hosting for your source document.