Developer Hub & Open Specifications

The open print protocol for modern thermal printers.

Connect web applications, ERPs, and warehouse management systems directly to local thermal printers over WebSocket. Zero JVM overhead, zero per-printer license fees, and an open, fully resolved document schema.

Why renderers shouldn't measure text

Traditional print architectures force printers or local spoolers to calculate line breaks, evaluate dynamic expressions, and guess layout based on local OS font metrics. This causes margin drift, clipped text, and inconsistent barcodes across operating systems.

Fully Resolved Geometry (BLPD)

BLPD (BrioLabel Print Document) strictly separates layout calculation from physical rendering:

  • Every node has explicit millimeter X/Y/width/height frames pre-calculated by the generator.
  • A renderer never measures text, wraps lines, shrinks fonts, or evaluates dynamic expressions.
  • The renderer simply streams native raster, ZPL, TSPL, or Brother commands directly to the hardware.
  • The exact same document renders identically across every supported printer brand.

WebSocket Agent Protocol

Connect from any client (browser JS, Node.js, Python, curl) to the local Desktop Agent over secure WebSocket.

JavaScript — Browser / Client to Desktop Agent// Connect to the local BrioLabel Desktop Agent over WebSocket const socket = new WebSocket("wss://localhost:9443/agent"); socket.onopen = () => { // Dispatch a print job containing a fully resolved BLPD payload socket.send(JSON.stringify({ action: "print", printerId: "Zebra_ZD421_USB", copies: 1, document: blpdPayload })); }; socket.onmessage = (event) => { const response = JSON.parse(event.data); console.log("Print job status:", response.status); // "success" | "queued" | "error" };
BLPD — Fully Resolved Document Payload (JSON){ "specVersion": "1.0", "document": { "unit": "mm", "pages": [ { "width": 101.6, "height": 152.4, "layers": [ { "id": "label_content", "nodes": [ { "type": "text", "frame": { "x": 10, "y": 10, "width": 80, "height": 12 }, "text": "SKU-98421-BL", "style": { "font": { "family": "IBM Plex Mono", "size": 14, "weight": 600 }, "color": "#000000" } }, { "type": "barcode", "frame": { "x": 10, "y": 28, "width": 81.6, "height": 28 }, "data": "98421002345", "symbology": "code128" }, { "type": "qrcode", "frame": { "x": 10, "y": 62, "width": 25, "height": 25 }, "data": "https://verify.example.com/item/98421", "errorCorrection": "M" } ] } ] } ] } }

Lightweight native performance vs QZ Tray

Why engineering teams are replacing legacy Java-based print utilities:

Native Go/C binary (~3 MB download) vs 100+ MB Java runtime bundle
Single-digit MB idle RAM vs 100+ MB JVM memory footprint
Cryptographic origin pairing — no need to purchase expensive $500+/yr code-signing certificates for silent printing
Open BLPD specification — no vendor lock-in

Evaluating an alternative to QZ Tray?

See full runtime memory benchmarks, certificate requirements, and licensing comparisons.

Compare with QZ Tray →

Build on open thermal printing.

Explore the open specification or download the free reference Desktop Agent.