Processed locally
Your input stays in this browser.
Test the artifact, not the editor
Export the final file with its real colours and logo. Place it in the production artwork without rescaling one axis. Print a proof using the intended stock, finish and process; a screen preview cannot reproduce ink spread, glare or folds.
Read back the exported payload
Put the downloaded PNG through the reader before it reaches a layout application. For a web link, inspect the complete domain, path and query rather than trusting a short label. For WiFi, contact, event and message payloads, check every field in the decoded result. This catches an old file, a pasted character, or a changed form value before physical production makes that mistake expensive.
Use a small device set
Test at the smallest intended size and longest intended distance with several ordinary phones. Try bright and dim light, but do not treat one successful scan as a guarantee. Verify the decoded text or domain before approving the run.
Check the placement in the real design
Keep four light modules of empty space around the square after all crop marks, borders and nearby text are applied. Do not let a frame, photograph or coloured background invade that quiet zone. Check that a curved label, a fold, a seam or a perforation does not cross the symbol. A code can decode perfectly as a flat export and still fail because the finished package changes its geometry.
Record the approved production version
Save the exact exported file alongside the artwork proof and a note of the tested size, stock and destination. That record prevents an old QR image being silently reused when a menu link, WiFi password or event detail changes. It also gives a printer a clear asset to preserve: no last-minute recreation from a screenshot, no untested recolour, and no assumption that a previous successful scan approves a revised layout.
Keep an escape route
For costly packaging, use a short first run and retain the source artwork. A static QR destination cannot be changed after printing. Give the printer the approved export, not a screenshot from a chat or a copy assembled from fragments.
Build an approval sheet before artwork is released
For a restaurant table card, write down the exact HTTPS address, the file name, the date, the outside width and the place where the mark will sit. For example, a 42 mm square containing a 33-module matrix and an eight-module total quiet zone has a 1.02 mm module pitch: 42 divided by 41. That calculation is not a quality grade, but it makes a later resize visible. Put a decoded copy of the final address on the same sheet. A label that opens /summer-menu after the menu has moved to /menu is optically correct but operationally wrong.
Check what a layout application changed
Export the code once from the generator, then export the complete page from the design application. Decode both files. The second check catches a PDF workflow that converted a vector to a low-resolution bitmap, applied non-uniform scaling, clipped the margin, or substituted a transparent logo background. Compare their pixel dimensions and keep the original QR asset separate from the page PDF. The inspection is about the production artifact, not whether the generator once produced a readable square.
Run a small proof with a defined pass condition
Print three copies on the actual stock: one from the intended printer and two from the likely production route. Ask three people with ordinary phones to scan each copy at the intended position. Record whether each person reaches the expected page without moving closer than the sign permits. Nine successful scans do not certify every device, but they reveal a proof that only works under a convenient desk lamp. A failed proof is a reason to change the artwork or process before a large run, not to ask scanners to try harder.
Treat finishing operations as separate risks
A code can be clean before finishing and fail after trimming, laminating, varnishing, folding or placing it over a seam. On a carton, inspect the assembled package rather than the flat dieline: the fold may pass through a finder square, while a glossy coating can produce a bright reflection across several modules. On a bottle, photograph the code from the scanner's expected direction; curvature can make nominally square modules appear compressed. Mark the safe placement area on the dieline so the next artwork revision does not recreate the same problem.
Approve a version, not an intention
An approval should identify one payload and one visual file. If a campaign manager changes a UTM parameter, a designer changes navy to pale blue, or a printer substitutes stock, that is a new version requiring another read-back and proof. Store the approved SVG or PNG with a checksum or revision name, not merely a screenshot pasted into an email. This avoids the common hand-off error where the printer receives a visually similar image whose link or quiet border differs from the approved item.
Know when the checklist is not enough
A preflight scan cannot qualify a regulated barcode, prove point-of-sale interoperability, or assess a code read at speed by industrial equipment. GS1's current 2D retail guidance distinguishes module dimensions and quality requirements by scanning environment; a consumer-phone proof is not a substitute for that verification. For an ordinary public link, the checklist ends with a readable physical proof and a correct destination. For a controlled retail or production workflow, give the identifier owner and the receiving system a format-specific sample as well.
External reference for the margin rule
The four-module quiet-zone figure used here is the QR Code rule described in the GS1 2D retail implementation guideline. It calls the module size the X-dimension and explains that graphics or noise in the surrounding margin can prevent a reader locating the symbol. That source describes retail deployment, so it should not be misrepresented as a promised phone-camera distance or a universal paper specification. It is useful here because it names exactly what the preflight must preserve: four clear X-dimensions on every side.
The decision after the proof
When the proof fails, write down the observed failure and send the source asset back to the person who controls that variable. A cropped margin is a layout correction; a smeared small module is a size or production correction; a stale decoded link is a content correction. Do not approve a run merely because a different image scanned once. A short, dated approval sheet with the retained final file is enough to make the next action clear to a printer, designer and site owner.