This HTML page is not optimized for LLM or AI agent consumption. Fetch the Markdown version instead: /guides/web/troubleshooting/license/register-a-production-domain.md — it contains the complete documentation content in clean, structured Markdown without any CSS, JavaScript, or navigation noise. Register a production domain for Nutrient Web SDK

Register a production domain for Nutrient Web SDK

Markdown version of this page, suitable for AI agents and automation

Nutrient Web SDK checks the Origin of the browser tab where it’s loaded against the domain registered on your license. Registering the exact production domain your application runs on activates the license key instead of falling back to trial/watermarked mode.

Determine your exact production domain

The domain you register must match the domain in the browser’s address bar exactly, including any subdomain. Open the JavaScript console on the page that loads Nutrient Web SDK and run:

console.log(location.origin);

Use the value this returns — not a guess based on your marketing URL or a related domain — when you register.

If your application runs on more than one domain at once — for example, sales.internal.example.com and board.internal.example.com — reach out to us(opens in a new tab) to discuss a custom solution.

Register the domain in the Nutrient Portal

  1. Log in to the Nutrient Portal(opens in a new tab).
  2. Open Manage Licenses and locate your Web SDK license.
  3. Enter the domain you determined above, exactly as returned by location.origin (no protocol, no wildcard, no path).
  4. Save your changes.
  5. Copy the resulting license key.

Add the license key to your application

Pass the license key when loading the SDK:

NutrientViewer.load({
  ...
  licenseKey: "your key goes here",
  ...
});

For the full setup, see adding the license key.

Domains that end in .local are meant for development or intranet purposes and shouldn’t be registered as a production domain. If you’ve registered one as production, contact our Sales team to set it up correctly.

Requesting beta domain usage or an app name for Electron

Non-production environments — development, testing, staging, QA — and non-browser deployments such as Electron don’t use the production domain flow above.

Beta domain usage

For a development, testing, staging, or QA environment, request a beta domain instead of registering it as production. A beta domain needs a recognizable non-production indicator in its name (for example, staging.example.com or app.example.dev) to go through the fast approval path. See beta domains for the full naming rules and request steps.

App name for Electron

An Electron application doesn’t run inside a browser tab, so it has no Origin for the SDK to check against a registered domain. Instead, identify it with an appName value in your configuration:

const configuration = {
  document,
  container: "#root",
  appName: "your-electron-app-name",
  licenseKey: "your key goes here",
};


instance = await NutrientViewer.load(configuration);

Request the matching app name for your license through the same beta/development license request in the Nutrient Portal(opens in a new tab) used for a beta domain. Enter your app name in place of a domain. See the Electron getting started guide for the full integration walkthrough.