Select Get License Key and choose version 31.x.x or higher.
: If you upgrade your Syncfusion packages from one major version to another (e.g., from v24 to v25), you must generate a new license key for the new major version. The old key will not work.
| # | Best Practice | |---|----------------| | 1 | Always register the key at the earliest possible application entry point. | | 2 | Use separate keys for dev/staging/production. | | 3 | Never hardcode keys – use environment variables or secret managers. | | 4 | Automate key injection via CI/CD to avoid manual errors. | | 5 | Test license validation as part of your build pipeline. | | 6 | Keep a copy of the license key in a secure password manager (as a backup). | syncfusion generate license key best
store your license key as a protected variable (e.g., SYNCFUSION_LICENSE ) and have your build script create the syncfusion-license.txt file on the fly, then run the activation command. Do not commit the license file to version control.
Choose the required edition (e.g., UI Edition for web/mobile controls, or Document SDK for file processing). Download/Copy the Key. Select Get License Key and choose version 31
: The key will be generated as a string for you to copy. Best Practices for Management & Security
With a correctly generated and registered license key, you can focus on what really matters: building great applications with Syncfusion’s powerful components. | # | Best Practice | |---|----------------| |
Need help troubleshooting a specific "License key not found" error? Check the exact Syncfusion assembly version in your bin folder and ensure it matches the year/volume of the key you generated.
Once you have generated your license key, how you store and register it matters as much as the generation itself. Below are the recommended approaches for different scenarios.
On the Downloads & Keys page, you will see options to generate keys for specific versions and platforms.