What you are seeing
This fix produces a print that reads correctly instead of mirrored. You will compare the proof with the digital file, find the step that flips the image, and correct that step. Verify the finished print against the file, because a file that looks right on screen can still print mirrored.
Likely causes
1.
Transfer or reverse print process flips the image — Quick test: compare the finished print with the digital file.
2.
Image flipped in the layout — Quick test: compare the layout file with the original export.
3.
Plate or engraving reversed — Quick test: compare the plate or screen with the digital file.
4.
Viewing the print from the reverse side — Quick test: view the print from the intended side.
5.
Proof checked without scanning — Quick test: scan the proof instead of only looking at it.
Step-by-step fix
Step 1: Compare the proof with the digital file. Check which corners hold the finder patterns.
Step 2: Scan the proof. A mirrored code will not scan, which confirms the flip.
Step 3: Compare the layout file with the original export to see whether the layout flipped the image.
Step 4: If the process flips the image, such as a transfer, pre-flip the file so the finished print reads correctly.
Step 5: If the plate or screen is reversed, remake it from the correct orientation.
Step 6: Print one corrected proof and scan it on two phones.
Step 7: Approve the run only when the proof scans and the finder patterns match the digital file.
Putting this into practice
In practice, add a scan test to the proof routine for every process that flips the image, such as transfers, stamps, and engraving. The scan is the test that proves the finished print reads correctly. 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
- Proofing a mirrored code by eye only, without scanning it, and approving a run that no phone can read.
- 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 prints mirrored will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that prints mirrored.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The proof finder patterns match the digital file
- The proof scans on two phones
- The transfer or plate orientation is correct for the process
- 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 minimum size checker](/qr-minimum-size-checker)
- [QR contrast checker](/qr-contrast-checker)
- [QR print proof checklist](/qr-print-proof-checklist)
- [QR DPI calculator](/qr-dpi-calculator)
- [QR quiet zone calculator](/qr-quiet-zone-calculator)
- [printed QR tester](/printed-qr-tester)
- [QR size calculator](/qr-size-calculator)
