Rasterization changes output
Converting a thermal label to an image or PDF can alter size, density, and barcode edges.
Raw printer languages
Keep ZPL, EPL, and ESC/POS raw all the way to the queue.
Base64-encode the commands and send raw_base64. RocketPrint Station writes the decoded bytes to the local queue instead of treating them as a document.
No render step
The target printer interprets the language it was built to understand.
The operational gap
Printer-native content loses its advantage when something redraws it.
Thermal and receipt printers are fast and precise because they execute compact command languages directly.
Text is not commands
Sending ZPL through a normal document path can print the source instead of executing it.
Drivers add variables
A raw queue path avoids extra layout decisions in an operating-system renderer.
The RocketPrint path
Declare raw content explicitly.
The content type tells RocketPrint Station whether to send bytes directly or invoke the installed document-printing path.
Generate commands
Use the carrier response, receipt template, or command generator that already produces the printer language.
Encode for JSON
Base64-encode the exact bytes and set contentType to raw_base64.
Target a compatible queue
Choose the printer ID for the thermal or receipt device that understands those commands.
What changes
Fewer transformations between source and paper.
Barcode fidelity
The thermal printer draws barcodes at its native resolution.
Compact payloads
Command languages stay small compared with rendered page images.
Mixed fleet support
Raw jobs and PDF jobs still use the same RocketPrint job endpoint.
Explicit compatibility
The application remains responsible for matching a language to a printer that supports it.
Start with one printer
Make the physical step part of the workflow.
Install RocketPrint Station beside a printer, send one request, and keep the job ID. That is the whole path.