01
Infer the structure
The model separates document fields, repeating rows, totals, and notes based on the file in front of it.
Dynamite Docs extracts fields and tables from a PDF, keeps the values available for source review, and exports JSON with column definitions, rows, and document metadata.
The download is a product export, not your application schema. Validate required fields, identifiers, dates, decimal precision, arrays, and null handling before using it in code.
The full workflow
Check the proposed fields against the source, correct a value, then export the reviewed structured PDF JSON.
Dynamite Docs01
The model separates document fields, repeating rows, totals, and notes based on the file in front of it.
02
The source remains visible while you edit cells, rename columns, inspect warnings, and mark the result reviewed.
03
Download structured PDF JSON, or move a recurring workflow into Google Sheets, Drive, webhooks, or the API.
Dynamite DocsChoose the AI route
Open AI & Processing, choose Connect Provider, and pick a provider. The setup screen links to that provider's key page. Create a free key where the provider offers one, paste it into Dynamite Docs, verify it, then select a model for the run.
Your provider key is encrypted before it is stored.
Switch between hosted, own-key, privacy-restricted, and local models.
The same source-first review screen works whichever route you choose.
Use PDF to JSON when a report, operational log, or mixed-content PDF needs to be transformed into structured JSON objects with document metadata and table row arrays. Start by establishing your application schema requirements: required properties, expected array shapes, and explicit null-handling rules.
During review, cross-check named header fields and table boundaries against the original pages. Ensure that numbers, dates, and identifiers preserve their correct data types, that wrapped descriptions do not fragment rows, and that optional fields are normalized consistently across extractions.
Choose the PDF Table Extractor when table recovery is the sole objective without nested metadata. Use Invoice to JSON for commercial supplier invoices with tax, vendor, and line-item hierarchies. Use PDF to CSV for flat database table imports. For automated software delivery, integrate directly with our REST API using saved extraction schemas.
The 28-day Free trial includes 25 page-equivalents per month shared by hosted and own-key processing, 5 hosted pages per document, and 5 documents per day. Anonymous trials have separate daily limits.
No. Plain text extraction follows reading order. This tool tries to identify named fields, data types, tables, and repeating records that software can use.
The download contains column definitions, a rows array and document metadata. Map those values into nested objects if your application needs a different structure.
Use a preset or saved schema in the workspace, then validate each result before it reaches downstream code.
Use a mapping and validation layer. Translate reviewed columns and metadata into your own versioned contract, reject missing or unexpected fields, and send failures to an exception queue. This protects consumers when layouts or inferred field names change.
Treat money with decimal-safe rules, preserve currency separately and normalize dates only after confirming the source format. Keep account numbers, reference codes and other identifiers as strings so leading zeroes and punctuation are not lost.
Starter and above add stored files, batch jobs and connected exports. Email intake requires Pro or Scale. File and processing limits depend on your plan.
Compare batch plansCan we save optional cookies?
Essential cookies keep you signed in. With your permission, optional analytics cookies and masked session replays help us understand usage and diagnose errors. Privacy policy. Change your choice anytime in Cookie settings.