An IronPDF license key unlocks production deployment for your Node.js application. Without a valid key, IronPDF runs in trial mode and stamps every generated PDF with a watermark. Applying a license key removes that watermark and lifts all output restrictions, giving you fully compliant documents ready for end-users. The steps below walk through obtaining a key, configuring it correctly, and confirming it is active.
Quickstart: Apply an IronPDF License Key in Node.jsApply your IronPDF license key in three steps
- Get a license key — purchase a license or request a free 30-day trial from the IronPDF licensing page.
- Set the key before any PDF operation — assign it to
IronPdfGlobalConfig.getConfig().licenseKeyat application startup. - Verify the key is active — call
IronPdfGlobalConfig.getConfig().isLicensedand check for atruereturn value.
How Do You Get an IronPDF License Key?
A license key is issued when you purchase a commercial license or register for a free trial. Both paths go through the same IronPDF licensing page, where options are available for single-developer, team, and royalty-free redistribution tiers.
To evaluate IronPDF before committing to a purchase, sign up for a free 30-day trial license. The trial key activates all production features - including HTML-to-PDF rendering, PDF merging, stamping, and encryption - so you can test the full API against your real requirements.
If your organization needs volume pricing or an enterprise agreement, contact the IronPDF sales team for a custom quote.
How Do You Apply a License Key in Node.js?
Set the licenseKey property on the global configuration object before calling any IronPDF function. Place this initialization at the entry point of your application - typically the first lines of your index.js or app.js file - so the key is active for every subsequent PDF operation.
// Import IronPdfGlobalConfig from the IronPDF package
import { IronPdfGlobalConfig } from "@ironsoftware/ironpdf";
// Apply your license key at application startup
// Replace the placeholder with the key you received from Iron Software
IronPdfGlobalConfig.getConfig().licenseKey = "YOUR-LICENSE-KEY-HERE";The assignment takes effect immediately - no restart or re-import is required. Any PDF operation that runs after this line will use the licensed engine.
How Do You Follow License Key Best Practices?
Hardcoding a license key directly in source code creates a security risk, particularly in public repositories. The recommended approach is to store the key in an environment variable and read it at runtime.
import { IronPdfGlobalConfig } from "@ironsoftware/ironpdf";
// Read the license key from an environment variable
// Set IRONPDF_LICENSE_KEY in your .env file or deployment environment
IronPdfGlobalConfig.getConfig().licenseKey = process.env.IRONPDF_LICENSE_KEY;When using this pattern, add IRONPDF_LICENSE_KEY=your-key to a .env file for local development and configure the variable in your hosting platform's secret management system for production. Add .env to .gitignore to prevent accidental commits.
Two additional practices reduce operational risk:
- Apply the key once at startup. Assigning it repeatedly on each request is harmless but wastes cycles. Initialize it in your app's entry module.
- Keep the key out of client-side bundles. License key initialization must occur on the server. IronPDF for Node.js runs in a server-side context, so this is the natural placement - but double-check that your build pipeline does not bundle
IronPdfGlobalConfiginto browser-facing code.
How Do You Verify Your License Key Is Working?
After applying the key, confirm it was accepted before running your production workflows. Use the isLicensed flag on the global configuration object.
import { IronPdfGlobalConfig } from "@ironsoftware/ironpdf";
// Apply the license key
IronPdfGlobalConfig.getConfig().licenseKey = process.env.IRONPDF_LICENSE_KEY;
// Verify the key was accepted
const config = IronPdfGlobalConfig.getConfig();
if (config.isLicensed) {
console.log("IronPDF: license key accepted — production mode active.");
} else {
console.warn("IronPDF: running in trial mode — PDFs will contain a watermark.");
}A true result confirms the key is valid and the engine is running in licensed mode. A false result means the key was not recognized - double-check for extra whitespace, truncation, or an expired trial key. If the problem persists, contact IronPDF support with your key and Node.js version.
What Are the Next Steps?
With a valid license key in place, the IronPDF engine is ready for production workloads. Start with the most common tasks:
- Generate PDFs from HTML - convert HTML strings, files, or URLs into pixel-accurate PDF documents.
- Merge, split, and manipulate existing PDFs - combine multiple files or extract specific page ranges.
- Add headers, footers, and watermarks - brand your output with consistent page elements.
- Explore the full IronPDF for Node.js documentation for API reference, tutorials, and code examples.
To upgrade your license tier or add developer seats, visit the IronPDF licensing page or start a free trial to evaluate a higher tier before purchasing.
Frequently Asked Questions
What is the purpose of an IronPDF license key in Node.js?
An IronPDF license key unlocks production deployment for your Node.js application, removing the watermark that appears during the trial mode and lifting all output restrictions.
How do you obtain an IronPDF license key?
You can obtain an IronPDF license key by purchasing a commercial license or registering for a free trial on the IronPDF licensing page.
How do you apply an IronPDF license key in a Node.js application?
You apply the license key by assigning it to the `IronPdfGlobalConfig.getConfig().licenseKey` property at the application startup before performing any PDF operations.
Why is it not recommended to hardcode the license key in your source code?
Hardcoding the license key creates a security risk, especially in public repositories. It is recommended to store it in an environment variable and read it at runtime.
How can you verify if your IronPDF license key is working in Node.js?
To verify if the license key is working, you can use the `isLicensed` flag on the global configuration object. A `true` result confirms that the key is valid.
What are the best practices for managing an IronPDF license key?
Best practices include storing the key in an environment variable, applying the key once at startup, and ensuring it is not included in client-side bundles.
What should you do if your license key is not recognized?
If the key is not recognized, check for issues like extra whitespace, truncation, or expiration. If issues persist, contact IronPDF support with your key and Node.js version.
What functionalities does the IronPDF license key unlock?
The license key unlocks production functionalities such as HTML-to-PDF rendering, PDF merging, stamping, and encryption.
What are the next steps after applying the IronPDF license key?
After applying the license key, you can start generating, merging, and manipulating PDFs, and explore IronPDF's full documentation for more features and capabilities.
How can you upgrade your IronPDF license tier?
To upgrade your license tier or add developer seats, visit the IronPDF licensing page or start a free trial to evaluate a higher tier.
Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.
