What you are seeing
The code scans, the video page opens, but the video will not play: a black player, a spinning loader, or an error message. The scan worked, so the fault sits in the video, the page, or the playback conditions: a removed video, a restricted video, a blocked player, or a connection too weak for the stream. Visitors who expected a video meet a dead player, which feels like a broken promise. The fix is to test the video on its own, then the page, then the QR journey.
Likely causes
1.
Video removed, private, or restricted — A video that was deleted, set to private, or restricted by region or age will not play for visitors. Test: open the video directly and check its availability.
2.
Player blocked by the browser or app — An in-app browser, a content blocker, or a restrictive setting can block the video player. Test: open the same page in a different browser.
3.
Page loads but the player fails — A script error or a missing player component can leave a dead player on an otherwise working page. Test: open the page on a desktop and on a phone and compare.
4.
Connection too weak for the stream — A weak mobile signal can stall a video that plays fine on fast WiFi. Test: try the video on a strong connection.
5.
Link points at the wrong video — A mistyped link or a redirect can land visitors on a different video or a non-video page. Test: decode the payload and compare the link with the intended video.
Step-by-step fix
1. Decode the payload and write down the exact link it carries.
2. Open the video directly, outside the QR journey, and confirm whether it plays.
3. Open the destination page in a second browser and on a desktop.
4. Fix the video availability, the page, or the link, whichever is at fault.
5. Regenerate the code if the payload points at the wrong video.
6. Retest by scanning the code and watching the video play on two phones.
Putting this into practice
In practice, test the video on its own before you blame the code. A video that will not play when opened directly is a video problem, and no QR fix can repair it. A video that plays directly but not from the code points at the link or the page. Keep a short note of what you tested, what failed, and what you changed, so the next person starts from evidence rather than guesswork. A fix that is written down survives staff changes and reprints; a fix that lives only in memory gets repeated.
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)
