13 tools · One-file trial
Pick the file you have. Get the format you need. Check every value before it leaves.
Start with one real document, not a polished demo. You can run free invoice or receipt OCR, pull tables from a PDF, or convert a PDF or image to Excel, CSV, JSON, or Markdown. The result opens beside the source so you can fix a split row, a wrong digit, or a missing field before export. Text-based PDF to Markdown stays in your browser. The other tools use the AI provider selected in the workspace.
Content reviewed .
Use Dynamite Docs to turn one PDF, scan, or image into reviewed Excel, CSV, JSON, or Markdown. AI reads scanned files and images, while the PDF to Markdown tool parses selectable text in your browser.
Each free tool accepts one supported file up to 50 MB without signup. Create a free account to download Excel, CSV, or JSON. PDF to Markdown can be downloaded anonymously.
Users can convert single documents without creating an account. For higher volume batches and automated exports, compare monthly processing allowances and plan limits or read how extraction and review work.
Choose an invoice or receipt tool when you need named business fields and line items. Choose a PDF or image tool when the required output is Excel, CSV, JSON, or Markdown. Each page explains its accepted file types, review steps, output limits, and common failure cases.
A handwritten Indian GST invoice and a historic German invoice can open in the same source-first workspace. Dynamite Docs infers fields and rows from each document instead of requiring one fixed invoice template. Reviewers can edit the result while the original remains visible.
AI OCR reads scanned pages and photos, then infers fields, rows and columns from the layout. The local PDF to Markdown workflow instead reads a text-based PDF inside your browser without sending the document to an AI provider or to DynamiteDocs. Invoice and receipt tools focus on purchase fields, tax, totals and repeating line items. PDF tools prepare reviewed results for Markdown, Excel, CSV or JSON.
Extract invoice data from a PDF, scan, or photo, then check every field beside the original.
Accepts PDF or image files. Run free invoice OCR on one PDF or image and review the extracted invoice fields.
Turn a native or scanned PDF into Excel rows without cleaning up a broken copy-paste.
Accepts PDF files. Convert one native or scanned PDF into an Excel workbook with reviewed rows.
Extract tables from a PDF without rebuilding every row by hand.
Accepts PDF files. Extract tables from one native or scanned PDF, review the cells and export the result.
Convert bank statements to Excel without uploading. Processed in browser RAM.
Accepts PDF or image files. Convert one bank statement into Excel-ready transaction rows for reconciliation.
Pull the merchant, tax, tip and line items from a receipt photo.
Accepts PDF or image files. Run free receipt OCR on one photo, scan, or PDF and review the expense fields.
Turn one invoice into JSON you can inspect before your code sees it.
Accepts PDF or image files. Convert one invoice into reviewed JSON for a prototype or integration sample.
Turn one PDF table into a flat CSV without retyping every row.
Accepts PDF files. Convert one PDF table into a reviewed flat CSV file.
Convert a PDF into named fields and rows, then map the JSON on your terms.
Accepts PDF files. Convert one PDF into reviewed fields and table rows for JSON mapping.
Convert a text PDF to Markdown in your browser. No upload. No AI model.
Accepts text-based PDF files. Convert a text-layer PDF into editable Markdown locally without uploading it or calling an AI model.
Turn a table photo or screenshot into real Excel cells, not an image inside a sheet.
Accepts JPG, PNG, WebP, GIF, TIFF or AVIF image files. Convert one table image, screenshot, photo, or scan into reviewed Excel-ready rows.
Convert a table image to CSV, with every row open for review first.
Accepts JPG, PNG, WebP, GIF, TIFF or AVIF image files. Convert one table image, screenshot, photo, or scan into a reviewed flat CSV file.
Read fields and tables from an image, then export reviewed JSON.
Accepts JPG, PNG, WebP, GIF, TIFF or AVIF image files. Convert one document image, screenshot, photo, or scan into reviewed fields and JSON rows.
Turn visible text in a scan, photo or screenshot into editable Markdown.
Accepts JPG, PNG, WebP, GIF, TIFF or AVIF image files. Turn one scanned page, document photo, or screenshot into editable Markdown with OCR.
Use a workbook when you need typed cells, separate result tables, filters or formulas. Review merged cells, dates, amounts and repeated page headers before download.
Use CSV for one flat table that will move into a spreadsheet, database or import job. Check section labels, subtotal rows and embedded line breaks before relying on the file.
Use JSON when software needs reviewed fields, column definitions, rows and document metadata. Your application still needs to validate types, missing values and its final object shape.
Use the local PDF converter for headings, paragraphs, lists, links and tables from a text-based PDF. Use Image to Markdown when the source is a photo, screenshot or scanned page that needs OCR.
Open AI & Processing, choose Connect Provider and follow the provider link to create a key. Several providers offer free developer allowances. Paste the key once, verify it and select a model for the document. Provider availability and limits come from the provider.
Find a provider and key or read the setup guide. Text-based PDF to Markdown can stay entirely in the browser without an AI provider.
Two PDFs can need different tools. One may contain selectable text; the other may be a stack of scanned page images. Try selecting a sentence first. If it works, local parsing may be enough for Markdown. If it does not, the page needs OCR. For a screenshot or phone photo, check focus, glare, perspective and cropped edges before upload. Missing pixels cannot be recovered later.
Now look at the content. Use Markdown for prose, Excel for tables that need formulas or typed cells, CSV for one flat import table, and JSON when software needs fields, rows and metadata. Invoices, receipts and bank statements deserve their own tools because the review checks are different. An invoice number, a handwritten tip and a running balance do not fail in the same way.
A spotless sample tells you very little about the supplier scans that arrive late on Friday. Upload a representative file with the page count, dense tables and layout changes you actually receive. Before you start, note a few controls: page count, expected rows and any printed total. For an invoice, record the supplier, full invoice number and grand total. For a bank statement, record the period and both balances.
Compare the result with the source. Start with the fields that could change a payment or break an import, then inspect page breaks and row boundaries. Recalculate totals. If glare, a fold or a crop hides a value, get a better image. Do not guess. These tools prepare a draft for review; they do not approve transactions, reconcile accounts or decide whether a document is legally valid.
Excel keeps multiple tables, dates and numeric cells. CSV is easier to import but cannot store sheets or cell types. JSON carries fields, rows and metadata, although your application still needs a versioned schema. Markdown keeps the words editable; it does not rebuild the page design.
Open the export in the program that will consume it. Check leading zeroes, ambiguous dates, currency, blank cells and decimal separators again after import. A valid CSV can still fail in a locale-specific importer. Valid JSON can still contain the wrong value. The handoff is finished when the receiving system reads the reviewed data correctly.
OCR reads pixels. It cannot restore a cropped column or a total hidden by glare. Worse, some errors look believable: 0 becomes O, 1 becomes I, or a decimal point disappears. A table can contain every visible word and still put one amount in the wrong row. Confidence scores help you decide where to look first. They do not replace source review.
Fix the input before swapping models. Photograph the page square on, use even light and keep every edge visible. Prefer the original file to a compressed chat attachment. On multi-page tables, inspect the last row of one page and the first row of the next. When several layouts recur, test the hardest example from each one before you automate the folder.
One-file tools prove the input and output. A recurring document extraction workflow also needs an owner for low-confidence fields, duplicates, missing pages, arithmetic differences and schema failures. Decide which values always need a person. Keep the source, accepted result, corrections and export together. A supplier can change a layout overnight, so test saved mappings against new versions instead of assuming the old rows still line up.
Check data handling before upload. Local PDF to Markdown reads a text-layer PDF in the browser and does not send the document to an AI provider. OCR and structured extraction may send content to the provider selected for the run. Anonymous originals stay in browser storage instead of cloud file storage. For confidential files, review the provider, privacy and retention settings first. Move to stored files, batch jobs, connected exports or the API only when the process needs them.
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.
Starter and above add stored files, batch jobs and connected exports. Compare plans and processing limits.
Anonymous originals stay in browser storage, not cloud file storage. Extraction may send document content to the selected AI provider. Read the privacy policy, data retention policy and AI provider options before using confidential or regulated documents.