Sign In
Products
ZPL ViewerBarcode GeneratorImage → ZPLZPL cheat sheetLabel DesignerTemplate Gallery
Developers
API QuickstartAPI ReferenceMCP ServerBulk GenerationWebhooksSDKs & ExamplesLimitsDirectPrint agent NewGitHub ActionVS Code extensionOn-Premise
Solutions
Logistics & ShippingE-CommerceERP & WMSManufacturingRetailHealthcare & LaboratoryAll solutions
Tools
ZPL Diagnostics HubZPL DebuggerSize & DPI AnalyzerDPI ConverterBarcode fit calculatorShipping Label AnalyzerFont InspectorOrientation DebuggerCalibration AssistantPrinter Compatibility CheckerBarcode Readability CheckerPrinter Language DetectorThermal Printer Test PackZPL ToolsEPL ToolsTSPL ToolsCPCL ToolsPrinter Language ConverterAll ToolsGuidesPricing
Language
EnglishTürkçeDeutsch
Home›Guides›The printer prints gibberish

The printer prints gibberish

Published:

Paste your code

Paste code or load the sample — the result appears below, with the line and severity of each finding.

Result

Health report

Instead of a label, the printer produces lines of raw characters — often right after a calibration run. Two very different causes share this symptom, and the printout itself tells you which one you have.

Read the gibberish before replacing anything

If you can recognise your own data in the output — the ZPL commands themselves printed as text, carets and tildes included — that is almost always dump mode: a diagnostic state in which the printer prints the bytes it receives instead of interpreting them. It is easy to trip accidentally during a feed-button sequence, which is why it so often follows calibration.

Leaving it: power-cycle the printer. If it comes back dumping, send ^XA^JR^XZ — or power-cycle while not holding feed.

Genuinely scrambled glyphs: a language mismatch

If the output is not readable echoes of your file but truly garbled characters, the other candidate is that the printer does not speak the language of the file. Older desktop generations are EPL printers, and feeding ZPL to an EPL interpreter produces exactly this half-digested output. Checking which language your file actually is takes a second with the printer language detector — and rules that half in or out.

Why the distinction matters

The two fixes share nothing: dump mode ends with a reset and no file changes; a language mismatch ends with converting the job or re-targeting the printer, and no number of resets helps. A minute spent reading the printout picks the right path — and an old printer that "went crazy" after calibration usually just needs the first one.

Related guides

Every label in the job prints the same time (^FC, ^SL)

A multi-label ZPL job stamps every label with the same clock value. That is ^SL's documented default, not a bug — and ^SLT changes it.

ZPL special characters print wrong

Umlauts and accents printing as garbage is an encoding mismatch: the printer decodes your UTF-8 bytes with a legacy code page. ^CI28 fixes it — here is how.

ZPL troubleshooting by symptom

Eight common ZPL label failures mapped to their usual cause and the check that confirms it — plus what a preview can and cannot prove.

Only the last graphic prints

A format with several ^GB boxes prints only the final one on a mobile printer. The file is usually innocent: check the active printer language first.

Try your own ZPL code →