Skip to content

Print ZPL labels on Zebra printers

For Zebra printers, CloudPrint can send ZPL as RAW data when the discovered queue advertises both the ZPL language profile and RAW passthrough. Confirm those capabilities and test the exact printer model, DPI and media before production.

Confirm the discovered printer

Call GET /api/v1/printers and inspect capabilities.language_profiles, supported_dpi, media information and endpoint.raw_passthrough_available. The display name or Zebra brand alone is not proof that this operating-system queue accepts RAW ZPL.

Prepare a minimal ZPL document

A simple test label might be:

text
^XA
^PW812
^LL1218
^FO40,40^A0N,40,40^FDCloudPrint test^FS
^FO40,110^BCN,120,Y,N,N^FDORDER-18452^FS
^XZ

^PW and ^LL are dots, so calculate them for the real media and 203 or 300 DPI device. Verify fonts, code pages, graphics and barcode commands on the physical printer rather than relying only on an online preview.

Upload and route ZPL correctly

Upload it as document_format=raw with document_raw_language=zpl, then create a job for the compatible printer_id. Sending the bytes as PDF, omitting the RAW language or routing to a PDF-only queue produces a validation or routing error—it is not an automatic conversion request.

Configure the physical printer

Calibrate the media sensor and set the correct width, darkness and speed in the printer or driver. Higher darkness is not always better: it can spread barcode bars and reduce scan reliability. Keep the approved media profile and DPI with the workstation configuration.

Diagnose failed or poor output

For a failed job, collect print_job_id, X-Request-Id, failure reason, driver, connection type and advertised capabilities. For shifted, blank or unreadable output, test a minimal ZPL label locally, recheck DPI and media calibration, and then compare the exact payload. Do not place customer label data or access tokens in logs.

Production checklist

  • Calibrate the label size and verify the installed printer driver and queue.
  • Store the stable printer identity instead of relying only on a display name.
  • Validate document format, page size and orientation before creating the job.
  • Record job identifiers and failure reasons for support and monitoring.

Next steps

Guides for integrating CloudPrint, connecting the local agent and operating print workflows.