What you are seeing
This fix restores playback to the video behind the code. You will test the video on its own, check the page and the playback conditions, and repair whichever step blocks it. Verify the fix by scanning the code and watching the video play on two phones.
Likely causes
1.
Video removed, private, or restricted — Quick test: open the video directly and check its availability.
2.
Player blocked by the browser or app — Quick test: open the same page in a different browser.
3.
Page loads but the player fails — Quick test: open the page on a desktop and on a phone and compare.
4.
Connection too weak for the stream — Quick test: try the video on a strong connection.
5.
Link points at the wrong video — Quick test: decode the payload and compare the link with the intended video.
Step-by-step fix
Step 1: Decode the payload and write down the exact link it carries.
Step 2: Open the video directly in a phone browser. If it does not play there, the video itself is the problem.
Step 3: Open the destination page in a second browser and on a desktop, and compare the player behaviour.
Step 4: If the video is private, removed, or restricted, restore its availability or point the code at a working video.
Step 5: If the player fails on the page, fix the page or link to the video directly.
Step 6: If the link is wrong, regenerate the code from the correct video link.
Step 7: Retest by scanning the code on two phones and watching the video play to the end.
Putting this into practice
In practice, keep video codes pointed at videos you control and monitor. A video that goes private or is removed after the code is printed leaves every visitor facing a dead player. 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
- Reprinting a video QR code when the video itself was set to private.
- 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 video will not play 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 video will not play.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The video plays when opened directly
- The page player works on two phones
- Scanning the code plays the intended video
- 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 payload inspector](/qr-payload-inspector)
- [QR redirect chain viewer](/qr-redirect-chain-viewer)
- [QR expiry checker](/qr-expiry-checker)
- [QR scan log](/qr-scan-log)
- [QR safety checker](/qr-safety-checker)
- [blog](/blog)
