QuestPDF 2022.2.5

.NET Core 2.0 .NET Standard 2.0 .NET Framework 4.6.2
There is a newer version of this package available.
See the version list below for details.
dotnet add package QuestPDF --version 2022.2.5
NuGet\Install-Package QuestPDF -Version 2022.2.5
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="QuestPDF" Version="2022.2.5" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add QuestPDF --version 2022.2.5
#r "nuget: QuestPDF, 2022.2.5"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install QuestPDF as a Cake Addin
#addin nuget:?package=QuestPDF&version=2022.2.5

// Install QuestPDF as a Cake Tool
#tool nuget:?package=QuestPDF&version=2022.2.5

QuestPDF Overview

QuestPDF presents a new approach to PDF document generation. Unlike other libraries, it does not rely on the HTML-to-PDF conversion which in many cases is not reliable. Instead, it implements its own layouting engine that is optimized to cover all paging-related requirements. Then, everything is rendered using the SkiaSharp library (a Skia port for .NET, used in Chrome, Android, MAUI, etc.).

I have designed this layouting engine with full paging support in mind. The document consists of many simple elements (e.g. border, background, image, text, padding, table, grid etc.) that are composed together to create more complex structures. This way, as a developer, you can understand the behaviour of every element and use them with full confidence. Additionally, the document and all its elements support paging functionality. For example, an element can be moved to the next page (if there is not enough space) or even be split between pages like table's rows.


Rely on solid fundamentals - This library is created specifically for designing and arranging document layouts, with full paging support. Alternative solutions, such as HTML-based converters, are not designed for this purpose and therefore are often unpredictable and do not produce desired results.

Work with organized self-explanatory code - The entire process of implementing PDF document, takes place in your code. Free yourself from slow visual designers and strange technological limitations. Follow simple yet highly effective approaches to create maintainable, high-quality code.

Compose simple components into complex documents - Do you remember the feeling when your code just works? When your ideas are becoming real without any effort? Working with simple, easy to understand, self-explanatory and highly composable layout elements is the key here!

Create and reuse components - Feel no fear of complex documents! Create custom, reusable components and divide the document's layout into easy to maintain pieces. Inject data to customize content and use slots to enhance composability. Decide how complex approaches your solution needs and follow the best path.

Prototype with ease - We understand that document generation is often tricky and require multiple iterations. The library offers additional prototyping tools such as random text generator or image placeholder element. By following best practices, you can develop a document without having data.

Enjoy fast PDF generation - QuestPDF is created upon SkiaSharp, a well-known graphical library, and converts your data into PDF documents. It offers a highly optimized layouting engine capable of generating over 1000 PDF files per minute per core. The entire process is thread-safe.

Learning resources

Release notes and roadmap - everything that is planned for future library iterations, description of new features and information about potential breaking changes.

Getting started tutorial - a short and easy to follow tutorial showing how to design an invoice document under 200 lines of code.

API Reference - a detailed description of behavior of all available components and how to use them with C# Fluent API.

Patterns and practices - everything that may help you designing great reports and reusable code that is easy to maintain.

Example invoice

Do you believe that creating a complete invoice document can take less than 200 lines of code? We have prepared for you a step-by-step instruction that shows every detail of this implementation and describes the best patterns and practices.

For tutorial, documentation and API reference, please visit the QuestPDF documentation.


Here you can find an example code showing how easy is to write and understand the fluent API.

General document structure with header, content and footer:

