PDF-to-JSON API: Convert PDFs to structured JSON

Convert PDF to JSON two ways: layout-aware elements with coordinates, confidence, and page context, or document content as text, tables, and key-value pairs. Free to try with 5,000 Data Extraction API credits each month.


Try it live

See the JSON output on a sample document

Pick a sample document and inspect the raw JSON. To run it on a different PDF, open Parse Studio, which needs no signup. The playground processes the first 10 pages by default.

Two JSON shapes for two jobs

Spatial JSON returns every element with its bounds, confidence, and page. Content JSON returns the text, tables, and key-value pairs on their own. Pick whichever the next system expects.

Tables that survive the conversion

Rows and cells come back as data rather than flattened text, so invoices, forms, and reports stay machine-readable.

Automate with Zapier

Automatically extract tables from PDFs in Google Drive and save as JSON files using our Zapier integration. A no-code workflow for document-to-data processing.

Used by Lufthansa, Disney, Autodesk, UBS, Dropbox, IBM
Lufthansa
Disney
Autodesk
UBS
Dropbox
IBM

Three steps

How to convert PDF to JSON

Both routes take a PDF and return JSON in a single request.

Get an API key

Create a free account for a key: 5,000 Data Extraction credits a month for spatial JSON, or 50 Processor credits for content JSON.


Pick the JSON shape

Spatial JSON for layout and coordinates, or content JSON for text, tables, and key-value pairs.


Post the PDF and read the response

The result is JSON, ready to write to result.json or hand straight to the next system.

Choose the JSON shape

Two routes to JSON

Spatial JSON comes from the Data Extraction API and carries layout: every element with bounds, confidence, and page context. Content JSON comes from the Processor API and returns the document’s text, tables, and key-value pairs in one /build call. The Data Extraction free plan includes 5,000 credits a month; the Processor free plan includes 50.

CONVERT FROM
CONVERT TO

Security is our top priority

SOC 2 Type 2 audited

Nutrient’s infrastructure is SOC 2 Type 2 audited and GDPR compliant. See our privacy policy and security documentation for details on data handling.

HTTPS encryption

All communication between your application and Nutrient is done via HTTPS to ensure your data is encrypted when it’s sent to us.

Safe payment processing

All payments are handled by Paddle. Nutrient DWS Processor API never has direct access to any of your payment data.


Frequently asked questions

What is a PDF-to-JSON API?

Nutrient’s PDF-to-JSON API converts a PDF into machine-readable JSON with a single call. It offers two shapes: spatial JSON from the Data Extraction API, where every element carries bounds, confidence, and page context; and content JSON from the Processor API, which returns the document’s text, tables, and key-value pairs.

Which JSON output should I use?

Nutrient’s spatial JSON suits work that needs to know where content sits on the page: document analysis with spatial data, table extraction with cell coordinates, form field extraction, and document viewers or overlays. Content JSON suits straight data capture, where only the text, tables, and key-value pairs matter. Both take the same PDF: Spatial JSON comes from the Data Extraction API parse endpoint, and content JSON comes from a single Processor API /build call.

How do I extract tables from a PDF programmatically?

Nutrient returns tables as structured data rather than flattened text, so rows and cells stay intact for databases, analytics, and downstream automation. Post the PDF and read the tables from the JSON response. See the extract document elements guide for the request and response shapes.

Does it work on scanned PDFs?

Yes, Nutrient’s Data Extraction API is backed by optical character recognition (OCR), so scanned and image-based pages are read rather than skipped, in more than 100 languages, set with the options.language parameter. See the supported languages guide for the full list.

Which programming languages does the API support?

Nutrient’s APIs can be called from any language that makes HTTP requests. The Data Extraction route has shell, Windows shell, Python, and JavaScript samples; the Processor route adds Java, C# (.NET), and PHP, plus REST and a Postman collection.

Is there a free PDF-to-JSON API?

Yes, Nutrient’s Data Extraction API free plan includes 5,000 credits each month with no credit card required; the Processor API free plan includes 50. See Data Extraction API pricing for credit costs and paid plans.

What if the output needs to be Markdown instead?

Nutrient’s PDF-to-Markdown API returns the whole document as a Markdown string, which suits RAG pipelines, search indexing, and knowledge bases better than JSON. It runs on the same Data Extraction endpoint, so only the requested output format changes.

Ready to try it?

Create an account to get your DWS Processor API key and start making API calls.