HTML to PDF on ARM64 Linux (AWS Graviton) in C#

Build it step by step.

1. 1Install the NuGet packages

   SelectPdf.Universal is the library. The native package carries the Chromium engine for one platform: add the one for the platform you run on.

   Windows x64 Linux x64 Linux ARM64 macOS · Apple Silicon
   terminal COPY

   dotnet add package SelectPdf.Universal
   dotnet add package SelectPdf.Universal.Native.win-x64

   terminal COPY

   dotnet add package SelectPdf.Universal
   dotnet add package SelectPdf.Universal.Native.linux-x64

   terminal COPY

   dotnet add package SelectPdf.Universal
   dotnet add package SelectPdf.Universal.Native.linux-arm64

   terminal COPY

   dotnet add package SelectPdf.Universal
   dotnet add package SelectPdf.Universal.Native.osx-arm64

2. 2Create a console app

   Any .NET 8 or .NET 10 project works. To follow along, create a console app, run the install commands above inside its folder, then replace Program.cs with the code below.

   terminal COPY

   dotnet new console -n PdfSample
   cd PdfSample

3. 3Import the namespaces

   Program.cs · lines 1–2 COPY

   using System.Runtime.InteropServices;
   using SelectPdf.Universal;

   System.Runtime.InteropServices reports the architecture; the converter is in SelectPdf.Universal. The project references SelectPdf.Universal.Native.linux-arm64, the ARM64 engine, next to SelectPdf.Universal.

4. 4Check where it runs

   Program.cs · lines 4–5 COPY

   // 1. Where the program runs: Arm64 on AWS Graviton and other ARM64 Linux hosts.
   Console.WriteLine($"{RuntimeInformation.OSDescription}, {RuntimeInformation.ProcessArchitecture}");

   RuntimeInformation.ProcessArchitecture prints Arm64 on a Graviton instance, an ARM64 container or an ARM64 developer machine. It is only there to show the architecture; the conversion does not need it.

5. 5Prepare the HTML

   Program.cs · lines 7–16 COPY

   // 2. The same code as on x64: only the engine package differs.
   string html = """
       <html>
         <body style="font-family: sans-serif">
           <h1>Shipping label #58213</h1>
           <p>Deliver to: Fabrikam Ltd, 12 King Street, London</p>
           <p>Rendered by SelectPdf.Universal on Linux.</p>
         </body>
       </html>
       """;

   A raw string literal holds the page. Any HTML works: a template with your data filled in, a Razor view rendered to a string, or a full page with CSS.

6. 6Convert and save

   Program.cs · lines 18–21 COPY

   HtmlToPdf converter = new HtmlToPdf();
   PdfDocument doc = converter.ConvertHtmlString(html);
   doc.Save("label.pdf");
   doc.Close();

   ConvertHtmlString returns a PdfDocument, Save writes label.pdf and Close releases it. This is the code that runs on x64; on ARM64 only the engine package differs.

7. 7Run it

   terminal COPY

   dotnet run
   
   # or in a container on an ARM64 machine (writes label.pdf to ./out):
   docker build --platform linux/arm64 -t label-pdf .
   docker run --rm --platform linux/arm64 -v "$PWD/out:/out" -w /out label-pdf

   The program writes label.pdf to the working folder. Without a license key, every page carries a trial watermark; set GlobalProperties.LicenseKey before the first conversion to remove it.

The complete Program.cs.

This is the exact file our samples pipeline compiled and ran on Linux ARM64 and Linux x64 and macOS ARM64 and Windows x64 to produce the output on this page.

using System.Runtime.InteropServices;
using SelectPdf.Universal;

// 1. Where the program runs: Arm64 on AWS Graviton and other ARM64 Linux hosts.
Console.WriteLine($"{RuntimeInformation.OSDescription}, {RuntimeInformation.ProcessArchitecture}");

// 2. The same code as on x64: only the engine package differs.
string html = """
    <html>
      <body style="font-family: sans-serif">
        <h1>Shipping label #58213</h1>
        <p>Deliver to: Fabrikam Ltd, 12 King Street, London</p>
        <p>Rendered by SelectPdf.Universal on Linux.</p>
      </body>
    </html>
    """;

HtmlToPdf converter = new HtmlToPdf();
PdfDocument doc = converter.ConvertHtmlString(html);
doc.Save("label.pdf");
doc.Close();

Open the project on GitHub → this program and the variations below, ready to dotnet run

Supporting files.

Dockerfile

The same two stages as on x64. The .NET base images are multi-architecture, so on an ARM64 machine, or when building with --platform linux/arm64, they come in their ARM64 variants. There is no apt-get line: the ARM64 engine package carries everything the engine needs.

FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build
WORKDIR /src
COPY . .
RUN dotnet publish -c Release -f net10.0 -o /out

FROM mcr.microsoft.com/dotnet/runtime:10.0
# no apt-get: the Chromium closure ships in SelectPdf.Universal.Native.linux-arm64
WORKDIR /app
COPY --from=build /out ./
ENTRYPOINT ["dotnet", "/app/PdfSample.dll"]

.dockerignore

Keeps the host's build output out of the image's build context, so the publish inside the container starts clean.

bin/
obj/
out/

The PDF it produces.

Common problems and fixes.

Good to know.

• SelectPdf.Universal.Native.linux-arm64 holds the native engines for 64-bit Linux on ARM64 (aarch64). Source
• For ARM64 containers, reference SelectPdf.Universal.Native.linux-arm64 instead of linux-x64; everything else stays the same, and the multi-architecture .NET base images select the matching architecture. Source
• SelectPdf runs on Amazon Web Services on Linux x64 and arm64 (Graviton); on Linux, reference linux-arm64 for Graviton. Source
• On AWS Lambda, arm64 is cheaper per second and converts at a similar speed. Source