public void Compose(IDocumentContainer container)
        .Page(page =>
            page.Footer().AlignCenter().Text(x =>
                x.Span(" / ");

The header area consists of basic invoice information along with a logo placeholder.

void ComposeHeader(IContainer container)
    var titleTextStyle = TextStyle.Default.Size(20).SemiBold().Color(Colors.Blue.Medium);
    container.Row(row =>
            stack.Item().Text($"Invoice #{Model.InvoiceNumber}", titleStyle);

            stack.Item().Text(text =>
                text.Span("Issue date: ", TextStyle.Default.SemiBold());

            stack.Item().Text(text =>
                text.Span("Due date: ", TextStyle.Default.SemiBold());

Implementation of the content area that contains seller and customer details, then listing of all bought products, then a comments section.

void ComposeContent(IContainer container)
    container.PaddingVertical(40).Stack(column => 
        column.Item().Row(row =>
            row.RelativeColumn().Component(new AddressComponent("From", Model.SellerAddress));
            row.RelativeColumn().Component(new AddressComponent("For", Model.CustomerAddress));


        var totalPrice = Model.Items.Sum(x => x.Price * x.Quantity);
            .Text($"Grand total: {totalPrice}$", TextStyle.Default.SemiBold());

        if (!string.IsNullOrWhiteSpace(Model.Comments))

The table and comments codes are extracted into separate methods to increase clarity:

void ComposeTable(IContainer container)
    var headerStyle = TextStyle.Default.SemiBold();
    container.Table(table =>
        table.ColumnsDefinition(columns =>
        table.Header(header =>
            header.Cell().Text("#", headerStyle);
            header.Cell().Text("Product", headerStyle);
            header.Cell().AlignRight().Text("Unit price", headerStyle);
            header.Cell().AlignRight().Text("Quantity", headerStyle);
            header.Cell().AlignRight().Text("Total", headerStyle);
        foreach (var item in Model.Items)
            table.Cell().Element(CellStyle).Text(Model.Items.IndexOf(item) + 1);
            table.Cell().Element(CellStyle).AlignRight().Text($"{item.Price * item.Quantity}$");
            static IContainer CellStyle(IContainer container)
void ComposeComments(IContainer container)
    container.ShowEntire().Background(Colors.Grey.Lighten3).Padding(10).Stack(message => 
        message.Item().Text("Comments", TextStyle.Default.Size(14).SemiBold());

The address details section is implemented using components. This way the code can be easily reused for both seller and customer:

public class AddressComponent : IComponent
    private string Title { get; }
    private Address Address { get; }

    public AddressComponent(string title, Address address)
        Title = title;
        Address = address;
    public void Compose(IContainer container)
        container.ShowEntire().Stack(column =>

                .Text(Title, TextStyle.Default.SemiBold());
            column.Item().Text($"{Address.City}, {Address.State}");
Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed. 
.NET Core netcoreapp2.0 is compatible.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 is compatible.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 is compatible.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (11)

Showing the top 5 NuGet packages that depend on QuestPDF:

Package Downloads

Package Description


A2v10 Platform PDF report




Relorer.QuestPDF.HTML is an extension for QuestPDF that allows to generate PDF from HTML

Verify.QuestPDF The ID prefix of this package has been reserved for one of the owners of this package by

Extends Verify ( to allow verification via QuestPDF.

GitHub repositories (7)

Showing the top 5 popular GitHub repositories that depend on QuestPDF:

Repository Stars
ASP.NET Core eCommerce software. nopCommerce is a free and open-source shopping cart.
Simple, flexible, interactive & powerful charts, maps and gauges for .Net, LiveCharts2 can now practically run everywhere Maui, Uno Platform, Blazor-wasm, WPF, WinForms, Xamarin, Avalonia, WinUI, UWP.
原来所有项目都移动到**OleVersion**目录下进行保留。新的案例装以.net 5.0为主,一部分对以前案例进行升级,一部分将以前的工作经验总结出来,以供大家参考!
Manage your personal finances
This is a repository for creating a Blazor Server dashboard application following the principles of Clean Architecture
Version Downloads Last updated
2023.5.2 233 5/31/2023
2023.5.1 4,640 5/22/2023
2023.5.0 4,285 5/15/2023
2023.4.2 3,502 5/9/2023
2023.4.1 1,741 5/4/2023
2023.4.0 113 5/4/2023
2022.12.6 5,872 5/9/2023
2022.12.5 19,030 4/27/2023
2022.12.4 6,577 4/22/2023
2022.12.3 11,729 4/16/2023
2022.12.2 97,027 3/12/2023
2022.12.1 183,783 1/13/2023
2022.12.0 76,627 12/14/2022
2022.11.0 169,644 11/5/2022
2022.11.0-alpha1 93 11/1/2022
2022.11.0-alpha0 73 10/28/2022
2022.9.1 42,836 10/15/2022
2022.9.0 71,260 9/18/2022
2022.9.0-alpha1 92 9/16/2022
2022.8.2 97,911 8/21/2022
2022.8.1 10,149 8/19/2022
2022.8.0 28,719 8/15/2022
2022.6.3 38,504 7/18/2022
2022.6.2 85,079 6/22/2022
2022.6.1 17,657 6/12/2022
2022.6.0 76,404 6/12/2022
2022.6.0-prerelease 1,470 5/30/2022
2022.5.0 183,506 5/9/2022
2022.4.1 48,792 4/8/2022
2022.4.0 35,317 4/4/2022
2022.4.0-alpha1 125 3/27/2022
2022.4.0-alpha0 96 3/27/2022
2022.3.1 88,061 3/15/2022
2022.3.0 1,749 3/14/2022
2022.2.7 1,380 3/12/2022
2022.2.6 5,943 3/8/2022
2022.2.5 14,845 2/18/2022
2022.2.4 388 2/18/2022
2022.2.3 9,237 2/7/2022
2022.2.2 1,302 2/1/2022
2022.2.1 1,145 1/30/2022
2022.2.0 1,042 1/29/2022
2022.2.0-beta1 119 1/24/2022
2022.1.0 16,607 1/10/2022
2022.1.0-beta5 732 1/7/2022
2022.1.0-beta4 120 1/6/2022
2022.1.0-beta3 119 1/5/2022
2022.1.0-beta2 112 1/5/2022
2022.1.0-beta1 116 1/3/2022
2022.1.0-beta0 116 12/30/2021
2022.1.0-alpha0 145 12/30/2021
2021.12.0 21,126 12/6/2021
2021.12.0-alpha1 940 11/29/2021
2021.12.0-alpha0 176 11/18/2021
2021.11.4 19,049 11/14/2021
2021.11.3 3,836 11/7/2021
2021.11.0-beta3 170 11/3/2021
2021.11.0-beta2 221 10/28/2021
2021.11.0-beta 272 10/23/2021
2021.10.1 7,972 9/30/2021
2021.10.0 334 9/30/2021
2021.10.0-beta.2 177 9/14/2021
2021.10.0-beta 213 9/13/2021
2021.9.3 2,991 9/12/2021
2021.9.2 402 9/1/2021
2021.9.1 264 9/1/2021
2021.9.0 258 8/30/2021
2021.8.0 2,120 8/2/2021
2021.5.2 1,842 5/5/2021
2021.4.0 470 4/2/2021
2021.3.1 6,692 3/1/2021
2021.3.0 283 3/1/2021
2021.2.0 301 2/8/2021
2021.1.0 343 1/4/2021
2020.11.0 5,796 11/1/2020

- Added a `ScaleToFit` element - scales its child down so it fits in the provided space,
- Added a `StopPaging` element - when its child requires more than one page to fully render, only the first page is shown,
- Added a 'LineVertical' and a 'LineHorizontal' elements - those will simplify your code a lot, there is no need to use the `Border` element anymore!
- Renaming: the `Stack` element was renamed to the `Column` element,
- Renaming: children of the `Row` element are now called `items` instead of `columns`, e.g. `RelativeItem` instead of `RelativeColumn`,
- Added support of the `AutoItem` to the `Row` element - those items take as little width as possible,
- Improved default Fluent configuration behavior for elements: Scale, Padding, Translate,
- Improved integration support with the HttpContext.Response.Body. This improvement was introduced by schulz3000, thank you!