free · in-browser · no upload
Drop your OFX file. We'll convert it to CSV right here in your browser, your file never leaves your device.
Select your file here to get started
or drop your file here.
Accepts .ofx
How it works
Click the dropzone above or drag a OFX from your desktop. Files of any size, there's no upload, so there's no upload limit.
The conversion runs entirely in this tab using JavaScript and WebAssembly. Your file never touches our servers, we don't have any.
Get your CSV the moment the conversion finishes. Convert another, or close the tab.
Your file is never uploaded. The entire conversion runs in your browser using WebAssembly. We can't see what you convert because we have no server to see it.
Server converters cap free users at 1-2 GB and gate larger files behind a paid plan. Since nothing uploads, our limit is whatever your browser can handle.
No account required. No watermark on the output. No queue. Drop a file, get a converted file.
Why convert OFX → CSV
OFX is the format every US bank exports for Quicken/QuickBooks, but if you're doing your own analysis in a spreadsheet, categorizing spending, tracking net worth, building a budget, CSV is what you need. OFX → CSV pulls transactions, dates, amounts, and payee strings into a flat sheet you can sort and filter without specialty software.
You downloaded a year of statements from Chase as .ofx files (one per month). You want one big CSV to see total spending per category. Drop each OFX in turn (or batch your statements into one OFX), get a CSV with date, payee, amount, and account. Open in Sheets, autocategorize with text-match formulas.
Negative amounts vs positive amounts seem reversed.
OFX uses 'TRNAMT' with a sign that varies by institution. Most banks make purchases negative and deposits positive; some flip that. Our CSV preserves the bank's sign exactly. If amounts look reversed for your needs, multiply the amount column by -1 in your spreadsheet.
Memo or check-number fields are missing.
Banks vary wildly in what optional OFX fields they populate. We include MEMO, CHECKNUM, REFNUM, FITID when present and leave them blank when the bank didn't include them. Check your bank's export options for richer data.
Encoding looks broken (accented characters showing as garbage).
Older OFX 1.x files use ASCII or Windows-1252. We auto-detect and convert to UTF-8 in the CSV output. If you still see broken characters, your OFX file was probably saved in an encoding we couldn't detect, open it in a text editor, save as UTF-8, re-run.
Formats involved
OFX is the standard file format banks use to export account history. Created in 1997 by Microsoft, Intuit, and CheckFree, it carries transactions, balances, and account metadata in XML. Quicken, GnuCash, Tiller, Money in Excel, and most personal-finance apps import OFX directly.
How to open
Quicken, GnuCash, Moneydance, Tiller, most accounting software. Plain-text editors can view the XML structure.
CSV is plain text, one row per line, fields separated by commas. The simplest possible tabular data format, which is exactly why it remains the most portable: every spreadsheet, database, programming language, and analytics tool reads CSV. Tradeoffs: no formulas, no formatting, no multiple sheets, and various edge cases around quoting fields that contain commas or newlines.
How to open
Excel, Google Sheets, Apple Numbers, LibreOffice Calc, any text editor, every database import wizard, every programming language with one line of code.
You may also need
Related tools
FAQ
Yes. No signup, no watermark, no daily file count limit. Every conversion runs in your browser, your file never touches our servers because there are no servers.
Nowhere. The conversion runs entirely in your browser using JavaScript and WebAssembly. Your file is never uploaded to our servers. We don't have any servers handling files, there's nothing for us to log, store, or accidentally leak.
Whatever your browser can hold in memory. Practically, this means a few hundred MB on most computers, significantly larger than the 1-2 GB caps that server-upload converters charge for. Very large files (multi-GB) may require closing other browser tabs first.
Bank statements imported into personal-finance software. Universal tabular data interchange. The most common reason to convert is compatibility, CSV works in places where OFX doesn't, or vice versa.
Quicken, GnuCash, Moneydance, Tiller, most accounting software. Plain-text editors can view the XML structure.
Once the page is loaded, the conversion itself runs entirely offline. The first time you use a tool, your browser downloads the conversion library (a one-time cache). If you reload while offline, the page won't load, but you can install the site as a Progressive Web App for full offline use.
Single file at a time for now. Batch conversion is on the roadmap, for now, drop one file, download the result, then convert the next.
