How do I install Web Print Expert on Kylin or UnionTech UOS?

Download the Linux deb from the official site. On Kylin or UOS desktops you can usually double-click to install, or run sudo dpkg -i. Launch the client and complete initial setup.

Can Linux and Windows share the same front-end print code?

Yes. Windows and Linux clients expose the same WebSocket API (/websocket/standard). Your web-print-pdf front-end code stays platform-agnostic for mixed domestic OS and office PC deployments.

What permissions are required to install the deb package?

Installing the deb requires root (e.g. sudo dpkg -i). Day-to-day client use can run as a normal user. HTML-to-PDF runs locally and works on offline intranets.

Linux & domestic OS deployment

Deploy the Web Print Expert client on Kylin, UOS, Ubuntu, Debian, and more; integrate web-print-pdf for web printing and HTML to PDF.

Platform editions

Edition	Platform	Print backend	Installer
Windows	Windows 10/11	Built-in silent print engine	`.exe` installer
Linux	x64 / arm64	System print service	`.deb` / `.rpm`
macOS	macOS 11+	CUPS	`.dmg`

Windows and Linux ship as separate installers but share the same WebSocket API (/websocket/standard)—front-end code stays platform-agnostic.

End-user deb install

Download the Linux deb from the download page.
On Kylin / UOS: double-click the deb or run sudo dpkg -i.
Launch the client, complete setup, and verify the local print service.
npm install web-print-pdf—same APIs as on Windows.

# CLI install example
sudo dpkg -i WebPrintExpert_*_amd64.deb
sudo apt-get install -f    # fix dependencies

# Launch (from menu or CLI after install)

Item	Description
Install method	Double-click deb or `dpkg -i`
Install location	System applications folder (configured by the package)
Launch	Desktop menu “Web Print Expert” or app shortcut
Architecture	Separate deb packages for x64 / amd64 and arm64

System dependencies (deb)

The Linux installer declares runtime dependencies, typically including:

System print client libraries — required for silent printing on Linux
GUI and font rendering runtime libraries
Install common CJK font packages to avoid missing glyphs in PDF or print output

If print services or system libraries are missing, the client opens an in-app guide—no Node.js required for end users.

Building Linux packages (advanced)

For custom builds: obtain the project sources and follow the bundled packaging guide.

# Typical flow (see project docs for exact commands)
1. Install build deps and frontend toolchain
2. Clone source and install project dependencies
3. Run Linux packaging (deb / rpm)
4. Install and verify on target system

Typical steps: prepare front-end assets → verify layout engine and system libs → produce deb/rpm packages.

RPM builds need extra system packaging tools; see the project documentation for commands.

Cross-platform print overview

HTML→PDF uses the client’s built-in layout engine; output is handed to each platform’s print stack:

Windows: client silent print engine → system print queue
Linux: system print service for silent output

Front-end still passes printOptions.printerName; printer lists are normalized by the client API.

Notes

Share one front-end print codebase across Linux and Windows endpoints.
deb install needs root; runtime can use a normal user.
Works offline on intranet; PDF generation is local.
Linux clients support updates via architecture-specific update descriptors.

Download client free Documentation