Formats

Every route the live app is allowed to offer.

This page lists current conversion families in plain English. A file is accepted only when the upload flow can safely handle that input and selected output.

Unsupported, corrupted, encrypted, or low-confidence files fail closed.

Accounting

Bank statement exports

Bank statement PDFs can produce Clean CSV, QuickBooks CSV, Xero CSV, Wave CSV, GnuCash CSV, QIF, OFX, or QBO when the required details are present. CSV is the default path; OFX and QBO ask for bank details.

Extraction

Receipts, invoices, screenshots

Receipts can become expense CSV. Invoices can become CSV or JSON. Screenshot tables can become CSV. These routes use OCR or image understanding only when needed and stop when confidence is too low.

Documents

Markdown and common document swaps

Supported documents can become Markdown. Provider-backed routes can handle common document swaps such as PDF, DOCX, TXT, MD, CSV, XLSX, and PPTX when the selected pair is supported.

Media

Images, audio, video, archives

Images can be converted through local or provider routes. Audio can become transcript TXT or JSON. Provider-backed media and archive outputs are shown only when that input/output pair is available.

Truth rule

Availability is not a blanket promise.

AI Converter does not claim every file, every bank, every document, every media file, or every archive will work. The app shows only relevant output choices for the file it detects, then runs a preview before paid unlock whenever the route needs server processing.

Use the preview as your quality gate.

AI Converter is built around a simple rule: inspect the sample before trusting the full export. That matters for bank statements, receipts, invoices, screenshots, and other sensitive files because automated extraction can be wrong when a scan is noisy, a table is unusual, a file is damaged, or a provider cannot safely read the source. The preview gives you an early look at columns, dates, descriptions, totals, signs, and row structure before you pay for the complete result.

For accounting workflows, compare the export with the source statement before importing it into bookkeeping, tax, lending, or compliance systems. Keep the privacy pages close too: source files are handled for the job you start, generated files have a short download window, and support requests should use job IDs rather than pasted bank, receipt, invoice, screenshot, or document contents.

A clean export is only useful when the route matches the file. Choose the most specific output available, keep the original file until you have checked the result, and use the validation notes or row preview to spot missing dates, duplicate transactions, weak OCR, wrong signs, or totals that do not reconcile. If the preview looks off, stop there instead of paying for a full export.