--- title: "Nutrient Web SDK licensing" canonical_url: "https://www.nutrient.io/guides/web/license/" md_url: "https://www.nutrient.io/guides/web/license.md" last_updated: "2026-11-02T00:00:00.000Z" description: "Learn about the subscription model for Nutrient Web SDK licensing, domain deployment, and how to activate your product effectively." --- # Licensing Thank you for considering Nutrient Web SDK. Licensing for Nutrient Web SDK operates on a subscription model. Several factors affect the price: the [operational mode](https://www.nutrient.io/guides/web/about/operational-modes.md), required [components](https://www.nutrient.io/sdk/features-list/), whether you require headless server-side processing, and the number of users. If you’re interested in licensing our product, please get in touch through our [Contact Sales](https://www.nutrient.io/contact-sales/) form. If you’re an existing customer, learn more about [updating the license key](https://www.nutrient.io/guides/web/license/add-license-key.md). When loading app-provided documents with DWS Viewer API, Web SDK uses a DWS Viewer API session instead of `licenseKey`. Refer to the [open app-provided documents](https://www.nutrient.io/guides/dws-viewer/developer-guides/open-client-provided-documents.md) guide for that flow. Web SDK verifies a license key offline, but each viewer load with a publishable key or session token [needs a connection to DWS](https://www.nutrient.io/guides/dws-viewer/developer-guides/open-client-provided-documents.md#offline-use-and-token-lifetime). ## Deployment When you purchase a subscription license for Nutrient Web SDK, you’re able to deploy on a given number of agreed-upon domain names. You can set up these domains in the [Nutrient Portal](https://my.nutrient.io/). Nutrient Web SDK will verify that the `Origin` of the browser tab where it’s used matches the list of allowed domains for your license. Refer to the [Document Engine licensing](https://www.nutrient.io/guides/document-engine/license.md) guide for how Document Engine’s online and offline license types affect network and analytics behavior. Activate Nutrient Web SDK with a production or development key. Development mode doesn’t restrict the allowed `Origin`. If your license agreement differs from the above, then the language of that agreement is binding. ## Product-specific Once purchased, the Document Engine backend product works only within Nutrient Web SDK. To use Document Engine with other Nutrient products, license those products as well. ## Headless server-side processing Nutrient Web SDK with Document Engine doesn’t cover headless server-side processing unless you’ve licensed those components too. Purchasing Nutrient Web SDK with Document Engine includes JavaScript API access for working with documents programmatically or headlessly, without licensing headless server-side processing components. ## Component selection Components are the smallest licensable part of Nutrient, and they come with a set of unique features. When you license a component, you license its entire feature set, whether you use one component feature or all of them. Find the full list of licensable components and their features on our [features list](https://www.nutrient.io/sdk/features-list/). ## License agreement By downloading and evaluating the Nutrient SDK demo, you accept the terms of the [evaluation license agreement](https://www.nutrient.io/downloads/legal/Nutrient_SDK_User_Evaluation_Subscription_Agreement.pdf). To purchase Nutrient, the company that owns the end product/app must sign a license contract. We use DocuSign for a fast and secure digital signing experience. If you require a physical copy of a contract, we can accommodate this need as well. Licensing runs on a per-year basis. You can’t change this to a monthly license. ## Agreement modifications Nutrient licenses technology to a large number of companies, so we keep contract modifications to a minimum. Modifications incur additional management and reviewing overhead. Our quote assumes acceptance of our standard license agreement. We’re somewhat flexible; however, making changes to a contract will take more time and likely increase your cost. As we’re an Austria-based company, the place of jurisdiction is Vienna, Austria. ## Setting up a domain in the Nutrient Portal When setting up your license using the [Nutrient Portal](https://my.nutrient.io/), assign a web domain to activate your product. Always make sure to use the exact domain (including any subdomains) your product is using. If your product runs on multiple domains at once — for example, `sales.internal.example.com` and `board.internal.example.com` — [reach out to us](https://support.nutrient.io/hc/en-us/requests/new) to discuss a custom solution. To determine the required domain, open the JavaScript console on the website that will run Nutrient Web SDK and execute the following code: ```js console.log(location.origin); ``` For non-production environments such as development, testing, or staging, request a beta domain. See [requesting a beta usage domain](https://www.nutrient.io/guides/web/license/requesting-a-beta-usage-domain.md) for the naming rules and how to request one. ## Updating your Nutrient Web SDK license You can safely update your license without updating to the newest Nutrient Web SDK version. ## Security The license key is an encrypted payload. The SDK verifies offline that Nutrient produced it and that it hasn’t been tampered with. The key carries the details of what the license permits. The way this works is: When you purchase our license, you provide a domain on which you’re deploying your application. This is part of the encrypted information. The Nutrient SDK then checks locally from the browser if it’s been loaded at the same location/domain contained in the license. If so, the key is safe to use. If someone stole it, they’d only be able to use it at the permitted locations encoded within the key itself. If they tried to change the content to add their own domains, we’d be able to detect it. --- ## Related pages - [How to add your license key for Nutrient Web SDK](/guides/web/license/add-license-key.md) - [Register a production domain for Nutrient Web SDK](/guides/web/license/register-a-production-domain.md) - [Request a beta usage domain for Nutrient Web SDK](/guides/web/license/requesting-a-beta-usage-domain.md) ## Pages in this section - [License troubleshooting for Nutrient Web SDK](/guides/web/license/troubleshooting/license-troubleshooting.md) - [❌ INCORRECT: Missing `NEXT_PUBLIC_` prefix.](/guides/web/license/troubleshooting/watermark-still-appearing.md)