Local conversionNo statement uploadEditable reviewCorrect rows before exportScanned-page fallbackLocal OCR on the first 8 pages
Built around a visible result
The sensitive conversion path stays local
StatementForge does not hide extraction behind a black box. The transaction table, warnings, totals, and destination format stay visible so you can decide whether the result is usable.
The PDF and pasted statement text are read in the browser
OCR text, transaction rows, edits, amounts, and balances stay in the workspace
CSV, XLSX, JSON, QBO, OFX, and QIF contents are generated locally
Hosting, authentication, billing, and anonymous product events use separate network requests
A review-first workflow
From source document to a file you can inspect.
01
Choose
Select a statement PDF or use the safe sample.
02
Extract
Read its text layer or run limited local OCR.
03
Review
Check and correct the transaction table.
04
Export
Generate CSV from the reviewed rows.
Honest operating limits
Financial files still deserve a human check.
Statement contents are processed in your browser and are not uploaded to StatementForge servers.
Account and billing features use a backend, but conversion files stay local.
You should still download and store exports according to your own privacy and bookkeeping process.
Where this workflow fits
Use the converter for a defined job.
Personal statements
Convert PDFs while keeping source files on your own computer.
Client work
Reduce exposure when handling financial documents from clients.
Internal finance teams
Create structured exports without sending PDFs to a generic conversion service.
Practical questions
Privacy questions
Are bank statements uploaded to StatementForge?
No. Statement contents are processed in the browser for conversion.
What does the backend do?
The backend handles account, billing, and usage logic, not statement file conversion.
What happens when I close the tab?
The in-browser workspace is cleared unless you have exported the data first.
Can I use it for sensitive documents?
It is designed for privacy-first conversion, but you should still follow your own document handling requirements.