Layout-driven · no per-bank templates
Bank statement formats, by bank
The converter does not use a profile for your bank — it reads the layout of the page. What is genuinely useful is knowing how to get a file it can read, and which statements have been tested. Both are below.
Drop your bank statement here
PDF from online banking, or an OFX / QFX export. Click to choose, or paste with Ctrl/⌘+V.
Text-based PDF up to 60 MB / 200 pages, or .ofx / .qfx
Getting the right file out of your bank
Most failed conversions are the wrong download, not a parsing problem. In rough order of how well they work:
1. OFX or QFX export
Structured data, no layout to infer, dates that cannot be misread. Look for Export, Download transactions, or a file-type dropdown offering OFX/QFX. This site converts those too.
2. The PDF download button
Take the actual download, not a copy of what is on screen. Many banks render an image in the browser viewer while the file behind the download button is a proper text PDF.
3. A CSV export
Usually fine, but bank-produced CSVs vary between exports in ways that trip up automated tools. If both CSV and OFX are offered, OFX is a fixed specification and CSV is not.
4. A scan or a photo
The only case that genuinely needs OCR. Try the download button first — it is usually there. What to do if it is not.
Statements we have tested
Nothing is listed yet. We publish a bank page only after a real statement from that bank has been parsed and its rows reconciled against the running balance the statement prints. Until then there is nothing honest to say about that bank’s layout, and swapping the bank name on a generic page is exactly the kind of content that should not exist.
You can convert your statement right now regardless — the parser reads the layout of the page rather than a per-bank profile, so most text-based statements work without ever having been seen before. The converter on the homepage reports how many rows reconciled, which is the answer to “did it work” for your specific bank.
7 bank layouts are queued for testing. If you have a statement from one of them, running it through the converter and checking the reconcile count is the whole test.
Questions about bank coverage
Does the converter need a profile for my bank?
No, and that is deliberate. It identifies rows and columns from the geometry of the page — where the text sits and how the numbers align — rather than from a per-bank template. A template that matched last year’s layout would fail silently the moment the bank changed it; the balance check fails loudly instead.
Then why list banks at all?
Because the useful information is not "does it work for Chase" but "how do I get a file it can read". Most failed conversions are the wrong download, not a parsing problem. The sections below cover that, and where we have tested a statement from a particular bank we say exactly what we found.
What does a bank page actually tell me once it exists?
Only tested facts: the date of the test, how many pages and transactions were parsed, what share of rows reconciled against the statement’s own running balance, and anything that did not work. No guesses, and no page at all for a bank we have not tested.
My bank is not listed. Does that mean it will not work?
No. Most text-based statements convert without any bank-specific knowledge. Drop yours in and look at the reconcile count in the preview: if the rows match the statement’s balance chain, it worked, whatever the bank.
What if I can only get a scanned statement?
A scan is an image and needs OCR, which cannot run well in a browser. The scanned statements page covers what to use instead — but check first whether your bank also offers a PDF download or an OFX/CSV export, because that is a much better input.