Overview
Whenpage_chunks=True is passed to to_markdown() or to_text(), the return value is a list of dictionaries — one per page — rather than a single concatenated string. Each dictionary follows the schema described on this page.
Iterating over chunks
To quickly see the structure of each chunk, you can iterate over the list and print the keys of each dictionary:Why use page chunks?
Page chunking is the recommended approach for any pipeline that needs to process, search, or embed a PDF’s content — rather than working with one giant string, you get a structured list where each page is a self-contained unit carrying both its text and the metadata needed to make that text useful. This matters most in RAG applications, where you need to attach source information (file path, page number, document title) to every embedded chunk so that retrieved passages can be traced back to their origin. The layout data inpage_boxes adds another layer of utility — you can filter out headers, footers, and captions before embedding, or treat tables and body text differently depending on your retrieval strategy.
Rather than post-processing a flat markdown string and trying to guess where page boundaries or section headings fall, chunking gives you that structure for free, directly from the PDF’s own layout engine.
Example: Extracting page numbers and first 100 characters of text from each chunk
Chunk schema
Each item in the returned list is a dictionary with four top-level keys:metadata
Contains both document-level properties (consistent across all chunks) and page-level properties (unique per chunk).
The PDF version string, e.g.
"PDF 1.7".Document title from PDF metadata. Empty string if not set.
Document author from PDF metadata. Empty string if not set.
The application that originally created the PDF.
The application that produced or converted the PDF.
PDF date string in
D:YYYYMMDDHHmmSSZ format.Date the PDF was last modified, same format as
creationDate.Encryption method if the document is encrypted, otherwise
None.The file path of the source document as provided to
to_markdown().Total number of pages in the document.
The 1-based page number this chunk represents.
Usage example
toc_items
A list of Table of Contents entries that fall on this page. Each entry is a list in the format [level, title, page_number].
Heading hierarchy depth.
1 = top-level chapter, 2 = section, 3 = subsection, etc.The heading text as it appears in the Table of Contents.
The page number the TOC entry points to (1-based).
toc_items is an empty list [] for pages that have no TOC entries, or for documents without a Table of Contents. Always check before iterating.Usage example
page_boxes
A list of layout elements detected on the page by the layout analysis engine. Each element describes a discrete visual block — a paragraph, heading, image, table, list item, and so on — along with its position on the page.
Zero-based position of this box in the page’s layout order (reading order, top to bottom).
The type of layout element detected. See the box classes table below.
Bounding box of the element in PDF page coordinates:
(x0, y0, x1, y1). Origin is the top-left of the page. Units are PDF points (1 point = 1/72 inch).Character offsets into the page’s
text string: (start, end). Use these to slice the exact text that corresponds to this layout element.Box classes
| Class | Description |
|---|---|
text | Body paragraph or general prose |
section-header | A heading or section title |
list-item | A bullet or numbered list entry |
table | A detected table |
picture | An image or figure |
caption | A caption beneath a figure or table |
page-footer | Footer content at the bottom of the page |
page-header | Header content at the top of the page |
Usage example — extract only headings
Usage example — get bounding boxes for all images
text
The full markdown-formatted text content of the page as a single string. Headings, bold text, tables, and list items are represented using standard markdown syntax.
Markdown string for the entire page. Newlines separate logical blocks. Images that cannot be extracted are replaced with a placeholder like
==> picture [535 x 193] intentionally omitted <==.The character offsets in each
page_boxes[n]["pos"] correspond directly to positions within this string, so you can use them to precisely extract the text for any layout element.Usage example — slice text by layout element
Full iteration example
Related
| Method | Description |
|---|---|
to_markdown() | The method that produces chunks when page_chunks=True |
to_json() | Alternative export with full bounding box and layout data |
get_key_values() | Extract form field data from a PDF |
JSON Schema
The JSON schema reference for the full output of to_json(), including text, image, table, and drawing blocks with bounding boxes and metadata.
Extract JSON Guide
Working walkthrough with filtering, DataFrame export, and pipeline examples.
to_json()
Full API reference for to_json().
Get Form Data
Extracting form data from PDF as key value pairs.