Windows 10 and 11 supported?
Yes—use the current exe from the official download page for your supported Windows release.
Windows deployment & integration guide
Deploy the Web Print Expert client on Windows 10/11 (office PCs, POS, warehouse stations) and integrate web-print-pdf for silent HTML-to-PDF printing. Same API as macOS and Linux/domestic clients for mixed fleets.
Three-client comparison
| 版本 | 平台 | 打印后端 | 安装包 |
|---|---|---|---|
| Windows 版 | Windows 10/11 | 内置静默打印引擎 | .exe |
| Linux 版 | x64 / arm64 | 系统标准打印服务 | .deb / .rpm |
| macOS 版 | macOS 11+ | CUPS | .dmg |
Official Windows, macOS, and Linux clients use different installers but expose the same WebSocket API (/websocket/standard)—front-end code needs no platform branches.
Install steps (exe)
- Download the Windows exe from the download page
- Run the installer and launch Web Print Expert from the Start menu
- Confirm the service is running (tray icon / main window shows WebSocket ready)
npm install web-print-pdf—same API as Mac/Linux
Firewall & WebSocket troubleshooting
The client listens on 127.0.0.1; the npm package connects from the browser. If connection fails:
- Ensure the client is running
- Allow the app through Windows Firewall (private/public on first launch)
- Check security software blocking local WebSocket
- Preflight with
getConnectStatus()—see error handling guide
Front-end integration
Browser pages on Windows use the same npm package as Mac/Linux:
npm install web-print-pdfimport webPrintPdf from 'web-print-pdf';
await webPrintPdf.printHtml(
'<h1>Hello Windows</h1>',
{ paperFormat: 'A4', printBackground: true },
{ printerName: '默认打印机' }
);Service URL: ws://127.0.0.1:{port}/websocket/standard—port shown in the client UI; web-print-pdf auto-connects by default.
Deployment notes
- Share one front-end print codebase across Windows and Linux/domestic desktops.
- Silent print uses the built-in client engine—no browser print dialog.
- Multi-printer sites: set
printOptions.printerName; enumerate printers via client APIs.
FAQ
Browser cannot connect to the client?
Start the client first; check firewall and security software; use getConnectStatus. See the error handling guide if needed.
Same front-end as Mac and domestic Linux?
Yes—shared web-print-pdf API; only the desktop installer differs per OS.
Need admin rights?
Installing the exe may require elevation; day-to-day printing usually does not need ongoing admin.
Client deployment by platform
The same web-print-pdf front-end runs on Windows, macOS, and Linux/domestic OS—install the matching client on each desktop.