All tools

PDF Metadata, Page Size & Outline Reader

DataPopular

Read a PDF's metadata (title, author, dates, version, page count, encryption), every page's size and orientation, and its bookmark outline, without rendering it

Was this tool helpful?
pdfmetadatadocumentinfopage-sizedimensionsorientationoutlinebookmarkstoc

About PDF Metadata, Page Size & Outline Reader

Drop in a PDF and inspect it three ways without opening a viewer. Metadata reads the title, author, subject, keywords, creator, producer, creation and modification dates, page count, PDF version and encryption flag from the file's trailer and info dictionary. Page sizes lists each page's width, height, rotation and orientation from the page tree and recognises common paper sizes such as Letter and A4, which is the quick way to find the one landscape page in a long report. Outline / bookmarks walks the bookmark tree and lists every entry's title, nesting level and target in document order. All three use targeted parsing rather than a full rendering engine, so they stay fast on large files and never extract page text. XMP metadata is not read, and files using unusual compressed cross-reference streams can return partial results. The file never leaves your browser.

How to use PDF Metadata, Page Size & Outline Reader

  • 1.Drop a PDF file (or click to browse) to read its title, author, subject, keywords, creator, producer, creation/modification dates, page count, and PDF version.
  • 2.Check the Encrypted badge to quickly see whether a PDF is password-protected before trying to open it in another tool.
  • 3.Use the REST API or an SDK to batch-read metadata across many PDFs, e.g. to build an index of a document archive.
  • 4.Switch to Page sizes to spot mixed paper sizes or rotated pages before printing or merging documents.
  • 5.Use Outline / bookmarks to see a PDF's table of contents structure, or confirm that an exported PDF kept its bookmarks.

Frequently asked questions

Does this render or extract the actual page content?
No, it only reads the trailer and Info dictionary (and the page tree's /Count for page numbers): it never decodes page content, so it works even on very large PDFs and stays fast.
Is my PDF uploaded to a server?
In the browser tool, no: the file is read and parsed entirely client-side. The REST API and SDKs do process the bytes you send them, same as any other API call.
Why are some fields missing for my PDF?
Not every PDF sets every Info field, and some modern PDFs store metadata only as XMP (embedded XML) rather than the classic Info dictionary, which this tool does not parse.
Does it work on PDFs with compressed cross-reference streams?
It handles classic trailers directly, and falls back to scanning for an Info-shaped object when there's no classic trailer, which covers most PDFs in practice, but very unusual or hand-crafted files may return partial results.
Why does a PDF show no outline?
Many PDFs, especially scanned documents and simple exports, have no /Outlines bookmark tree at all. The Outline mode reports that rather than guessing headings from page content.
Why did an old Utilix tool page redirect me here?
Utilix merged several single-purpose tools into the PDF Metadata, Page Size & Outline Reader. Each old URL now opens this page with its mode preselected (via ?mode=<old-tool-slug>), so bookmarks and links keep working. The old tools' REST endpoints, Node.js and Python SDK functions, and MCP tools are unchanged.