What Is an OFX File? Format, Uses, and Converters

Sooner or later, anyone who downloads transaction data from a bank runs into a file ending in .ofx. Double-click it and nothing useful happens: Excel refuses to lay it out in rows, and your operating system may not even know which program to suggest. This guide explains what an OFX file actually is, how the format works under the hood, how it relates to QFX and QBO, and the fastest ways to open or convert one.

OFX, Defined

OFX stands for Open Financial Exchange. It is a structured, plain-text format for moving financial data (transactions, balances, account details) between banks and the software that needs to read them. The standard was created in 1997 by Microsoft, Intuit, and CheckFree, who merged their competing formats into a single specification so that any bank could talk to any personal finance program without a custom integration. Before OFX, every bank and software pairing needed its own export format, which meant most pairings simply did not work together at all.

OFX was designed to do two jobs. The first is the one most people meet: a downloadable file format. When your bank's statement page offers a "Download" menu with options like OFX, QFX, or QBO, each choice produces a file built on the OFX specification. The second job is a direct-connect protocol: programs like Quicken and the old Microsoft Money used OFX over the wire to fetch transactions from the bank automatically, without any manual downloads.

The specification evolved through the 2000s and 2010s under an industry consortium, and in 2019 stewardship of the OFX standard passed to the Financial Data Exchange (FDX), the body that now promotes API-based bank data sharing. FDX continues to maintain OFX, which is why the format still works today even as newer connection methods emerge.

Where You Will Encounter OFX Files

• Bank download pages: Many banks list OFX (sometimes labeled "Money" or "Other financial software") alongside CSV and PDF in their export menus.
• Accounting software migrations: Moving transaction history between tools like GnuCash, Xero, Quicken, or QuickBooks often goes through an OFX export and import.
• Microsoft Money era archives: Money leaned heavily on OFX, so old backup folders from that era are often full of .ofx files containing years of transaction history.

OFX 1.x vs 2.x

There are two generations of the OFX format, and the difference trips up a lot of people (and a lot of parsers). The original versions, OFX 1.0 through 1.6, are based on SGML rather than XML. The file starts with a block of plain key and value header lines, and the data fields that hold a single value have no closing tags. That looks broken if you are used to XML, but it is valid SGML. A minimal OFX 1.x file looks like this:

OFXHEADER:100
DATA:OFXSGML
VERSION:102
SECURITY:NONE
ENCODING:USASCII

<OFX>
<BANKMSGSRSV1>
<STMTTRNRS>
<STMTRS>
<CURDEF>USD
<BANKTRANLIST>
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260709120000[0:GMT]
<TRNAMT>-42.50
<FITID>2026070900142
<NAME>COFFEE ROASTERS LLC
<MEMO>Card purchase
</STMTTRN>
</BANKTRANLIST>
</STMTRS>
</STMTTRNRS>
</BANKMSGSRSV1>
</OFX>

Notice that container elements like STMTTRN close normally, but value fields like TRNAMT and FITID just run to the end of the line. Starting with OFX 2.0, the format switched to proper XML: the header became an XML declaration plus a processing instruction, and every tag must be closed. The same transaction in OFX 2.x looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<?OFX OFXHEADER="200" VERSION="211" SECURITY="NONE"
      OLDFILEUID="NONE" NEWFILEUID="NONE"?>
<OFX>
  <BANKMSGSRSV1>
    <STMTTRNRS>
      <STMTRS>
        <CURDEF>USD</CURDEF>
        <BANKTRANLIST>
          <STMTTRN>
            <TRNTYPE>DEBIT</TRNTYPE>
            <DTPOSTED>20260709120000</DTPOSTED>
            <TRNAMT>-42.50</TRNAMT>
            <FITID>2026070900142</FITID>
            <NAME>COFFEE ROASTERS LLC</NAME>
            <MEMO>Card purchase</MEMO>
          </STMTTRN>
        </BANKTRANLIST>
      </STMTRS>
    </STMTTRNRS>
  </BANKMSGSRSV1>
</OFX>

The field names and the overall structure are identical in both generations. In practice, many banks still generate OFX 1.x files (the header line VERSION:102 is a common sight), so any tool that claims OFX support needs to handle both the SGML and XML styles. Good converters, including CapyParse's free tools, read either one without complaint.

OFX vs QFX vs QBO

OFX has two well-known descendants, and both come from Intuit. QFX is Intuit's licensed flavor of OFX for Quicken (marketed as Web Connect for Quicken), and QBO is the flavor QuickBooks uses for its Web Connect import. Inside, both are OFX files with the same transaction structure you saw above, plus a handful of Intuit-specific fields (such as a bank identifier tied to Intuit's licensing program) that Quicken and QuickBooks check on import.

