Choose a stable destination first
Generate the code from the permanent HTTPS address of the published card. Avoid disposable short links or destinations that will require the physical card to be reprinted after a routine profile update.
Use a practical preflight for QR code size, contrast, quiet space, final artwork, mobile loading and fallback links before printing business cards.
Generate the code from the permanent HTTPS address of the published card. Avoid disposable short links or destinations that will require the physical card to be reprinted after a routine profile update.
Do not crop the pale border around the code, round off its individual squares or place a busy photograph behind it. Keep the entire code flat, square and visibly separated from surrounding text.
Open the PDF or image sent to the printer and scan it at its intended size. Resampling and compression can blur edges even when the original generator preview was clear.
Test an actual proof in ordinary indoor light with at least two phones. Confirm the browser opens the expected HTTPS domain, the page loads over mobile data and the primary contact action works.
There is no universal size because distance, camera, material and code density matter. Start around 25 mm square for a close-range card and verify a physical proof before a full print run.
A code with strong error correction may tolerate a small overlay, but it reduces margin for print defects. A clean, unobstructed code is the more dependable choice.
Opening your NexaCard workspace…