Document tool

QIF to CSV Converter

Convert Quicken QIF exports to clean CSV: amounts summable, categories and account types preserved, encodings handled. Never stored.

QIF CSV
PrivConvert
Privacy-first conversion
No files stored
In-memory processing
Deleted instantly
No sign-up needed

Complete the security check to begin

The oldest export format still in the wild

QIF predates OFX, predates online banking, nearly predates the web - and plenty of banks, credit unions and accounting tools still offer it as an export option, while decades of personal finance history sit in .qif files from retired copies of Quicken and Microsoft Money. The format is plain text and refreshingly simple; the tools that read it are what disappeared.

This converts it to a CSV that behaves: amounts stripped of thousands separators so they sum, payees and memos decoded correctly even from legacy encodings, categories and cleared status preserved, and a column carrying the account type when one file holds several sections. One honest caveat: QIF dates never specified day-month order, so they are passed through as written rather than silently guessed - the one place where guessing would mean corrupting data. Banks that offer OFX solve that properly.

Your financial history stays yours

A QIF export is years of transactions in one file. It is parsed here by a dependency-free text reader, entirely in memory, never written to disk, never logged, and deleted the moment your download is delivered. On the way out, text cells are neutralised against spreadsheet formula injection while amount cells are validated as pure numbers and left clean for arithmetic.

Want a ready workbook instead? QIF to Excel types the amount column numerically. Building an import pipeline? The API runs this at /api/convert/qif-to-csv.

How to Convert QIF to CSV Online

Turning a QIF file into CSV is straightforward here - upload, convert, download. Your file is processed privately in memory and deleted the instant the CSV is ready.

1
Upload your QIF file

Drag and drop your file into the upload area, click to browse your device, or paste a URL to a file hosted online. You can upload files up to 250 MB and batch convert up to 200 files at once.

2
Automatic conversion

Once uploaded, the conversion from QIF to CSV starts automatically. The process runs entirely in an isolated environment - your data never leaves the secure pipeline.

3
Download your CSV file

Your converted file is ready instantly. Click the download button to save it to your device. The file is deleted from memory immediately after download.

Why choose PrivConvert?

Converting QIF to CSV should not mean handing a stranger a permanent copy of your data. PrivConvert processes everything in memory and forgets it instantly.

Isolated sandbox

Every conversion runs in its own locked-down process with no network access, so files can never leak or interfere with one another.

No human ever sees it

Your files are handled entirely by automated code. No staff, partner or AI model ever reads, stores or trains on your data.

Zero data retention

Files are processed in volatile memory (RAM) and purged the instant your download is ready - nothing is ever written to disk, cached or backed up.

Encrypted transfers

Every upload and download is protected with TLS 1.3, so your spreadsheet cannot be intercepted on the way to the server or back to you.

QIF vs CSV - Format Comparison

FeatureQIFCSV
File extension.qif.csv
Supported by PrivConvertYes (as input)Yes (as output)
Privacy-safe conversionIn-memory, zero storage
Max file size250 MB per file
Batch supportUp to 200 files at once

Trusted by thousands of users

Professionals reach for PrivConvert when the spreadsheet they are converting is sensitive and cannot be left sitting on someone else’s server.

250 MB Max file size
450+ Conversion tools
0 sec File retention
100% Free to use

Frequently Asked Questions

What comes out?
One CSV with the columns Date, Amount, Payee, Memo, Number, Category, Cleared and Account type. Amounts are cleaned of thousands separators so they sum correctly; everything else arrives as written in the file.
Why are the dates not normalised like in the OFX tool?
Because QIF dates are genuinely ambiguous: the format never specified whether 03/04/26 is March or April - it depended on the regional settings of whatever wrote the file. Guessing silently would corrupt half the world’s statements, so dates are passed through exactly as written and the decision stays visible and yours. If your bank offers OFX, prefer it; it has unambiguous dates.
Multiple accounts in one file?
Handled. The Account type column carries the active !Type header (Bank, CCard, Cash and so on), so transactions from different sections stay distinguishable.
Will Hebrew or accented payees decode correctly?
Yes. UTF-8 is tried first, then the common legacy encodings, so files from older tools (frequently Windows-1252, or Windows-1255 for Hebrew) come through readable. The CSV is UTF-8 with a byte-order mark for Excel.
Is the file parsed safely?
QIF is plain line-oriented text and the parser is dependency-free - there is no XML, no macros, nothing executable involved. On output, text cells get the standard spreadsheet formula-injection neutralisation while amounts are validated as pure numbers.
Do you keep the statement?
No. Parsed in memory, never written to disk, never logged, deleted the moment your download is delivered.

Further Reading