Is silent print the same as no-preview print?
In practice, yes—no browser preview/confirm dialog; jobs go straight to the printer. That usually requires a local client or print control.
Silent printing — complete guide
Teams searching for silent print, no-preview printing, or web printing usually need: no browser dialog, a named printer, and batch labels/reports. This pillar page explains the principle, common routes, and a decision table into our 38+ topic guides—read by scenario instead of comparing everything from scratch.
Why pure front-end JavaScript cannot silent-print
Browsers require user confirmation for window.print(). Page scripts cannot bypass the system print dialog to a named printer. Production silent output needs a local client, print control, or extension.
- window.print / Print.js / react-to-print: often still use the browser dialog
- Lodop / C-Lodop: common in legacy intranet overlay stacks
- hiprint / electron-hiprint: Vue visual template designer ecosystem
- web-print-pdf + local client: HTML/CSS → PDF → silent output, one npm API on Win/Mac/Linux/domestic OS
Recommended architecture (HTML admin apps)
The page sends jobs over WebSocket to the Web Print Expert desktop client, which renders PDF and prints silently. Front-end: npm install web-print-pdf and printHtml. Details: web printing & window.print alternative.
- Install and run the client on each desk
- Add
web-print-pdfto your project - Pass print-area HTML and
printOptions - Client prints locally—no browser dialog
Pick a topic cluster
Deep dives live in existing topic pages—this guide routes you there without adding hub cards.
| Your scenario | Read next | Notes |
|---|---|---|
| Upgrade from window.print | Web & browser printing | Dialog limits & migration |
| Lodop overlays / C-Lodop | Lodop comparison · C-Lodop & Chrome | Parallel evaluation |
| hiprint / electron-hiprint | hiprint comparison | Designer vs HTML reports |
| Print.js / react-to-print | Print.js comparison | When you need a client |
| PDF file vs physical printer | HTML to PDF & print | jsPDF vs printHtml roles |
| Vue / React / Next.js | Vue · React · Next.js | Framework guides |
| Shipping labels / WMS | E-commerce labels · WMS remote · Receipts | Silent batch |
| Win / Mac / Kylin / UOS | Windows · macOS · Linux · Kylin · UOS | Client deploy |
Quick decision table
| If you need… | Start here |
|---|---|
| Manual confirm each job | window.print / Print.js |
| Silent + named printer + HTML | Client + printHtml (architecture above) |
| Legacy Lodop overlays | Lodop comparison; PoC web-print-pdf for new modules |
| Vue drag designer estate | hiprint / electron-hiprint |
| PDF export only | jsPDF or Puppeteer archive |
| Server push, desk auto-print | WMS remote print |
FAQ
Can an npm package alone silent-print?
Not end-to-end. web-print-pdf needs the Web Print Expert client; Print.js and react-to-print still rely on the browser dialog in most setups.
Must we replace Lodop?
No one-size-fits-all. Keep Lodop for precision overlays; evaluate web-print-pdf in parallel for new HTML/Vue/React modules.
Domestic OS (Kylin/UOS)?
Yes—official Linux deb client shares the same printHtml API as Windows exe and macOS dmg.
What to read next?
Follow the cluster table; for hands-on integration start with Vue or React and install the client.
Notice
Technical selection reference only. Third-party names are for identification; trademarks belong to their owners.
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.