---
title: "Beta domains for Nutrient Web SDK | Nutrient"
canonical_url: "https://www.nutrient.io/guides/web/about/beta-domains/"
md_url: "https://www.nutrient.io/guides/web/about/beta-domains.md"
last_updated: "2026-08-07T00:00:00.000Z"
description: "Request a beta domain for Nutrient Web SDK in development, testing, and staging environments, and learn the naming rule that gets a request approved."
---

# Beta domains for Nutrient Web SDK

A beta domain, also called a development domain, lets you run Nutrient Web SDK in a non-production environment such as development, testing, staging, or QA. Request it in the Nutrient Portal to receive a license key for that domain. Beta domains are for development and testing, not for production.

## Naming your beta domain

Make your beta domain clearly identifiable as a non-production environment. Include a recognizable development indicator in the domain, for example:

- `app.example.dev`

- `staging.example.com`

- `uat.example.com`

- `demo.example.com`

- `app.testing.example.com`

Indicators such as `staging`, `preprod`, `.dev`, `.uat`, `.demo`, and `.testing` all read as development and are suitable.

A beta domain that resembles a production domain doesn’t take the quick path. It goes through a longer, manual review and risks being declined. If the domain you submit looks like a live site, add a development indicator so it reads as a beta domain.

Enter the domain on its own: no protocol (leave off `http://` and `https://`), no wildcard (`*`), and no path such as `example.com/app`.

## Requesting a beta domain in the Nutrient Portal

1. Log in to the [Nutrient Portal](https://my.nutrient.io/).

2. In your Web SDK license row, click **Request Beta/Development License Key**.

3. In the **Request Beta/Development License Key** dialog:
   - In **Beta/Dev Domain**, enter your beta domain — for example, `staging.example.com` or `app.example.dev`.
   - In **Request Reason**, enter a short reason — for example, testing, QA, or staging.
   - Click **Continue**.

4. Review the details and submit the request.

After you submit, an approved beta domain appears in your Nutrient Portal, ready to use. If a request isn’t approved as submitted, or if more details are needed, Nutrient will follow up.

## Requesting a production-looking domain

A development-style domain is the quick path and the recommended one. A domain that resembles production isn’t approved on that basis alone. It goes through a longer, manual review: a person checks the request, you provide a rationale in the **Request Reason** field or through your Customer Success representative, and Nutrient follows up with questions when something isn’t clear before reaching a decision. For a swift turnaround, use a development-style domain.

## Related guides

- [Nutrient Web SDK licensing](https://www.nutrient.io/guides/web/pspdfkit-for-web/licensing.md) covers the subscription model and components.

- [License troubleshooting](https://www.nutrient.io/guides/web/troubleshooting/license-troubleshooting.md) covers common license errors.
---

## Related pages

- [Compare deployment options and use cases for Nutrient document solutions](/guides/web/about/capability-and-component-comparison-document-engine.md)
- [Compare deployment options and use cases for Nutrient document solutions](/guides/web/about/capability-and-component-comparison-web-sdk-document-engine.md)
- [Compare deployment options and use cases for Nutrient document solutions](/guides/web/about/capability-and-component-comparison-web-sdk.md)
- [File type support](/guides/web/about/file-type-support.md)
- [JavaScript PDF framework support](/guides/web/about/frameworks.md)
- [Ways to use Web SDK](/guides/web/about/operational-modes.md)
- [Browser support for our JavaScript PDF viewer](/guides/web/pspdfkit-for-web/browser-support.md)
- [Licensing](/guides/web/pspdfkit-for-web/licensing.md)