Thermalink

How to print to a thermal receipt printer from a web app without the print dialog

Every way I know to do it in 2026, what each one costs, and where each one breaks. Prices checked on 20 November 2026.

The short answer

A web page cannot send bytes to a printer on its own. window.print() always goes through the browser's print dialog, and the browser does not let a page skip it. To print silently you need one of three things: a browser started with a special flag, direct device access (WebUSB or Web Serial), or a small program on the computer that the page talks to. That last one is what most POS web apps end up using.

OptionSilentCut / drawerBrowsersCostGood for
Chrome --kiosk-printingYes, to the default printerOnly what the driver doesChrome / Edge, per computerFreeOne till you set up yourself
WebUSB / Web SerialYesYes, you write the bytesChromium onlyFreeKiosks you fully control
QZ TrayYesYes, you write the bytesAllFree (LGPL); $749/year Premium Support with trusted certificateTeams that want a mature open-source agent
PrintNodeYes, through their cloudRaw jobs supportedAny (server-side API)Free for 50 prints/month; $9 to $99/monthPrinting from your server to many sites
Thermalink (mine)YesYes, from JSONAll modern$49 one-timeWeb POS apps that want receipt layout done for them
Write your own agentYesYesAllYour timeTeams with time and one printer model

1. Chrome with --kiosk-printing

Start Chrome or Edge with --kiosk-printing (often together with --kiosk) and window.print() goes straight to the default printer with no preview. Shops and shipping tools document this for one-click label printing, for example SKULabs' Windows guide.

Where it breaks: it is set per computer, on the shortcut, so every till needs the change and it is lost when someone opens Chrome another way. It always uses the default printer, so a receipt printer and a label printer on one PC is awkward. Layout still goes through CSS and the driver, which on thermal paper is its own fight (see why @page { size: 80mm auto } does nothing in Chrome). There is also an old Chromium report of the flag being ignored without --kiosk, so test it on your Chrome version.

2. WebUSB or Web Serial

The page talks to the printer directly and sends ESC/POS bytes, so cut, cash drawer and QR codes all work. No install.

Where it breaks: Chromium browsers only (no Firefox, no Safari). The user has to pick the device once. On Windows, a USB printer with its normal driver is already claimed by the system, and WebUSB gets Access denied; I wrote up who holds the device and the three workarounds. Every workaround stops the printer working with normal Windows printing. Network printers on port 9100 are out of reach.

3. QZ Tray

The best-known option, and a good one. A desktop agent that the page talks to over a local WebSocket. It sends raw ESC/POS, ZPL and EPL, and prints PDFs, images and HTML. qz.io says the source is LGPL, that it is free to download and use, and that all versions can be used in commercial software.

The paid part: Premium Support is $749 a year (annual renewal at a reduced rate) and Company Branded is $3,499 a year, both per qz.io on 20 November 2026. Premium includes the trusted dialog certificate and message signing, which is what makes printing from your site stop asking the user for permission. Without it you use community support and self-signed keys.

Things to know: it ships with its own Java runtime, and you build the printer bytes yourself (or with a library), so receipt layout, column widths and code pages are still your job.

4. PrintNode

A different design: you install their client on the shop computer, and your server sends print jobs through PrintNode's cloud API. Nothing runs in the browser. Their pricing page on 20 November 2026: Lite free (50 prints a month, 1 computer), Essential $9/month (5,000 prints, 3 computers), Standard $29/month (25,000 prints, 5 computers), Premium $99/month (200,000 prints, unlimited computers), with yearly plans and integrator accounts too.

Good when the print is triggered from your back end (an online order printing in the kitchen). The cost grows with prints and computers, and jobs go through a third party and the internet, so printing stops when the shop's connection does.

I built Thermalink because I wanted the QZ Tray model without the yearly fee and without writing ESC/POS by hand. It is a single small Go program that runs on the shop computer and listens on 127.0.0.1, plus an 8 KB JavaScript SDK. You send the receipt as JSON (rows, columns, QR, barcode, logo, cut, drawer) and the agent draws it as an image at the printer's real width, so it looks the same on every brand and does not depend on code pages.

const tl = new Thermalink();
await tl.print(
  Thermalink.receipt()
    .title('BLUE DOOR CAFE')
    .row('Flat white x2', '8.00')
    .row('TOTAL', '8.00', { bold: true })
    .cut()
);

$49 one-time for one app, $149 for all your apps and client projects, Go source included. Honest limits: it has been tested end to end on one real printer (a BIXOLON SRP-352plusIII on Windows 11); other ESC/POS printers use the same commands but have not each been tested; the macOS and Linux builds have not been hardware-tested; the binaries are not code-signed. The compatibility page has the details.

6. Write your own small agent

Perfectly doable if you have one printer model: a local HTTP server that accepts bytes and writes them to the printer (RAW to the Windows spooler, port 9100 for network printers, lp -o raw on macOS and Linux). The parts that take the time are the ones around it: which websites may print, raster images for logos and non-Latin text, paper width per printer, and the browser permission prompt below. The free ESC/POS, ZPL and TSPL cheat sheet has the bytes.

One thing that affects every local agent: Chrome's local network prompt

Since Chrome 142 (and Firefox 153), a public website that calls a program on localhost triggers a permission prompt. Until the user clicks Allow, requests just hang, which looks exactly like "the agent is not installed". This applies to QZ Tray, Thermalink and anything you write yourself. The troubleshooting page covers how to detect it and the policy that pre-allows your site on managed computers, and I tested it in detail in this write-up.

What I would pick

Just want window.print() receipts to come out the right size? The Receipt Print Kit ($9) has the stylesheet and eight templates for 58 mm and 80 mm.

Prices and facts checked on 20 November 2026 from the linked pages. Corrections welcome.