EvoPdf.HtmlToPdf.MacOS 15.0.1

EVO HTML to PDF Library for .NET (Classic API on the Next Engine, macOS ARM64)

HTML to PDF for .NET | PDF Library for .NET and C# | Free Trial | Licensing | Support

Overview

EVO HTML to PDF Library for .NET (Classic API on the Next Engine, macOS ARM64) runs the Classic EvoPdf API on the Chromium-based rendering engine of EvoPdf Next. It converts HTML to PDF and creates PDF documents in .NET applications on macOS ARM64 with the EvoPdf namespace (EvoPdf.HtmlToPdfConverter, EvoPdf.Document, EvoPdf.PdfPage, the elements, templates, forms, bookmarks and security settings) and renders modern HTML, CSS and JavaScript as EvoPdf Next does, to the latest standards.

An application written for the EvoPdf.HtmlToPdf package keeps its code and changes only the package reference. The pages render as in Chromium, with the options of the EvoPdf API; the options specific to the Classic rendering engine are accepted and have no effect.

Package structure

This package references the library of the EvoPdf API and the EvoPdf.Next.HtmlToPdf.MacOS package, which brings the rendering engine for macOS ARM64.

The same library is available for the other platforms in the packages below, which can be referenced on their own or alongside this package:

• EvoPdf.HtmlToPdf.Windows (Windows x64)
• EvoPdf.HtmlToPdf.Windows.Arm64 (Windows ARM64)
• EvoPdf.HtmlToPdf.Linux (Linux x64)
• EvoPdf.HtmlToPdf.Linux.Arm64 (Linux ARM64)
• EvoPdf.HtmlToPdf.MacOS (macOS ARM64)

Compatibility

• macOS Ventura or later on Apple Silicon
• .NET 10.0, 9.0, 8.0, 7.0, 6.0 and .NET Standard 2.0
• Web, Console and Desktop applications

Main Features

• Create PDF documents from HTML with advanced support for CSS3, SVG, Web Fonts and JavaScript
• Automatically create PDF links, forms, bookmarks and table of contents from HTML tags
• Place the content from multiple HTML documents at any position in PDF pages, headers or footers
• Create JPEG, PNG and Bitmap raster images from HTML documents
• Create SVG images from HTML documents
• Create PDF documents with text, graphics, images, headers and footers
• Create PDF documents with security features and digital signatures
• Create interactive PDF documents with forms, internal links, text notes and JavaScript actions
• Edit, stamp and merge PDF documents

Installation

Install the package using your preferred NuGet package manager or with the .NET CLI:

dotnet add package EvoPdf.HtmlToPdf.MacOS

On macOS the rendering engine does not require the installation of additional dependencies. The fonts and images created from System.Drawing objects need libgdiplus, installed with Homebrew (brew install mono-libgdiplus); the fonts created from a file, from font data or from a standard font and the images given by file path do not use it. On Apple Silicon .NET does not look in the Homebrew folder, so the library is linked in the folder of the application (the build output or the publish folder): ln -s /opt/homebrew/lib/libgdiplus.dylib libgdiplus.dylib.

Getting Started

The code written for the EvoPdf.HtmlToPdf package runs as it is. To convert a web page or an HTML string to a PDF document:

using EvoPdf;

HtmlToPdfConverter converter = new HtmlToPdfConverter();
converter.LicenseKey = "your-license-key";

byte[] pdfBytes = converter.ConvertUrl("https://www.evopdf.com");
System.IO.File.WriteAllBytes("url_to_pdf.pdf", pdfBytes);

EvoPdf Next features in the existing code

Each converter raises the NextConverterCreated event before a conversion, with the EvoPdf Next converter it uses, for the options the EvoPdf API has no setting for, such as the PDF standard; its Next property holds the converter of the last conversion. The results are plain PDF data, so the EvoPdf API and the EvoPdf Next API can be used together in the same application.

For new applications, the EvoPdf Next HTML to PDF Converter offers the native API of the new engine.

Licensing

The EVO PDF Software licenses are perpetual which means they never expire for a version of the product and include free maintenance for the first year. You can find more details about licensing on the website.

Set the license key on the converter object before the conversion:

converter.LicenseKey = "your-license-key";

Without a license key the converter runs in evaluation mode and a demo watermark is displayed in the generated PDF documents.

Support

For technical and sales questions or for general inquiries about our software and company you can contact us using the email addresses from the contact page of the website.