Files stay local
Bank statement contents are parsed and converted inside the browser session.
StatementForge is built for sensitive financial documents: statement contents are parsed in your browser, not uploaded to a conversion server.
Bank statement contents are parsed and converted inside the browser session.
Keep source statements on your device while creating exports for review.
Billing and login use backend services, but conversion files are not uploaded.

Choose a text-based bank statement PDF, add a batch on bulk plans, or paste statement text when a PDF is locked.

StatementForge looks for dates, descriptions, withdrawals, deposits, net amounts, and balances.

Check and edit the transaction table before exporting, especially for unusual layouts or rows that need manual review.

Download CSV, XLSX, JSON, QBO, OFX, or QIF depending on the workflow you need.

No. Statement contents are processed in the browser for conversion.
The backend handles account, billing, and usage logic, not statement file conversion.
The in-browser workspace is cleared unless you have exported the data first.
It is designed for privacy-first conversion, but you should still follow your own document handling requirements.
Start with the format, privacy setup, or statement type that matches the file in front of you. Each guide opens the same converter with a more focused workflow.
Use these when you want clean rows for spreadsheets, bookkeeping cleanup, or analysis.
Create reviewed files for accounting tools that accept QBO, QIF, OFX, or CSV imports.
Parse, review, analyze, and batch-convert sensitive statement files in the browser.
Start from a bank-specific or statement-review workflow, then convert the downloaded PDF.