Nirmion
Help Find a tool

PDF and document workbench

Export observable PDF metadata to structured JSON.

The processor reads the document Info dictionary and XML metadata stream without changing either.

One unlocked PDF containing 1 to 500 pages.10 MB combined limitOne JSON report with Info fields and XML-metadata presence and length signals.
Drop zone ready10 MB combined

Drop one PDF here

Choose one unlocked PDF. The source remains unchanged and the result downloads separately.

Files are sent only when you run the tool; no server-side job history is created.

Step 2 / configure and run

Prepare PDF Document Metadata Report

Select one source and confirm the processor is available before running this bounded operation.

Checking this processor...

No extra settings requiredNo settings are required. The operation examines the complete bounded document using one fixed rule.
Request handlingThe API processes the selected file in request memory, returns Cache-Control: no-store, and creates no server-side job history.

Product contract

Understand PDF Document Metadata Report before processing

The processor reads the document Info dictionary and XML metadata stream without changing either.

01

What you provide

One unlocked PDF containing 1 to 500 pages.

02

What you receive

One JSON report with Info fields and XML-metadata presence and length signals.

03

What to review

Custom objects and private application data outside those locations may not appear.

Workflow

From source to checked download

Use PDF Document Metadata Report on a working copy and review the separate result.

1. Select

One unlocked PDF containing 1 to 500 pages.

2. Configure

No hidden presets or inferred selections are applied; the complete supported structure is processed.

3. Verify

Open the download and verify its schema or document behavior. Custom objects and private application data outside those locations may not appear.

Worked review example

How to interpret PDF Document Metadata Report

A report can show a title, author, producer, creation date, and whether an XML packet exists.

01

Observed input

One unlocked PDF containing 1 to 500 pages.

02

Expected artifact

One JSON report with Info fields and XML-metadata presence and length signals.

03

Interpretation boundary

Custom objects and private application data outside those locations may not appear.

Example output

A concrete verification target

A report can show a title, author, producer, creation date, and whether an XML packet exists.

title: Quarterly packet
xml_metadata_present: true
xml_metadata_characters: 842

Implementation reference:PyMuPDF PDF API documentation

Common uses

When PDF Document Metadata Report is useful

Export observable PDF metadata to structured JSON.

01

Audit supplied document properties before sharing.

02

Compare metadata before and after a controlled cleanup.

03

Record producer and date fields during document QA.

Important boundary

Keep the source until review is complete.

Custom objects and private application data outside those locations may not appear.

Practical help

Questions before you run it

What does PDF Document Metadata Report actually inspect or change?

The processor reads the document Info dictionary and XML metadata stream without changing either. It processes only the supported structures found in the selected PDF and returns a separate download. It does not overwrite the source, infer missing document intent, or certify legal, archival, accessibility, privacy, or security status. Review the artifact against the original before using it in another workflow.

What limits apply to PDF Document Metadata Report?

One unlocked PDF containing 1 to 500 pages. The request is limited to 10 MB, the document to 500 pages, discovered structures to 10,000 items, and generated output to 50 MB. Password-protected files must be unlocked first. Malformed, application-specific, or unsupported PDF objects may require a specialist desktop application and manual inspection.

What should I verify after PDF Document Metadata Report finishes?

Confirm the download opens and matches the stated output, then compare page count, visible content, navigation, form behavior, and any task-specific structure with the source. Custom objects and private application data outside those locations may not appear. Keep the original until the result has been tested in the viewer, print process, records system, or downstream application where it will be used.

Document workflow

PDF Document Metadata Report with inspectable boundaries

Export observable PDF metadata to structured JSON. The processor reads the document Info dictionary and XML metadata stream without changing either. One unlocked PDF containing 1 to 500 pages.

One JSON report with Info fields and XML-metadata presence and length signals. Custom objects and private application data outside those locations may not appear. Completed downloads remain only in this browser tab for limited re-download.