Chrome PDF Rendering Engine
Published: 2022-01-26 08:03:52

---
canonical_url: https://ironpdf.com/docs/questions/ironpdf-2021-chrome-rendering-engine-eap/
---

The Iron Software engineering team is proud to release a game-changing upgrade to IronPDF in 2021, now featuring **“Chrome Identical” PDF rendering**.

[Download the latest version free](https://www.nuget.org/packages/IronPdf/) to add high-grade rendering in your projects and read the instructions below to implement.

`PM > Install-Package IronPdf`

---

## High-Quality Improvements, Well Tested

### High-Quality Rendering

The latest “Blink!” HTML rendering. Choose from **Chrome Identical rendering** or Enhanced Rendering (which we find more accurate and easy to code for than Chrome.)

### 20% Faster Renders

Provides effortless multithreading and Async, using as many CPU cores as you wish. For SAAS and high-load applications this may be **5-20 times faster**, outperforming direct browser usage and web-drivers.

### Full Support

Full (and we mean full) support for **JavaScript**, **responsive** layout and **CSS3**.
**Azure** as a first class citizen. It just works.
Continued maintenance and improved full support for .NET 5, Core, and Framework 4.0+.

### Rigorously Tested

The release passed with **1156 green unit & integration tests** (and no red ones). We believe this EAP to be as stable as our main release, and has our best minds actively improving it every day.

### Section 508 Accessibility Compliance

Produces accessible PDFs using the PDF(UA) tagged PDF standard.

### Ongoing Improvements

We would love to hear your feedback. Contact developers@ironsoftware.com with ideas or if you need any help getting things running.

---

**Implement in Your Project**

## 1. Implement the Code in Your Project

### 1.1. Step 1 - Update IronPdf

First you must install IronPDF into your project from the Nuget Package Manager named `IronPdf`.

`PM > Install-Package IronPdf`

This is essential.

### 1.2. Step 2 - Upgrade with 1 line of code

Changing to the new renderer at a global level is simple. This approach updates all usages of your existing _ChromePdfRenderer_ and _AspxToPdf_ code.

Just do this once, before you render any pdfs and you have switched to the new renderer.

**C#:**
```
IronPdf.Installation.DefaultRenderingEngine = IronPdf.Rendering.PdfRenderingEngine.Chrome;
```

**VB:**
```
IronPdf.Installation.DefaultRenderingEngine = IronPdf.Rendering.PdfRenderingEngine.Chrome
```

---

## 2. Try the new API

We haven’t broken the previous IronPDF C# and VB.NET API you are already using. It will remain! However, the old style is being superseded by a better one to give you more control.

For example, you now have RenderingOptions and HttpLoginCredentials specific to your renderer.

**C#:**
```
using IronPdf;
ChromePdfRenderer Renderer = new ChromePdfRenderer();
Renderer.RenderingOptions.FitToPaper = true;
Renderer.RenderingOptions.CssMediaType = IronPdf.Rendering.PdfCssMediaType.Screen;
Renderer.RenderingOptions.PrintHtmlBackgrounds = true;
Renderer.RenderingOptions.CreatePdfFormsFromHtml = true;
var doc = Renderer.RenderHtmlAsPdf("<h1>Hello world!</h1>");
// var doc = Renderer.RenderUrlAsPdf("https://www.google.com/");
// var doc = Renderer.RenderHtmlFileAsPdf("example.html");
doc.SaveAs("google_chrome.pdf");
```

**VB:**
```
Imports IronPdf
Private Renderer As New ChromePdfRenderer()
Renderer.RenderingOptions.FitToPaper = True
Renderer.RenderingOptions.CssMediaType = IronPdf.Rendering.PdfCssMediaType.Screen
Renderer.RenderingOptions.PrintHtmlBackgrounds = True
Renderer.RenderingOptions.CreatePdfFormsFromHtml = True
Dim doc = Renderer.RenderHtmlAsPdf("<h1>Hello world!</h1>")
' var doc = Renderer.RenderUrlAsPdf("https://www.google.com/");
' var doc = Renderer.RenderHtmlFileAsPdf("example.html");
doc.SaveAs("google_chrome.pdf")
```

## 3. Apply Pixel-Perfect Chrome Rendering

This example will give you PDFs that are pixel-perfect to the latest Chrome desktop browser’s “print to PDF” functionality.

**C#:**
```
ChromePdfRenderer Renderer = new ChromePdfRenderer();
Renderer.RenderingOptions.CssMediaType = IronPdf.Rendering.PdfCssMediaType.Print;
Renderer.RenderingOptions.PrintHtmlBackgrounds = false;
Renderer.RenderingOptions.CreatePdfFormsFromHtml = false;
var doc = Renderer.RenderUrlAsPdf("https://www.google.com/");
```

**VB:**
```
Dim Renderer As New ChromePdfRenderer()
Renderer.RenderingOptions.CssMediaType = IronPdf.Rendering.PdfCssMediaType.Print
Renderer.RenderingOptions.PrintHtmlBackgrounds = False
Renderer.RenderingOptions.CreatePdfFormsFromHtml = False
Dim doc = Renderer.RenderUrlAsPdf("https://www.google.com/")
```

### Recommended Improvements

We recommend using some Iron-specific improvements.

- Use screen stylesheets to print PDFs. They are less fiddly to develop and more true to existing web assets.
- Responsive layout support.
- Create PDF Forms from your HTML form elements.

**C#:**
```
ChromePdfRenderer Renderer = new ChromePdfRenderer();
Renderer.RenderingOptions.CssMediaType = IronPdf.Rendering.PdfCssMediaType.Screen;
Renderer.RenderingOptions.PrintHtmlBackgrounds = true; Renderer.RenderingOptions.CreatePdfFormsFromHtml = true;
Renderer.RenderingOptions.ViewPortWidth = 1080;  //pixels
var doc = Renderer.RenderUrlAsPdf("https://www.google.com/");
```

**VB:**
```
Dim Renderer As New ChromePdfRenderer()
Renderer.RenderingOptions.CssMediaType = IronPdf.Rendering.PdfCssMediaType.Screen
Renderer.RenderingOptions.PrintHtmlBackgrounds = True
Renderer.RenderingOptions.CreatePdfFormsFromHtml = True
Renderer.RenderingOptions.ViewPortWidth = 1080 'pixels
Dim doc = Renderer.RenderUrlAsPdf("https://www.google.com/")
```

## 4. Comparing Chrome and WebKit

You can use the IronPdf.Rendering.AdaptivePdfRenderer to switch between the ‘Chrome’ and ‘WebKit’ rendering at an instance level if you preferred the old rendering style for some of your applications, or don't want to break unit tests.

**C#:**
```
using IronPdf; 
IronPdf.Rendering.AdaptivePdfRenderer Renderer = new IronPdf.Rendering.AdaptivePdfRenderer();
Renderer.RenderingOptions.RenderingEngine = IronPdf.Rendering.PdfRenderingEngine.Chrome;
/*switch between Chrome and WebKit here*/
var doc = Renderer.RenderHtmlAsPdf("<h1>Hello world!</h1>");
```

**VB:**
```
Imports IronPdf
Private Renderer As New IronPdf.Rendering.AdaptivePdfRenderer()
Renderer.RenderingOptions.RenderingEngine = IronPdf.Rendering.PdfRenderingEngine.Chrome
'switch between Chrome and WebKit here
Dim doc = Renderer.RenderHtmlAsPdf("<h1>Hello world!</h1>")
```

## 5. Multi-threading and Async Support

Multithreading and Async support for our Chrome rendering engine is in a different league to the previous build.

- For enterprise grade multi-threading, use our ChromePdfRenderer in your existing threads and it will work. For web applications this also takes zero setup.
- For batch processing of HTML to PDF, we recommend using the built in .NET Parallel.ForEach pattern.
- We love async and have provided Async variants of all of our rendering methods methods such as _ChromePdfRenderer.RenderHtmlAsPdfAsync_

---

## 6. What is next?

### Features Coming Soon

- Ultra-Slim deployments, useful for Azure functions and AWS Lambda. We aim to provide deployment options to produce the smallest possible disk footprint.
- Mobile rendering support: support for iOS and Android app developers.
- ARM and M1 processor support.
- IE and Firefox rendering options.
- Multi-server distributed rendering architectures for large enterprise users.
- A re-imagined internal PDF document object model to support the widest range of PDF standards. We want to be able to handle reading and automatically fixing corrupted and badly encoded PDF documents elegantly.
- "{YourIdeaHere}" Feature requests and bug reports our customers go to the top of the stack.

Please [Contact Us](https://ironpdf.com/docs/questions/ironpdf-2021-chrome-rendering-engine-eap/#helpscout-support) with any suggestions or questions.