What is SBPL?

SBPL (SATO Barcode Printer Language) is the command language of SATO label printers — the CL4NX/CL6NX and S84NX/S86NX lines, the older GL4xxe, and other SBPL-speaking models. Like ZPL for Zebras and DPL for Datamax printers, SBPL is how applications tell a SATO printer what to draw.

What it looks like

<ESC>A
<ESC>H0001<ESC>V0100<ESC>WB1LabelZoom
<ESC>H0130<ESC>V0200<ESC>B103150*12345678*
<ESC>H0170<ESC>V0360<ESC>L0202<ESC>S12345678
<ESC>Q1
<ESC>Z

Every command begins with an ESC character (0x1B). <ESC>A opens a print job and <ESC>Z closes it; in a real stream the commands run together as one continuous sequence of bytes, split onto separate lines here only for readability.

Inside the job, H and V set the horizontal and vertical print position in dots, and the command that follows draws something at that position: WB1 selects a smoothing font and prints the text after it, B1 draws a bar code, and S prints in a resident bitmap font. Modifiers are sticky — L0202 doubles character expansion for everything after it until it is changed again — which is the main thing that makes SBPL harder to read by eye than ZPL. Q1 sets how many copies to print.

SBPL vs ZPL

	SBPL	ZPL
Hardware	SATO CL4NX/CL6NX, S84NX/S86NX, GL4xxe	Zebra (and much else via emulation)
Command prefix	`ESC` (`0x1B`) before every command	`^` or `~`
Positioning	Separate `H` and `V` commands, sticky	One `^FO`/`^FT` per field
Modifiers	Sticky state — rotation, expansion, pitch persist	Mostly per-field

Both languages describe a complete label in a single stream, so they map onto each other cleanly. The practical difference is the sticky state machine: in ZPL a field carries its own formatting, while in SBPL the formatting is whatever the preceding commands last set it to. A converter has to track that running state to place fields correctly.

Working with SBPL files

SBPL files are plain text apart from the ESC control characters, so they usually open readably in a text editor. The LabelZoom conversion engine parses SBPL natively — rendering SBPL labels to images and PDF the same way it renders ZPL. The REST API converts SBPL in both directions — sbpl is a source and a target (e.g. POST /api/v2/convert/sbpl/to/pdf or POST /api/v2/convert/zpl/to/sbpl); see Supported formats and the API quickstart. If you’re migrating SATO labels to other hardware or need SBPL rendered for verification, contact us.