You've got a .dbf file and none of the software that normally opens one — dBase, FoxPro, Visual
FoxPro — is installed anywhere you have access to. Maybe it's data recovered from an old system,
a shapefile's attribute table from a GIS export, or a table pulled from a retired point-of-sale
application. Here's how to get it open and into a spreadsheet without installing decades-old
database software.
Why you can't just open it in Excel or a text editor
A .dbf file is binary, not text — unlike CSV, BAI2, NACHA, or IIF, there's no readable
structure to glance at in Notepad. A 32-byte header tells a reader where the schema ends and how
big each record is, a field descriptor table defines the columns, and every row after that is a
fixed-width binary block with no delimiters. Renaming it to .csv just gets you an Excel error
or a wall of unreadable characters — Excel has no idea how to parse a DBF header. For the full
breakdown of the format, see What is a DBF file?
Convert DBF to CSV in your browser
The free DBF to CSV converter on LegacyFile parses the binary structure directly:
- Drop your .dbf file into the converter. Parsing happens entirely on your device — the raw file bytes are never uploaded anywhere.
- It reads the header and field descriptors to know exactly what columns exist, their types, and their widths — building the schema from the file itself rather than assuming one.
- It decodes every field type — Character, Numeric, Date, Logical, and FoxPro's binary Integer type — into readable values, including correctly parsing the DOS/Windows-era encoding for accented or special characters when the file's code page byte identifies it.
- It keeps deleted records, flagged. DBF doesn't actually remove a record on delete — it just marks it. The converter surfaces that as a "Deleted" column instead of silently hiding rows you might still need to see.
- Check the summary and preview, then export CSV, XLSX, or JSON. The CSV/XLSX opens directly in Excel, Google Sheets, or Numbers.
About memo fields
If your table has Memo (M) fields, you'll see [memo] in that column instead of the actual text.
That's not a bug — memo text isn't stored in the .dbf file at all. It lives in a separate
companion file (.dbt for dBase, .fpt for FoxPro) that has to be present alongside the main
table for any reader to resolve it, and this converter only works with the single file you drop
in. If you need that text, you need the companion memo file too.
What if my table's characters look wrong?
DBF encodes text according to a code page declared in the header — but plenty of real-world DBF files leave that byte blank or use one this converter doesn't specifically recognize as Windows ANSI. When the file actually contains non-ASCII bytes and the code page isn't recognized, the converter flags it with a warning so you know to double-check accented or special characters rather than assuming they're right. It never fails or refuses to convert the file over this — you still get every row, just with a heads-up about that one column's reliability.