> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/license-entitlements/portal/offline-portal.md).

# Offline Portal

**URL:** [offline.licensespring.com](https://offline.licensespring.com/)

End users of computers without an internet connection use the Offline Portal to activate a license, sync usage, and deactivate a license.<br>

{% embed url="<https://www.youtube.com/watch?v=mN4KiwQbNrI>" %}

### What the Offline Portal Is Used For

* **Activate:** node-lock a license, which binds it to one specific computer, when that computer cannot reach the License API, [See Activating and Deactivating Offline.](https://docs.licensespring.com/license-entitlements/portal/offline-portal/activating-and-deactivating-offline.md)
* **Sync usage:** report consumptions, feature consumptions, and device variables from an offline computer without deactivating it.[ See Syncing Usage Offline.](https://docs.licensespring.com/license-entitlements/portal/offline-portal/syncing-usage-offline.md)
* **Deactivate:** release an offline node-locked license so it can be activated on another computer. [See Activating and Deactivating Offline.](https://docs.licensespring.com/license-entitlements/portal/offline-portal/activating-and-deactivating-offline.md)

### How It Works

{% stepper %}
{% step %}

#### Create a request file

The application on the offline computer creates a request file (`.req`).
{% endstep %}

{% step %}

#### Upload it to the Offline Portal

The end user copies the file to a computer that is online and uploads it to the Offline Portal.
{% endstep %}

{% step %}

#### Receive the response file

The portal sends the request to LicenseSpring and returns a response file: a license file for an activation, or a sync response for a sync. A deactivation needs no response file.
{% endstep %}

{% step %}

#### Load it in the application

The end user copies the response file back to the offline computer and loads it in the application.
{% endstep %}
{% endstepper %}

### Uploading a Request File

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FM6RR2dHTJvAofNPhWLBy%2F01-upload-page.jpg?alt=media&amp;token=fbbe04f7-3226-48cc-b221-09fc48081b64" alt=""><figcaption></figcaption></figure>

Every offline action starts the same way: upload the `.req` file the application created.

{% stepper %}
{% step %}

#### Select the request file

Open the Offline Portal and drag the request file onto the upload area. You can also use the **click to select** link and choose it. The upload area highlights while you drag a file over the page.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FMTXRPG2A2qDwSmC2KBRD%2F02-upload-drag-over.jpg?alt=media&amp;token=ab06ec2a-c223-4709-9caa-87c8ccb3926a" alt=""><figcaption></figcaption></figure>

The portal checks the file before it uploads anything:

| Check         | Requirement                    | If it fails                                         |
| ------------- | ------------------------------ | --------------------------------------------------- |
| File type     | Upload a `.req` file.          | The portal shows "This file type is not supported." |
| File size     | Keep the file at 4 MB or less. | Create a smaller request file in the application.   |
| File count    | Select or drop one file.       | Upload files one at a time.                         |
| {% endstep %} |                                |                                                     |

{% step %}

#### Enable bundle licensing when needed

For a bundle activation or deactivation, turn on **Bundle license** under the upload area before uploading. Sync files work with the toggle on or off.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FkVOeMWBPBDk1lHAHwBEZ%2F24-bundle-toggle-on.jpg?alt=media&amp;token=39ba7ed4-7842-44fd-bd71-c47799207c43" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Wait for processing

The portal uploads the file, then waits while the server processes it. A progress card shows the file name, request type, and progress steps.

{% hint style="info" %}
Activations and deactivations usually take a few seconds. A large sync file can take up to a minute. Keep the page open until the result appears.
{% endhint %}
{% endstep %}
{% endstepper %}

### White Labeling the Offline Portal

The Offline Portal can run on your own subdomain with your branding. Contact LicenseSpring support to set it up.

| Branding element      | Where it appears                                                             |
| --------------------- | ---------------------------------------------------------------------------- |
| **Logo and favicon**  | At the top of the portal and in the browser tab                              |
| **Company name**      | Under the logo and in the browser tab title                                  |
| **Title and message** | Replaces “Offline Licensing” and the introductory text                       |
| **Colors**            | The page background, buttons, primary and secondary text, and status accents |

The branding applies to every screen, including progress, results and errors.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FJNABbAUdPvOsLx3baPWE%2F28-white-labeled-upload-page.jpg?alt=media&amp;token=8af21c7b-dc96-467a-aa26-97da124e5405" alt=""><figcaption></figcaption></figure>

* White-labeled upload page

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FF6v4ZsjjlIPykGW0LPEN%2F29-white-labeled-activation-success.jpg?alt=media&amp;token=bc837917-c873-48e7-8881-e944774115c4" alt=""><figcaption></figcaption></figure>

* White-labeled activation success page


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/license-entitlements/portal/offline-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
