---
title: "1.14 release notes"
canonical_url: "https://www.nutrient.io/guides/document-engine/release-notes/1-14/"
md_url: "https://www.nutrient.io/guides/document-engine/release-notes/1-14.md"
last_updated: "2026-06-09T20:45:45.749Z"
description: "Document Engine 1.14 release notes: TXT-to-PDF conversion, Word header/footer and spreadsheet print area rendering options, and Brotli support."
---

Before attempting to upgrade to Document Engine 1.14, make sure your application runs as expected on your current version. If you’re on version 1.6.1 or later, you can upgrade directly to 1.14. If you’re on an earlier version, follow the step-by-step upgrade path outlined in our [upgrade](https://www.nutrient.io/guides/document-engine/release-notes/upgrading.md#general-advice) guide.

## Highlights

Document Engine 1.14 expands file conversion capabilities with TXT-to-PDF support; adds rendering options for Word document headers/footers, spreadsheet print areas, and tile scale limits; and introduces Brotli decompression for improved PDF handling.

### TXT-to-PDF conversion

Document Engine now supports converting plain text (`.txt`) files to PDF. This expands the range of file formats that can be processed.

TXT files can be used like any other supported file format in the [Build API](https://www.nutrient.io/api/reference/document-engine/upstream/#tag/Build-API):

```json

{
  "parts": [
    {
      "file": "document.txt"
    }
  ]
}

```

### Half-transparent headers and footers in Word document conversion

This release adds the ability to render headers and footers as half-transparent when converting Word documents to PDF.

You can configure half-transparent header/footer rendering in two ways:

1. **Globally** — Set the `HALF_TRANSPARENT_HEADER_FOOTER` environment variable.

2. **Per request** — Use the `half_transparent_header_footer` parameter in [Build API](https://www.nutrient.io/api/reference/document-engine/upstream/#tag/Build-API) requests.

When both are specified, the API parameter takes precedence over the environment variable.

- `true` — Headers and footers are rendered as half-transparent.

- `false` (default) — Headers and footers are rendered as opaque.

```json

{
  "parts": [
    {
      "file": "document.docx",
      "half_transparent_header_footer": true
    }
  ]
}

```

### Spreadsheet print area rendering control

This release adds the ability to control whether only the print area or the entire spreadsheet content is rendered during conversion to PDF.

You can configure print area rendering in two ways:

1. **Globally** — Set the `SPREADSHEET_RENDER_ONLY_PRINT_AREA` environment variable.

- `false` (default) — Render the entire spreadsheet content.

- `true` — Render only the defined print area.

2. **Per request** — Use the `render_only_print_area` parameter in [Build API](https://www.nutrient.io/api/reference/document-engine/upstream/#tag/Build-API) requests.

### Tile rendering scale limit

This release adds the `TILE_MAX_SCALE` environment variable, which limits the maximum scale allowed for rendered tile requests. The default value is `2`. Use this option to prevent clients from requesting tiles at unexpectedly high scales. When using Web Viewer SDK with Document Engine, configure the Web SDK `tileSize` option if the default server-backed tile size of `512` pixels is too large for small pages.

### Adds support for Brotli decompression

Document Engine now supports [Brotli](https://pdfa.org/brotli-compression-coming-to-pdf/) decompression, enabling it to open PDFs that use Brotli-compressed content streams.

## Breaking changes

This release doesn’t include any breaking changes.

## Deprecations

This release doesn’t include any deprecations.

## Database migrations

This release contains a migration that modifies the `pdfs` table to address file size limits.

Previously, `byte_size` was stored as a Postgres `int4`, which tops out at ~2 GB. That cap was too low for larger PDFs, so we now store sizes in a new `bigint` column.

The migration:

- Adds a new `byte_size_big_int` column (`bigint`) for larger file sizes

- Makes the legacy `byte_size` column nullable so new rows can rely on `byte_size_big_int`

Operational note: This is a metadata-only change (no table rewrite). Postgres will take a brief AccessExclusive lock on `pdfs` while the columns are altered; lock acquisition last typically sub-seconds to a few seconds, and the change completes quickly once the lock is acquired.

## Changelog

A full list of changes, along with the issue numbers, is available [here](https://www.nutrient.io/guides/document-engine/changelog.md#1.14.0).
---

## Related pages

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