IronPDF is well-regarded for its developer-friendly, . This means that when you purchase a license, it’s a one-time payment that allows you to use the specific version of the library you bought for an unlimited time, without any recurring fees.
You have exceeded the number of allowed developers or machines. A Single Developer license allows one named developer but unlimited deploys to servers. However, simultaneous usage from multiple developer machines triggers this.
var key = Configuration["IronPdf:LicenseKey"]; License.LicenseKey = key;
// Now you can create PDFs without watermarks var renderer = new ChromePdfRenderer(); var pdf = renderer.RenderHtmlAsPdf("<h1>Hello World!</h1>"); pdf.SaveAs("output.pdf"); ironpdf license key
"IronPdf": "LicenseKey": "YOUR-KEY-HERE"
Covers up to 3 developers and 3 locations. Ideal for small teams.
Sharing license keys across teams without purchasing a multi-developer license violates the EULA and may result in key revocation. IronPDF is well-regarded for its developer-friendly,
Usually starts around $999, typically tailored for a single developer.
Store your IronPDF license key as a "Secret" or "Variable" in your pipeline settings. Pass it into your application context during build or release.
bool isLicensed = IronPdf.License.IsLicensed; Console.WriteLine($"Is IronPDF licensed in this session? isLicensed"); A Single Developer license allows one named developer
"IronPdf.LicenseKey": "IRONPDF-YOUR-LICENSE-KEY-12345"
Best for a single developer working on a single project.
Once you receive your license key (a long alphanumeric string starting with IRONPDF. ), you must apply it to your project. You can activate the key using three primary methods.
Otherwise, you'll see "License key not recognized" even if it's correct in code.
IronPDF is well-regarded for its developer-friendly, . This means that when you purchase a license, it’s a one-time payment that allows you to use the specific version of the library you bought for an unlimited time, without any recurring fees.
You have exceeded the number of allowed developers or machines. A Single Developer license allows one named developer but unlimited deploys to servers. However, simultaneous usage from multiple developer machines triggers this.
var key = Configuration["IronPdf:LicenseKey"]; License.LicenseKey = key;
// Now you can create PDFs without watermarks var renderer = new ChromePdfRenderer(); var pdf = renderer.RenderHtmlAsPdf("<h1>Hello World!</h1>"); pdf.SaveAs("output.pdf");
"IronPdf": "LicenseKey": "YOUR-KEY-HERE"
Covers up to 3 developers and 3 locations. Ideal for small teams.
Sharing license keys across teams without purchasing a multi-developer license violates the EULA and may result in key revocation.
Usually starts around $999, typically tailored for a single developer.
Store your IronPDF license key as a "Secret" or "Variable" in your pipeline settings. Pass it into your application context during build or release.
bool isLicensed = IronPdf.License.IsLicensed; Console.WriteLine($"Is IronPDF licensed in this session? isLicensed");
"IronPdf.LicenseKey": "IRONPDF-YOUR-LICENSE-KEY-12345"
Best for a single developer working on a single project.
Once you receive your license key (a long alphanumeric string starting with IRONPDF. ), you must apply it to your project. You can activate the key using three primary methods.
Otherwise, you'll see "License key not recognized" even if it's correct in code.