NuGet package
One package, native engines for every runtime identifier.
Language binding Package manager Cross-platform win-x86 win-x64 win-arm64 linux-x64 linux-arm64 macos
Who this is for: .NET developers who want dotnet add package and nothing else.
The package carries the engine for seven RIDs across six platform families, so the right binary is selected at publish time without any manual copying.
The download is public and needs no key. Unlicensed output carries an evaluation watermark and nothing else is restricted.
Is this the right package for you?
Best for
You are on modern .NET and want `dotnet add package` to be the whole install step, with the right native engine selected per runtime identifier.
Not the right choice when
You need to read or modify the binding source, or your build cannot reach a package feed. The source P/Invoke package covers both.
What is in the download
Generated from the packaging script, not from a description. Each row names the build output the binary came from.
| Platform | Built from | Licence covers it |
|---|---|---|
win-x86 |
nupkg_src | Yes |
win-x64 |
nupkg_src | Yes |
win-arm64 |
nupkg_src | Yes |
linux-x64 |
nupkg_src | Yes |
linux-arm64 |
nupkg_src | Yes |
macos |
nupkg_src | Yes |
Install
dotnet add package LumasPDF.Net
Your first PDF
The smallest complete program: create, write, close.
using LumasPdf;
var pdf = new PdfEngine();
pdf.CreatePDF("hello.pdf");
pdf.Append();
pdf.SetFont("Helvetica", FontStyle.None, 24, true, CodePage.Cp1252);
pdf.WriteFText(TextAlign.Center, "Hello from LumasPDF");
pdf.EndPage();
pdf.CloseFile();
How it deploys
The package carries the native engines and the build copies the right one next to your output. Publishing self-contained or framework-dependent both work.
Platforms
Two different questions, answered separately, because for one package today they have different answers.
| Platform | Licence covers it | Binary in the download |
|---|---|---|
win-x86 |
Yes | Yes |
win-x64 |
Yes | Yes |
win-arm64 |
Yes | Yes |
linux-x64 |
Yes | Yes |
linux-arm64 |
Yes | Yes |
macos |
Yes | Yes |
What you can build with it
The same documented API is behind every package. These are the areas most of it is in.
More worked examples
Every one of these is a file in the download, transcribed byte-for-byte. Nothing on this site is a snippet written for a web page.
Editions for this package
The edition decides which engine features your key turns on. Every one of them is royalty-free: you may redistribute the engine inside your application at no per-copy cost.
| Edition | Price | Includes | Available add-ons | Buy |
|---|---|---|---|---|
| Starter | EUR 249.00 | PDF Creation · Royalty free delivery | — | Buy → |
| Lite | EUR 399.00 | PDF Creation · PDF Import · Royalty free delivery | — | Buy → |
| Professional | EUR 699.00 | PDF Creation · PDF Import · PDF Optimization · Rendering Engine · Royalty free delivery | PDF/A Extension · LumasReport | Buy → |
| Enterprise | EUR 1799.00 | PDF Creation · PDF Import · PDF Optimization · Rendering Engine · Source Codes · Royalty free delivery | PDF/A Extension · LumasReport | Buy → |
Releases
Your key licenses every build released on or before your coverage date — including this one, if it falls inside it.
Known issues
No published, unfixed defect names this package. The whole list is public.
Questions about this package
Do I pay a royalty for every copy I ship?
No. Every edition is royalty-free: you may redistribute the engine inside your own application to as many end users as you like, with no per-copy fee and no runtime licence for them to accept.
Does the licence need to phone home or be activated?
No. Your build verifies the key locally, in your process. There is no activation call, no deactivation, and no server for us to take down — which is why the engine works in an air-gapped network and in a container that scales to zero.
What happens when my maintenance period ends?
Nothing stops working. A key licenses any build released on or before your coverage date, forever, including in production. Maintenance decides which BUILDS the key covers, never when it expires — the engine compares against a build date and never against the clock.
What does the free download do without a key?
Everything. The download is public and unrestricted and needs no key to run; unlicensed output simply carries an evaluation watermark. Register and we send a trial key that removes it, so you can evaluate the real output before you buy.
Can we buy on a purchase order and get a VAT invoice?
Yes. Request a quote and we will price the configuration, invoice against your PO, and show the VAT treatment for your country on the quote itself rather than after checkout.
Try NuGet package before you decide
Public download, no account, no card. Register only when you want the evaluation watermark gone.