JSPrintManager vs WebClientPrint: Which Web Printing Tool Is Right for You?

Short answer: choose JSPrintManager

JSPrintManager is our actively developed client-side printing solution. It is a JavaScript library that works with any web platform (ASP.NET, PHP, Django, Rails, Node.js, Angular, React…), and JSPrintManager for Blazor brings the same features to Blazor Server & WebAssembly in C#. Besides printing raw commands and files, it adds scanning, BIDI communication with serial, TCP/IP, Bluetooth, USB & HID devices, print job tracing, a printers watcher, white label, kiosk mode and mobile support.

WebClientPrint for ASP.NET and for PHP is in maintenance mode: version 6.0 remains available for existing projects, but no new major versions are planned. See how to migrate from WebClientPrint.


JS Print Manager
Recommended


JS Print Manager for Blazor
Recommended for Blazor


WebClientPrint for ASP.NET
Maintenance mode


WebClientPrint for PHP
Maintenance mode

PRODUCT STATUS
Development  Actively developed Maintenance mode (v6.0). No new major versions planned.
Where the print job is created In the browser (JavaScript) or in Blazor C# code; data can come from any backend On the server (.NET assembly or WebClientPrint.php)
DEVELOPMENT SIDE
Web Platforms
  • Any Web Platforms including:
    • ASP.NET Core, MVC & WebForms
    • PHP
    • Django
    • Ruby On Rails (RoR)
    • Express.js
    • Angular
    • React
  • Blazor Server
  • Blazor WebAssembly
  • ASP.NET Core, MVC & WebForms
  • PHP
Dependencies
  • WebSockets
  • .NET 5.0+
  • ASP.NET 4.6.1+ or ASP.NET Core 2.0+
  • System .Text .Encoding .CodePages 4.6.0+
  • PHP 5.3+
  • phpseclib 1.0+
Programming Languages
  • Javascript
  • C#
  • Javascript
  • C# / VB.NET
  • Javascript
  • PHP
CLIENT SIDE
White Label / Custom Brand  Supported  Not supported
Web Browsers
  • Chrome 31+
  • Firefox 31+
  • Internet Explorer 10+
  • Edge
  • Safari 6.0.3+
  • Chrome 11+
  • Firefox 2+
  • Internet Explorer 6+
  • Edge
  • Safari 3+
OSes Windows, Linux, macOS/OSX & Raspbian (Linux ARM)
Mobile & Sandboxed Devices Support Yes, can be configured to print from iOS, Android, ChromeOS, etc.  Not supported
Windows Kiosk Mode  Supported  Not supported
Client App Type Local TCP Listener URL Protocol
Client App Dependencies None! Native App for each client OS.
 No ActiveX,  No Flash,  No Silverlight,  No Java,  No .NET Framework
FEATURES
Print Raw Commands  Supported  Supported
Print Files & Images  Supported  Supported
Print Password Protected Files  Supported  Supported
Print Encrypted Files  Supported  Supported
Scan Docs & Images  Supported  Not supported
BIDI Serial Comm  Supported  Not supported
BIDI TCP/IP Comm  Supported  Not supported
BIDI Bluetooth Comm  Supported  Not supported
BIDI USB Comm  Supported  Not supported
BIDI HID Comm  Supported  Not supported
BIDI IPP Comm  Supported  Not supported
Print Job Status & Tracing  Supported  Not supported
Printers Watcher  Supported  Not supported

Explore JSPrintManager Download free trial


JSPrintManager vs WebClientPrint FAQ

Should I use JSPrintManager or WebClientPrint?
For new projects use JSPrintManager (or JSPrintManager for Blazor). It is actively developed, works with any web platform and covers everything WebClientPrint does. WebClientPrint for ASP.NET and for PHP are in maintenance mode: version 6.0 remains available for existing projects, but no new major versions are planned.
Which web platforms does JSPrintManager support?
Any web platform, because it is a JavaScript library: ASP.NET Core, MVC and WebForms, PHP, Django, Ruby on Rails, Express.js, Angular, React and others. JSPrintManager for Blazor targets Blazor Server and WebAssembly with a C# API.
What can JSPrintManager do that WebClientPrint cannot?
JSPrintManager adds scanning documents and images, bidirectional (BIDI) communication with serial, TCP/IP, Bluetooth, USB and HID devices, print job status tracing, a printers watcher, white-label/custom branding, Windows kiosk mode, and printing from mobile and sandboxed devices such as iOS, Android and ChromeOS.
What do both products have in common?
Both send raw printer commands (ZPL, EPL, ESC/POS, PCL, PostScript and more) and files (PDF, images, TXT, DOC, XLS, including password-protected and encrypted files) to printers installed on the client machine without a print dialog, on Windows, Linux, macOS and Raspberry Pi clients, with a native client app and no browser plugins.
How do I migrate from WebClientPrint to JSPrintManager?
Create the print job in JavaScript with JSPM.ClientPrintJob instead of on the server, using the same printer classes (DefaultPrinter, InstalledPrinter, NetworkPrinter, etc.) and file classes (PrintFilePDF, PrintFileTXT, etc.). Your ASP.NET or PHP backend can keep generating the commands or files, and client machines install the JSPrintManager Client App instead of WCPP.