> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anyformat.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Pages

> How pages work within a file and why page boundaries matter.

A file can be a single page (an image or a one-page PDF) or many pages (a multi-page PDF). **Most of the time you don't need to think about pages at all — anyformat handles them automatically.** This page covers the two situations where they do come up.

***

## Reviewing where a value came from

When you open a document, anyformat shows you the original alongside the extracted data, and highlights the exact spot on the page where each value was found. Each value also shows a **confidence indicator** — a quick signal of how sure anyformat is about it (see [Analytics & quality](/guides/workflows/analytics-quality) for what confidence means). This is how you check *why* a value was extracted, not just what it is, and correct it if it's wrong.

***

## When a value spans multiple pages

The one time pages can trip you up is when a single thing is split across a page break — for example a table whose rows continue onto the next page, or a total that's on a different page from its line items. anyformat usually stitches these together correctly. If a result looks wrong, open the document and check the highlighted source: it'll show you which page the value came from, so you can spot whether something on a page boundary was missed.

***

## A note on usage

Usage is counted per page, so a 10-page document counts as more than a 1-page one. See [Usage & billing](/concepts/usage-and-billing) for details.

***

## What's next?

<CardGroup cols={2}>
  <Card title="Usage & Billing" icon="chart-simple" href="/concepts/usage-and-billing">
    How usage is calculated based on pages and files
  </Card>

  <Card title="Schemas" icon="database" href="/concepts/schemas">
    Define the structure of the data you want to extract
  </Card>
</CardGroup>
