> This page is for version v2025-04-21.
> For other versions, use one of these documentation indexes:
> - v2026-02-09 (default): https://docs.extend.ai/2026-02-09/llms.txt
> - v2025-04-21: https://docs.extend.ai/2025-04-21/llms.txt
> - v2024-12-23: https://docs.extend.ai/2024-12-23/llms.txt

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.extend.ai/llms.txt
> Use this file to discover all available pages before exploring further.
>
> ## API version
> The current API version is `2026-02-09`, served at the site root (no version prefix in URLs).
> If this page URL contains `/2025-04-21/` or `/2024-12-23/`, you are reading an older API version.
> Prefer the current docs at https://docs.extend.ai/llms.txt unless the user explicitly needs that older version.
> Do not treat older-version pages as the source of truth for new integrations.

# Parse output metadata: page rotation, original dimensions, and file type

Parse runs now include a **`metadata`** object on `output`, alongside `chunks`:

* **`originalMimeType`** / **`finalMimeType`** — the file's media type before and after any format conversion.
* **`pages`** — an array of per-page entries, each with:
  * **`number`** — the page number, matching `metadata.page.number` on that page's blocks.
  * **`rotationApplied`** — degrees Extend rotated the page clockwise to make it upright. `0` if detection ran and the page was already upright, `null` if rotation detection was disabled for the run.
  * **`originalPageWidth`** / **`originalPageHeight`** — the file's true page size, independent of rendering resolution.
  * **`dpi`** — the DPI that `boundingBox`/`polygon` coordinates on the page are scaled to; multiply the original dimensions by `dpi / 72` to bring them into that same coordinate space.

`metadata` is `null` for parse runs that completed before this field was introduced, and `pages` is `null` when page-level metadata isn't available.

Bounding boxes and polygons are always returned in the corrected (upright) frame. To draw a citation or highlight on your own copy of the original file, use these fields to map coordinates back — see [Reconciling coordinates against your original file](/2026-02-09/parsing/response-format#reconciling-coordinates-against-your-original-file).