This family relationship has a practical consequence. If you are hunting for a QFX to OFX converter, the payload is usually already generic OFX: renaming the extension from .qfx to .ofx is often enough for software that reads plain OFX. Going the other direction (OFX to QFX, or either format to QBO) is harder, because Quicken and QuickBooks expect those Intuit-specific fields to be present and valid, so a simple rename frequently gets rejected. That direction genuinely needs a converter that rebuilds the file.

A useful rule of thumb: OFX is the open standard, QFX is OFX dressed for Quicken, and QBO is OFX dressed for QuickBooks. For a deeper look at how these formats compare with CSV, including a full feature table and import advice, see our guide QBO vs OFX vs CSV: Pick the Right Format.

Inside an OFX File

Every OFX statement file has the same skeleton: a signon block identifying the bank, an account block with the routing number, account number, and account type, and then a transaction list where each entry is wrapped in STMTTRN tags. The fields inside each transaction are where the real value lives:

Beyond the transaction list, an OFX statement also carries a currency code (CURDEF), the bank's routing and account numbers, the account type (checking, savings, or credit card), and a closing balance block with an as-of date. That context travels with the file, so importing software knows exactly which account the transactions belong to without you telling it.

Two of these fields explain why accountants prefer OFX over CSV when both are available. FITID gives every transaction a permanent identity, so importing the same file twice does not create duplicate entries. And DTPOSTED uses one fixed date layout, so there is no risk of software reading 05/04 as May 4 when the bank meant 5 April. CSV files carry neither guarantee.

How to Open an OFX File

Because OFX is plain text, any text editor can open it: Notepad on Windows, TextEdit on Mac, or an editor like VS Code. Right-click the file and choose "Open with" to pick the editor, since double-clicking often does nothing or launches whatever finance software happens to be installed. A text editor is the quickest way to confirm what is inside a mystery file, check the date range, or see which account it belongs to. It is not a practical way to work with the data, though, since hundreds of transactions wrapped in markup are painful to read line by line.

Excel does not work. Excel expects delimited rows or a spreadsheet format, and OFX is neither, so opening the file directly dumps raw tags into column A. If your goal is a proper spreadsheet, you need a conversion step first. We cover the full walkthrough (including what goes wrong and why) in How to Open an OFX File in Excel.

Accounting software imports OFX natively. QuickBooks Online, Xero, GnuCash, and most bookkeeping tools accept OFX uploads and map the fields automatically. The notable exception is Quicken, which insists on its licensed QFX variant. If you just want to see your transactions in rows and columns right now, the fastest route is the free browser-based converter below: it shows a preview instantly, with no install and no account.

How to Convert an OFX File

CapyParse offers two free tools for the most common conversion paths, and both run entirely in your browser. Your file is never uploaded to any server, there is no signup, and both tools read OFX 1.x (SGML), OFX 2.x (XML), and QFX files:

• OFX to CSV: Use the free OFX to CSV converter to flatten the file into clean rows with date, description, amount, and type columns, ready for any spreadsheet or import tool.
• OFX to Excel: Use the free OFX to Excel converter to get a native .xlsx workbook that opens directly in Excel with no import wizard.

Need to go the other way and build an OFX file from spreadsheet data? That takes a generator rather than a simple converter, because valid OFX needs FITIDs and correctly formatted dates. See How to Convert CSV to OFX for that workflow.

OFX vs CSV: An Honest Comparison

Neither format is simply better; they solve different problems. OFX carries unique transaction IDs, standardized type codes, unambiguous dates, and account metadata, which makes it the safer choice for importing into accounting software. CSV carries none of that, but it opens in every spreadsheet, script, and reporting tool on the planet, and it is trivially easy to filter, edit, and pivot. A sensible workflow keeps both: import the OFX into your accounting system so duplicate detection works, and keep a CSV copy for analysis and client reporting.

When OFX Is Not an Option

OFX only helps when your bank actually offers it. Plenty of banks provide no OFX download at all, and even the ones that do usually limit it to a short recent window: the last 90 days, the current quarter, or whatever the online banking session exposes. Anything older lives in the statement archive, and statement archives are PDFs. The same is true for closed accounts, paper statements you have scanned, and documents a client emails you.

In those cases no OFX tool can help, because there is no OFX file to convert. What you need is a way to get the transactions off the PDF itself. That is exactly what the CapyParse bank statement converter does: upload a PDF statement (digital or scanned), review the extracted transactions in an interactive preview, and export CSV, Excel, or QBO. The end result is the same clean, import-ready data you would have gotten from an OFX download, even when the bank never offered one.

Frequently Asked Questions

Related Articles