Skip to main content

Private browser tool

PDF to JSON

Export PDF to JSON with extracted page text, page dimensions and optional text-item coordinates. Choose the detail you need and download a structured report built from the PDF’s existing text.

Preparing the interactive workspace…

Your document processing stays in your browser.

Page data for inspection and development

Inspect PDF text and positions as structured data

This export describes what the PDF text extractor can read, rather than interpreting the document as an invoice, database or spreadsheet. Each page has a page number, dimensions, rotation and text. Optional item details help inspect coordinates and font identifiers, but they are not semantic labels or guaranteed reading order.

1

Choose export detail

Set text-position and metadata options before selecting the file. These settings determine which additional fields the conversion includes.

2

Select a readable PDF

Choose a text-based document. Scanned page images do not gain recognized words in this workflow.

3

Inspect the JSON preview

Review page text and item positions, especially on rotated or multi-column pages. The report includes source name and size locally.

4

Download and validate your use

Save the JSON and parse its fylvexa.pdf-json.v1 structure in your own workflow. Check required fields and test against representative documents.

Formats, limits and tradeoffs

Accepts one PDF up to 150 MiB without an explicit page-count cap. Output includes all pages and optional standard metadata information.

No OCR, invoice-field extraction or table-cell inference is performed. Positions describe PDF text items and may need coordinate interpretation. Metadata retrieval can return null when unavailable.

When this tool helps

Inspect extractable text

Check whether a document actually contains readable text before designing another extraction workflow.

Investigate a layout issue

Use text positions and font identifiers to inspect how words are stored on a page.

Create a page-based dataset

Use the exported page records as a reviewed input to your own script, with source traceability.

Troubleshooting

Page text is empty
The page may be image-only or use text that cannot be extracted correctly. Try a suitable OCR workflow first.
I expected named invoice fields
The export is page and text-item data. Semantic field extraction needs another reviewed workflow.
Privacy

Process on your device

PDF parsing and JSON assembly run in the browser. The PDF, metadata and extracted text are not uploaded. The downloaded JSON deliberately includes local source-file information.

Browser-first
Browser workflow
No desktop app
Frequently asked questions

PDF to JSON FAQ

Select a question to view the answer.

No. It focuses on pages, extracted text and optional metadata and text-item details.

No. It uses the text already present.

Yes. Disable text positions before conversion.

Yes, in the local report’s source object. It is not sent as a processing upload.