EvoPdf Classic · .NET client library

Cross-Platform PDF Library for .NET

The EVO PDF Client Library for .NET packs the Classic HTML to PDF, Word to PDF, Excel to PDF, PDF to Text, PDF to Image, PDF to HTML and PDF Images Extractor components into one assembly with the same API as the regular libraries, except that the conversions run on an EVO PDF Server. That is what lets it work anywhere .NET runs: Windows, Linux, macOS, Azure App Service, Azure Functions and UWP.

Download .NET client Download EVO PDF Server Download Server New Edition Documentation

Classic v14.0: Any platform, through the EVO PDF Server. Evaluate without registration; the demo output is watermarked until you set a license key. Licensed with the HTML to PDF Converter license or the EVO PDF Toolkit.

$dotnet add package EvoPdf.Client

Any platform with .NET Framework 4.0+ or .NET Standard 2.0 (.NET 6–10): the conversions run on an EVO PDF Server, on Windows

Program.csC#

using EvoPdfClient;

// conversions run on the EVO PDF Server
var converter = new HtmlToPdfConverter(
    "server.mycompany.com", 40000);
byte[] pdf = converter.ConvertUrl(
    "https://www.evopdf.com");

Classic API: EvoPdfClient namespace, one converter class, synchronous calls. API reference →

Windows, Linux and macOS
.NET Framework 4.0 – 4.8.1
.NET 6 → 10, .NET Standard 2.0
Azure App Service, Cloud Services & Virtual Machines
UWP, web, console and desktop applications

How it works

Same API, conversions on the server

Your application

References EvoPdf.Client, targets .NET Framework 4.0+ or .NET Standard 2.0 and calls the same converter classes you know from the Classic library: HtmlToPdfConverter, WordToPdfConverter and the rest, under the EvoPdfClient namespace.

EVO PDF Server

A Windows service that hosts the rendering engine. Install it once, on any Windows machine or VM the clients can reach; it is available in the original edition and in the New Edition, with the newer engine.

The PDF comes back

The client sends the HTML, Word or Excel input to the server and receives the PDF bytes: the application never needs a rendering engine of its own, which is exactly what restrictive platforms require.

In detail

How Cross-Platform PDF Library for .NET works

The client library exists for the cases the Classic library cannot cover directly: applications that must run on Linux or macOS, in Azure App Service or Azure Functions, in UWP, or anywhere a native Windows rendering engine cannot be loaded. It keeps the features, quality and API of the Classic components: HTML5, CSS3, JavaScript, SVG and web fonts, page breaks controlled from CSS or from the API, repeated table headers and footers, live and internal links, automatic bookmarks and tables of contents, fillable PDF forms, digital signatures and password protection, while the rendering happens on the EVO PDF Server.

Compatibility: any platform with .NET Standard 2.0 and above (.NET 6 to 10) or .NET Framework 4.0 and above; Windows, Linux and macOS; Azure, Azure App Service and Azure Functions; UWP; web, console and desktop applications.

The evaluation package contains the client assembly and demo projects with full C# code for .NET Framework and .NET Core, one per component. Before running them, install the EVO PDF Server (original or New Edition) on a machine the demo can reach and point the client at its address and port.

The same license covers the client library and the server.

At a glance

Component: EvoPdf Classic · .NET client library
NuGet package: EvoPdf.Client
Namespace: EvoPdfClient
Main class: HtmlToPdfConverter
Runs on: Any platform with .NET 6–10 or .NET Framework 4.0+; the EVO PDF Server runs on Windows, locally or on a remote machine with remote access enabled
Version: Classic v14.0
License: HTML to PDF Converter license or EVO PDF Toolkit; evaluation without registration

Documentation →

Installation

Install and run on Windows

The client assembly runs wherever .NET runs: .NET Framework 4.0+, .NET 6–10, including UWP applications and Azure App Service; install the EVO PDF Server (original or New Edition) on a Windows machine the clients can reach and point them at its address and port. For a single-package alternative on Linux and macOS, see EvoPdf Next.

Documentation

API reference and usage notes for the .NET client library component.

Open the docs →

Getting started

Install the EVO PDF Server on a Windows machine the clients can reach. Allow remote connections when the server is on another machine, then set the server address and port in the client.

Server installation guide →

Moving to Next?

EvoPdf Classic is the original engine, fully supported and licensed alongside EvoPdf Next. New projects should start with Next: Chromium rendering, Windows, Linux and macOS.

Migration guide →

UWP and Azure App Service

The .NET Standard 2.0 build of the client library also runs in Universal Windows Platform (UWP) applications and in Azure App Service, sending the HTML to an EVO PDF Server for rendering. Azure App Service is supported natively by EvoPdf Next on Windows, without a server; UWP is not supported by EvoPdf Next.

Licensing

Perpetual licenses, with a year of updates and support

The HTML to PDF Converter license (450 USD Deployment / 1200 USD Company) covers the Classic and the Next converter; the EVO PDF Toolkit (650 / 1400 USD) covers every component on this site, Classic tools included. The Company License includes redistribution.

Pricing & licensing EvoPdf Next All downloads