Free tool · unlimited · no account
One PDF, several bank statements. Split it.
Three months saved as a single download. A court bundle with seven statements bound inside. A council pack. A PDF is often a container, not a statement — and almost every tool downstream assumes otherwise. This finds where one statement ends and the next begins, and hands you back one PDF per statement.
Why this matters more than it looks
Ask a converter «does this statement balance?» and it checks opening balance, plus every transaction, against the closing balance. Ask the same question of a container holding four statements and it does not get a wrong answer — it gets no answer at all. The arithmetic has nothing to close against, so the tool either refuses a document that is perfectly fine, or, far worse, quietly reports a total that belongs to no account in particular.
We know how common this is because we measured it on our own corpus: 23 of 80 documents printed more than one opening balance. Not edge cases — bundles from federal courts, insolvency files, three months a bank exported as one download. It is the single most frequent reason a good statement fails a good converter.
Split it first and each piece becomes answerable on its own. Then, if you want, check whether the numbers inside actually add up.
How it decides where to cut
It reads two things the bank itself printed:
- Page numbering that restarts. A page that says «page 1 of 6» after you are already on page 9 is the start of a new document, not a continuation of the old one.
- An opening balance after a closing balance. A statement that opens where nothing closed belongs to the next statement, not this one.
Both signals live in the text layer of the PDF, so the whole thing runs in about twenty milliseconds and never calls a language model. That is not a technical detail for its own sake: it is why the tool can be free, unlimited and account-free without us quietly paying for your usage.
What it will not do. This is a reading of printed text, not a certification. On a scan with no text layer it finds nothing and says so. On an unusual layout it can miss a boundary. It leans deliberately towards saying one statement rather than inventing a split — if it is unsure, it stays quiet. And every page you upload comes back: 12 pages in, 12 pages out, with the page range written into each filename so you can check.
If you are cleaning up somebody's books
The people who hit this hardest are not one-off users. They are bookkeepers and accountants taking on a catch-up job: three years, three bank accounts, five hundred transactions, statements arriving as whatever the client managed to download. Half the files are one month, half are a year bundled together, and the first hour of the engagement goes on working out which is which.
Splitting is step one. After that, RowSure converts each deliverable statement to Excel or CSV with its status and diagnostics, then checks the opening balance plus every extracted transaction against the closing balance the bank printed. QuickBooks (QBO) and OFX are generated only after a green VERIFIED result. When a run of statements belongs to one account, it also chains them: the closing balance of one has to open the next, or a statement is missing in between. That is the check that turns a pile of PDFs into books somebody can sign off.
Credits never expire, and a single statement is $3 at launch if that is all you need.
Questions people actually ask
Is my statement uploaded anywhere?
It is sent to our server, read in memory and discarded. It is never written to disk, never stored, and never sent to any third-party service. What we keep is one number: how many statements were found. Not the file, not an amount, not your address. The privacy page spells this out.
Why is it free with no limit?
Because it genuinely costs us nothing per use — no model call, no per-page fee. Our conversion does cost money to run, so that one is metered. We would rather say which is which than invent a limit here to push you towards the paid part.
It says one statement, but I know there are more.
Then the boundaries are not in the document's text — a scan will do that, and so will a layout that never restarts its page numbering. The tool reads nothing else, so it declines rather than guessing. Splitting by hand in any PDF reader works fine in that case.
Does it work on credit card statements?
The same two signals apply, so usually yes. It does not care what kind of account it is — only whether the document prints where one period ends and the next begins.