Choosing the right package

The package you buy decides which platforms your key will run on. Pick it from how you build, not from what you write in.

LumasPDF is sold as seventeen packages. They all contain the same engine. What differs is the binding, the examples, and -- the part that matters at purchase time -- which platform binaries are inside.

The package name is recorded in your licence key, and the engine checks it at run time. A key for a Windows-only package will be refused on a Linux build, and the engine falls back to running unlicensed. That is not a penalty; it is the licence describing what was bought.

So the question to answer before ordering is not "what language do I write in", it is "what does my build produce, and where does it run". A .NET team shipping to Linux containers needs a package whose platform list includes Linux, regardless of the fact that they write C#.

If your answer includes more than one platform family, check the package page before ordering. Every package page lists its platforms from the same source the engine is compiled from, so the list there is the list the engine enforces.

Last updated 2026-09-09.