Skip to main content

Overview

When page_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. PyMuPDF4LLM Chunk Schema Diagram

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 in page_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
This is the recommended approach for RAG pipelines, as it lets you attach rich metadata to each piece of content before embedding or indexing it.

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).
string
The PDF version string, e.g. "PDF 1.7".
string
Document title from PDF metadata. Empty string if not set.
string
Document author from PDF metadata. Empty string if not set.
string
The application that originally created the PDF.
string
The application that produced or converted the PDF.
string
PDF date string in D:YYYYMMDDHHmmSSZ format.
string
Date the PDF was last modified, same format as creationDate.
string | None
Encryption method if the document is encrypted, otherwise None.
string
The file path of the source document as provided to to_markdown().
integer
Total number of pages in the document.
integer
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].
integer
Heading hierarchy depth. 1 = top-level chapter, 2 = section, 3 = subsection, etc.
string
The heading text as it appears in the Table of Contents.
integer
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.
integer
Zero-based position of this box in the page’s layout order (reading order, top to bottom).
string
The type of layout element detected. See the box classes table below.
tuple[float, float, float, float]
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).
tuple[int, int]
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

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.
string
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


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.