Ironpdf: License Key

Before searching for your key, you must understand which license type you own. Each license tier affects where and how you can use the key.

: For production use, various perpetual and subscription licenses are available for purchase directly from Iron Software or authorized distributors like ComponentSource Available License Types

You need a license key for any production use, including server-side applications deployed to development, staging, and production servers. While you can run the library locally for basic testing without a key, generating any significant content will trigger the evaluation restrictions. ironpdf license key

Built for a single developer working on one project.

| Feature | Trial Key | Paid Key | |--------|----------|----------| | Watermark on PDFs | ✅ Yes (removable after 30 days?) | ❌ No | | Time limit | 30 days | None | | Production use | ❌ No | ✅ Yes | | Docker/container | ❌ Blocked | ✅ Allowed | Before searching for your key, you must understand

A: IronPDF is a commercial product, but Iron Software manages free open‑source demo projects on GitHub. The main library requires a paid license for production use.

This is the most robust method and should be called at the start of your application before any IronPDF methods are used. // Example for C# .NET IronPdf.License.LicenseKey = "IRONPDF-MYLICENSE-KEY-EXPIRES.01.JAN.2050" Use code with caution. Copied to clipboard 2. Configuration Files While you can run the library locally for

When deploying software automatically, hardcoding keys into git repositories poses a security risk.

throw new Exception("Invalid IronPDF license key");