{"version":"2.1.242","anchor":"pdf-reads-return-the-document-and-page-images","canonical_anchor":"pdf-reads-return-the-document-and-page-images","heading":"PDF reads return the document and page images","tier":"notice","area":"File Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/pdf-reads-return-the-document-and-page-images","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### PDF reads return the document and page images\n\nReading a PDF now returns the document itself plus one image per page.\n\n**What**\n\nReading a PDF now returns the actual file as a base64 document block, and page extraction returns one image block per page instead of a summary line. A page that fails to render falls back to a placeholder for that page only.\n\n**Details**\n\n- The document block is `{ type: \"document\", source: { type: \"base64\", media_type: \"application\/pdf\" } }`, included only when base64 data is present.\n- A failed page yields text saying it \"could not be processed as an image\"; the other pages still come back.\n- Re-reading the same file path carries base64 data and already-extracted pages forward from the previous result.\n- Page ranges are validated up front: formats like `1-5`, `3` or `10-20` are accepted, and a range exceeding the per-request page maximum is rejected.\n\n**Evidence**\n\n`could not be processed as an image`\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}