QR code label sheets

Before you print thirty of them

Every sheet carries a 100 mm rule across the bottom margin, with a dashed mark at four inches sitting 1.6 mm past the end of it. That rule is the whole reason this page is trustworthy. A browser can tell the printer the exact sheet size, position every cell to a tenth of a millimetre and still have the print dialog quietly shrink the lot by four to six percent to clear the printer's unprintable edge — and nothing on screen will hint at it. Print one sheet, put a ruler on it, and you know.

If the rule measures 100 mm, everything else on the sheet is right too. If it measures 95 or 96, the dialog scaled the page and the fix is in the dialog, not here.

Chrome

Open More settings. Set Scale to Default or Custom 100, and Margins to None. Leave Background graphics on — the codes themselves are vectors and print either way, but the fold lines and cut marks are cleaner with it on. Chrome's Default scale is not always 100 on every printer driver, so if the rule measures short, choose Custom and type 100.

Safari

Untick Scale to fit and set the scale to 100%. Turn on Print backgrounds. Safari's default is to fit the page to the printer's imageable area, which is the single most common reason a label grid comes out a few millimetres short across a sheet.

Save as PDF

Both browsers offer Save as PDF as a destination in the same dialog, so a PDF costs nothing extra and no PDF library is loaded on this page. The same scale setting applies — a PDF saved from a scaled print is scaled.

The four layouts

Table tents put two folded tents on a sheet. Each tent prints the code twice, the top half turned upside down, so once you fold it along the dashed line it reads from both sides of the table. That is the layout for a restaurant menu code, a Wi‑Fi code on a guest-room desk or a payment code at a market stall.

Place cards are the same idea at six per sheet, caption first: a name, a table number or a shelf label with the code beneath it.

Address labels follow the published geometry of Avery 5160 on US Letter — 30 labels of 2.625 × 1 inch, 3 across and 10 down — and Avery L7160 on A4, which is 21 labels of 63.5 × 38.1 mm, 3 across and 7 down. The code sits on the left of each label with the caption beside it, and no cut marks are drawn because the stock is already die-cut. This is the preset where calibration decides the outcome: a 96% print is fine on the first row and half a label out by the tenth.

Sticker grid is 30 codes on plain paper with light corner cut marks, for asset tags, ticket stubs, seed-tray labels and anything you will cut with a guillotine rather than peel.

There is deliberately no custom rows-and-columns builder. It is the control that makes print layout fragile and it is not what stops a sheet from working — alignment is.

Where the codes come from

Two sources. One code, repeated takes a single payload and fills the sheet with it, which is what a Wi‑Fi code, a review link or a menu code actually needs. A CSV reads one code per row through the same RFC 4180 parser and the same delimiter detection the bulk CSV tool uses, so a file that batches cleanly there lays out cleanly here — this page is the half of that job that used to end in a ZIP of loose PNGs and a trip to Word.

Every distinct code on the sheet is read back through the decoder before you print, and the verdict sits above the preview. The sheet also reports the smallest printed module in millimetres, and warns below about 0.4 mm — the point where ordinary toner spread and a phone camera stop agreeing about where a module edge is. A code can read back perfectly on screen and still be too small to work on paper, and that is a fact only a print page can tell you.

Questions