What you are seeing
This fix makes the download behind the code complete reliably. You will test the file on its own, check the server and the file size, and repair the link, the file, or the serving setup. Verify the fix by scanning and downloading the complete file on two phones.
Likely causes
1.
File too large for the connection — Quick test: try the download on a strong connection and compare.
2.
Server interrupting the download — Quick test: download the file directly on a desktop and check whether it completes.
3.
Link points at an incomplete or moved file — Quick test: check the file on the server and compare its size with the expected size.
4.
Phone storage full — Quick test: check the storage on the failing phone.
5.
Redirect breaking the download — Quick test: follow the redirect chain and watch the download behaviour.
Step-by-step fix
Step 1: Decode the payload and write down the exact download link it carries.
Step 2: Download the file directly on a desktop and confirm it completes with the expected size.
Step 3: Check the file on the server. Re-upload it if it is incomplete or truncated.
Step 4: Test the download on a strong connection, then on a weak mobile connection.
Step 5: If the file is large, split it, compress it, or link to a page that offers it as a choice.
Step 6: Fix any redirect that interrupts the download, or point the code at the direct file link.
Step 7: Retest by scanning the code and downloading the complete file on two phones.
Putting this into practice
In practice, check the downloaded file size against the expected size after every test. A file that arrives short is a file that failed, even if the phone reports the download as complete. Record the before-and-after behaviour with the job file, so the fix is provable rather than anecdotal. When the same failure appears again, that record tells you whether the old fix held or a new cause appeared.
Common mistakes to avoid
- Linking a QR code to a huge file and assuming visitors will wait for it on a weak mobile signal.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that scans but the download stops halfway will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that scans but the download stops halfway.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The file downloads completely on a desktop
- The server file size matches the expected size
- Scanning downloads the complete file on two phones
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [QR expiry checker](/qr-expiry-checker)
- [QR redirect chain viewer](/qr-redirect-chain-viewer)
- [QR payload inspector](/qr-payload-inspector)
- [QR scan log](/qr-scan-log)
- [QR safety checker](/qr-safety-checker)
- [PDF QR code generator](/pdf-qr-code-generator)
