What is a QIF file?
QIF — Quicken Interchange Format — is the plain-text format Quicken used to move data in and out for decades, and it spread everywhere: Microsoft Money, GnuCash, and many banks' legacy "download transactions" options all speak it. A QIF file is a series of sections headed by lines like !Type:Bank or !Type:CCard, each containing records made of one field per line — a single-letter code followed by the value — terminated by a ^. For the full anatomy of the format, read What is a QIF file? in the Learn section, or the step-by-step How to convert QIF to CSV.
Who still has QIF files?
Anyone with years of personal or small-business finance history in Quicken or Microsoft Money (discontinued in 2009, but its data lives on), GnuCash users exchanging data with other tools, and people whose banks still offer "Quicken (QIF)" as a download format. Quicken itself dropped QIF import for bank accounts back in 2005 — which is exactly why old .qif files pile up with no easy way to open them. If you just need the transactions in a spreadsheet, converting to CSV is the fastest path.
QIF field codes, briefly
- D — Date: The transaction date, in whichever format the exporting program felt like.
- T — Amount: Signed decimal, sometimes with thousands commas; newer exports duplicate it as U.
- P — Payee: Who the money went to or came from.
- L — Category: Category, or an account name in [brackets] for a transfer.
- N — Number: The check number — or the action (Buy, Sell, Div) in investment sections.
- S / E / $ — Splits: Repeating groups: one category, memo, and amount per split leg.
The converter walks every section, tracks the active account through !Account blocks in multi-account exports, skips list sections like !Type:Cat that aren't transactions, and flattens everything into one row per transaction with a consistent set of columns — Date, Amount, Payee, Memo, Category, Number, Cleared, Account, Type, and Splits.
How to convert QIF to CSV or Excel
- Drop your .qif file above. Parsing happens on your device — the file is never uploaded.
- Check the summary: transaction and account counts, which sections the file contains, the detected date format (MM/DD vs DD/MM), and the date range.
- Preview every transaction — dates normalized to YYYY-MM-DD, split legs itemized in the Category column.
- Export as CSV for Excel, XLSX, or JSON.
Troubleshooting QIF files
What's the difference between QIF and OFX/QFX?
QIF is the older, looser format: plain text, one field per line, no amount-sign rules, no unique transaction IDs, and famously ambiguous dates. OFX (and Intuit's branded variant QFX) replaced it with a structured SGML/XML format that carries currency, account IDs, and unique transaction IDs. If your bank offers both, OFX is the more reliable download — and LegacyFile has an OFX to CSV converter for it. If all you have is a .qif, this tool is built for exactly that. You'll find the OFX to CSV converter here on LegacyFile too.
How does the converter handle QIF's ambiguous dates?
QIF never standardized dates: files contain MM/DD/YY, MM/DD/YYYY, DD/MM/YY, or the 2000s Quicken quirk "01/15'04" with an apostrophe before the year. The converter scans the whole file for evidence — any date with a day above 12 settles which position is the month — then reads every date consistently and shows the detected format in the summary. When a file is genuinely ambiguous (every day 12 or below), it assumes US MM/DD and says so in a warning instead of guessing silently.
What happens to split transactions?
A QIF split transaction (S/E/$ lines) stays as one row — the total amount in the Amount column, so your spreadsheet still sums to the real balance change — with each leg itemized in the Category cell like "Office Supplies $-600.00; Computer Equipment $-400.00" and a Splits column counting the legs. Nothing is dropped, and nothing is double-counted.
Is this QIF converter really free?
Yes — every file parses and previews free with no signup and no upload. Free exports include the first 100 transactions; a one-time $19 license unlocks unlimited exports on every LegacyFile tool.