OFX to CSV — Convert Bank Statements to CSV Online Free
Convert OFX/QFX bank statements to CSV spreadsheets. Extract all transactions with dates, amounts, payee, and memo. Private — your financial data never leaves your device.
OFX files are the universal export format for bank accounts and credit cards — every major bank produces them — but the format is an idiosyncratic mix of an SGML text header and an XML body that no spreadsheet can read directly. The header carries metadata (OFXHEADER:100, DATA:OFXSGML, VERSION:102), and the body is a deeply nested XML structure with transaction blocks inside statement wrappers inside message-set containers. No consumer tool reads this format except personal finance applications like Quicken and GnuCash. The OFX to CSV tool bridges that gap: paste your bank statement, get a CSV spreadsheet you can open in Excel, Google Sheets, or Numbers.
The converter extracts three layers of information. First, account metadata: the account number, the bank routing number, and the currency code. Second, every transaction: the date, the type (debit or credit), the amount, the payee name, the memo line, and the unique FitID assigned by the bank. Third, a summary line confirming the total number of transactions extracted. The output is a standard CSV with a header row, properly escaped fields, and a comment block at the top for account context.
The privacy model is the key design decision. Financial data is the most sensitive category of personal information — more sensitive than photos, more sensitive than location history. Every OFX-to-CSV converter that runs on a server is a potential data breach waiting to happen. This tool runs entirely in your browser. The OFX content is read by the FileReader API, parsed by JavaScript string operations, and displayed as output. No HTTP request is made after the initial page load. No data is stored in localStorage, IndexedDB, or any cache. Close the tab and the bank statement is gone from memory. That is the minimum viable privacy guarantee for a financial data tool, and it is the guarantee this tool makes.
How to use
Export the OFX file from your bank
Log into your online banking portal and find the export/download menu. Most banks label the OFX option as 'Microsoft Money', 'Quicken', 'OFX', or 'QFX'. Download the file and open it in a text editor — OFX files are plain text with an SGML header followed by XML content.
Paste the OFX content
Copy the entire file content (including the header lines like `OFXHEADER:100`) and paste it into the input area. The converter handles both bank account statements (`BANKMSGSRSV1`) and credit card statements (`CREDITCARDMSGSRSV1`).
Download the CSV
The converter extracts the account identifier, currency, and bank ID, then outputs every transaction with date, type (DEBIT/CREDIT), amount, payee name, memo, and unique FitID. Download as a `.csv` file and open in Excel, Google Sheets, or Numbers.
Frequently asked
What is OFX/QFX?
OFX (Open Financial Exchange) is the standard format for exchanging financial data between banks, brokerages, and personal finance software. It has been in use since 1997 and is supported by virtually every North American bank. QFX is Intuit's proprietary extension used by Quicken and QuickBooks — it follows the same structure and is handled identically by this converter.
Is my financial data safe?
Yes. All processing runs entirely in your browser using JavaScript string operations. Your bank statement data is never uploaded to any server. The page works offline after the initial load, and nothing is persisted between sessions — not in localStorage, not in cookies, not in any cache. Close the tab and the data is gone.
Does it support investment accounts?
The parser handles checking, savings, and credit card accounts. Investment transaction types (buy/sell stock, dividend, interest) are not parsed because they use a fundamentally different XML structure with different tag names and semantics. Use Quicken or a dedicated investment tracker for brokerage OFX files.
What about UTF-8 or non-ASCII characters?
OFX files typically use US-ASCII or Windows-1252 encoding for compatibility with legacy banking systems. The converter works with the text as-is. If you see garbled characters in payee names, the file may have been exported with the wrong encoding — try re-exporting or using the Charset Fixer tool on the text before conversion.
How does the date formatting work?
OFX dates are in `YYYYMMDD` or `YYYYMMDDHHMMSS` format (e.g. `20240115000000`). The converter normalizes them to ISO 8601 `YYYY-MM-DD` format for compatibility with spreadsheet software. Times are discarded because the date is typically sufficient for personal finance analysis.
Limitations
- No investment account supportThe converter handles checking, savings, and credit card statements only. Investment OFX files use different XML structures (INVSTMTTRN, SELLSTOCK, BUYSTOCK) that this parser does not recognize.
- No multi-currency conversionThe currency code (CURDEF) is extracted and displayed in the header comment but not used for conversion. Foreign-currency transactions keep their original amounts. Use a separate currency converter for cross-currency analysis.
- No OFX 2.x supportOFX 2.x uses pure XML without the SGML header that OFX 1.x uses. The parser expects the SGML-style header with `OFXHEADER` lines. If your file starts directly with `<OFX>` without a header, it may still parse correctly, but header metadata will be missing.
Platform notes
- macOS
- Most Mac banks export OFX through their web portals. Quicken for Mac exports QFX natively. The file extension is usually `.ofx` or `.qfx` — both open as plain text in any text editor.
- Windows
- Microsoft Money (discontinued but still supported by many banks) and Quicken for Windows are the primary OFX consumers on Windows. Even without these applications installed, your bank's website can export OFX files for download.
- Linux
- GnuCash and HomeBank support OFX import. For CLI processing, `ofx2csv` (pip) provides similar functionality, but the browser tool is private by default — no need to install Python packages or trust third-party code with your financial data.
- Web
- Runs entirely in the browser. Financial data is never transmitted to any server. This is the fundamental privacy guarantee — your bank statement is read by your browser's FileReader API and never leaves your device.