Published:
Part of the label never makes it onto the media: the right edge of a barcode is missing, the bottom line is gone, or the printer feeds a second, half-printed label. "Cut off" looks like one problem but is two very different ones — and they have opposite fixes.
A thermal printer does not raise an error for content beyond the printable
area — it clips silently. If ^PW says the label is 812 dots wide
and a field starts at ^FO780,..., most of that field simply does
not exist on paper. The same happens vertically against ^LL, and
a shifted origin (^LH) or a label-shift (^LS) can
push otherwise-correct fields over the edge wholesale.
The tell: only some elements are clipped, always the same ones,
and the label's overall size is right. The fix is in the layout — move the
offending ^FO/^FT coordinates inside the declared
size, or enlarge ^PW/^LL if the media is actually
bigger than the file claims.
If everything is oversized — text, barcodes, spacing — and the layout runs off the right side and bottom together, the file was authored for a higher resolution than the printer has. ZPL written for 300 DPI (12 dots/mm) and sent to a 203 DPI (8 dots/mm) printer prints every distance 1.5 times too long: a 4×6 design needs a 6×9 sheet it does not have, so the printer clips the right edge and continues onto the next label.
The tell: the proportions are perfect, just too big, and the numbers give
it away — divide ^PW by your printer's DPI and you get more
inches than the media measures. The fix is the mirror of the too-small case:
rescale every dot value by 8/12 (≈0.68) so the layout fits the coarser head —
coordinates, label size, fonts and ^BY together, rounded to
whole dots.
Compare two numbers: the declared size (^PW/^LL)
and the furthest field position in the file. Fields beyond the declared size
with a plausible label size point to cause 1. A declared size that is
physically larger than your media at the printer's real DPI points to
cause 2. A browser-based preview draws the same clipping the printer
would produce, so both checks work before a single label is spent.
Media calibration teaches the printer where a label starts and ends; it does not move a field at dot 780 back inside a 812-dot canvas, and it does not shrink a 300 DPI layout. Darkness and speed settings change print quality, not geometry. If the geometry is wrong in the file, the file is where the fix lives.
Either specific fields sit beyond the declared ^PW/^LL — the printer clips them silently, without an error — or the whole file was written for 300 DPI and prints 1.5x too large on a 203 DPI printer, running off the media.
If only some elements are missing and the label size is right, fields are outside the declared size (cause 1). If everything is proportionally oversized and ^PW divided by your printer's DPI exceeds the media width, it is a resolution mismatch (cause 2).
No — calibration teaches the printer where a label starts and ends. It does not move a field back inside the canvas and does not shrink an oversized layout; if the geometry is wrong in the file, the fix is in the file.
ZPL is the language Zebra thermal printers understand. How to read the commands, how a label is put together, and the most common mistakes.
Which barcode symbology should I use?EAN-13, Code 128 or QR? Practical rules for picking a barcode based on your data, your space and the scanner that has to read it.
How to preview a ZPL file without a printerA ZPL file is just text — the label only exists once something draws it. Three practical ways to see a ZPL label before it reaches the printer.