LumasCapabilities
Everything the engine does
One native engine behind every binding. These are the manual's own volumes and its own API counts — not a feature list somebody wrote.
Documented APIs
1,276
across 16 capability areas
Worked examples
192
shipped in your download
Languages
9
same engine, different idiom
Royalty
None
redistribute the engine freely
Getting Started
LumasPDF SDK is a native Windows PDF engine shipped as a single self-contained
9 examples
Core SDK
Document lifecycle, pages, getters/setters, document info, actions, OCG, structure tree, and general engine services
383 APIs
· 23 examples
Graphics
Paths, shapes, color spaces, patterns, shadings, transformations, graphics state, and the polygon clipper
114 APIs
· 12 examples
Fonts
Font selection, embedding, subsetting, CID/CJK, encodings, and the fnt* font-service exports
82 APIs
Text
Text output, formatted text, metrics, extraction, and text-state parameters
70 APIs
· 49 examples
Images
Image insertion (JPEG/PNG/BMP/TIFF/JP2/JBIG2), image objects, masks, and metafile playback
45 APIs
· 16 examples
Annotations
All annotation types, bookmarks/outlines, links, and annotation property APIs
95 APIs
· 9 examples
Forms
AcroForm fields: creation, properties, values, appearance, and form impor
115 APIs
· 2 examples
Digital Signatures
Signature fields, PKCS#7/CMS signing, and RFC-3161 timestamps
16 APIs
· 14 examples
Encryption
Standard Security Handler: RC4/AES encryption, passwords, permissions
12 APIs
· 1 examples
PDF/A & Conformance
CheckConformance, PDF/A conversion, ZUGFeRD/Factur-X, XMP
52 APIs
· 8 examples
PDF/X & Prepress
Output intents, trapped state, prepress color
6 APIs
Printing
Windows print pipeline and print-preview bitmaps
17 APIs
Rendering & Viewer
The ras* rasterizer, page-to-bitmap APIs, and the built-in viewer window
130 APIs
· 10 examples
Import & Output APIs
Opening/importing existing PDFs, memory buffers, output files/streams, and conversion
75 APIs
· 31 examples
Reporting
LumasReport is the banded, data-driven reporting engine embedded inside
64 APIs
· 8 examples
Why the numbers are here
Every count on this page is read out of the SDK at build time — the manual's table of contents for the API totals, the example tree for the code. Nothing is typed by hand, and a build fails if the two disagree.
That is deliberate. “109 APIs for AcroForm fields” is something you can check. “Powerful forms support” is not, and a vendor who writes the second is telling you they did not count.