---
title: "Upgrading from PSPDFKit Processor"
canonical_url: "https://www.nutrient.io/guides/document-engine/release-notes/upgrading-from-processor/"
md_url: "https://www.nutrient.io/guides/document-engine/release-notes/upgrading-from-processor.md"
last_updated: "2026-06-11T00:00:00.000Z"
description: "Learn how to migrate from PSPDFKit Processor to Document Engine by updating your Docker image and understanding new licensing requirements for seamless operation."
---

# Upgrading from PSPDFKit Processor

[PSPDFKit Processor](https://www.nutrient.io/guides/product-archives-and-deprecated-solutions.md) no longer receives updates as of version 2023.11.1 and has been replaced by [Document Engine](https://www.nutrient.io/guides/document-engine.md). This guide will walk you through the necessary steps to migrate your existing Processor instance to Document Engine.

## Before the update

If you haven’t done so yet, now is a good time to carefully read our [overview of the upgrade process](https://www.nutrient.io/guides/document-engine/release-notes/upgrading.md).

## Update the Docker image

To upgrade to Document Engine, you’ll need to change Processor’s Docker image from `pspdfkit/processor` to `pspdfkit/document-engine`.

Use the following image for the Document Engine version 1.16.0:

```sh

pspdfkit/document-engine:1.16.0

```

We publish our images to Docker Hub and AWS ECR. Refer to our [Docker registries](https://www.nutrient.io/guides/document-engine/deployment/docker-registry.md) guide to learn more.

Always use a specific image version tag; never rely on `:latest`.

## License changes

Document Engine uses a new license format that streamlines licensing. Refer to our [licensing](https://www.nutrient.io/guides/document-engine/about/licensing.md) guide to learn more about Document Engine licensing.

As of Document Engine 1.16.0, legacy Processor and Nutrient Web SDK (server-backed) activation and license keys are no longer supported, including legacy offline license keys.

Before upgrading, replace any legacy Processor or Nutrient Web SDK (server-backed) activation or license key with a Document Engine activation key or offline license key. Document Engine activation keys are expected to start with the `3-` prefix.

If an existing installation was previously activated with a legacy Processor or Nutrient Web SDK (server-backed) activation or license key, the stored activated license in the database or persistent storage can also block startup after upgrade. In that case, clear the stored activated license, configure a valid Document Engine activation key or offline license key, and start Document Engine again.

## Configuration changes

The following [configuration](https://www.nutrient.io/guides/document-engine/configuration/options.md) option needs to be updated (if you’re using it):

- `PROCESSOR_REQUEST_TIMEOUT` has been renamed to `SERVER_REQUEST_TIMEOUT`.

## API changes

Document Engine provides APIs that are compatible with PSPDFKit Processor. However, legacy Processor endpoints have been renamed:

- The `/build` endpoint has been renamed to [`/api/build`](https://www.nutrient.io/api/reference/document-engine/upstream/#tag/Document-Editing/operation/build-document).

- The `/validate_pdfa` endpoint has been renamed to [`/api/validate_pdfa`](https://www.nutrient.io/api/reference/document-engine/upstream/#tag/PDFA-Validation/operation/validate-pdfa).

- The `/process` endpoint has been renamed to [`/api/build`](https://www.nutrient.io/api/reference/document-engine/upstream/#tag/Document-Editing/operation/build-document). Refer to the [Processor 2023.3 migration guide](https://www.nutrient.io/guides/product-archives-and-deprecated-solutions.md) to review the endpoints that have been changed.

- The `/render` endpoint has been removed. Refer to our [rendering](https://www.nutrient.io/guides/document-engine/rendering.md) guide for the current API.
---

## Related pages

- [1 11](/guides/document-engine/release-notes/1-11.md)
- [1 1](/guides/document-engine/release-notes/1-1.md)
- [1 10](/guides/document-engine/release-notes/1-10.md)
- [1 12](/guides/document-engine/release-notes/1-12.md)
- [1 14](/guides/document-engine/release-notes/1-14.md)
- [1 13](/guides/document-engine/release-notes/1-13.md)
- [1 15](/guides/document-engine/release-notes/1-15.md)
- [1 2](/guides/document-engine/release-notes/1-2.md)
- [1 3](/guides/document-engine/release-notes/1-3.md)
- [1 16](/guides/document-engine/release-notes/1-16.md)
- [1 4](/guides/document-engine/release-notes/1-4.md)
- [1 5](/guides/document-engine/release-notes/1-5.md)
- [1 6](/guides/document-engine/release-notes/1-6.md)
- [1 8](/guides/document-engine/release-notes/1-8.md)
- [1 7](/guides/document-engine/release-notes/1-7.md)
- [Upgrading from PSPDFKit Server](/guides/document-engine/release-notes/upgrading-from-server.md)
- [1 9](/guides/document-engine/release-notes/1-9.md)
- [Upgrading Document Engine](/guides/document-engine/release-notes/upgrading.md)