How to open a DBF file
A .dbf file is a table from the dBase family of databases — dBase, FoxPro, Visual FoxPro, Clipper — still produced by accounting packages, GIS software, point-of-sale systems and government exports. Double-clicking it often gets you nothing useful: DBF is a binary format, and most spreadsheet programs understand only part of it.
Free for personal use. Nothing to install. The file is parsed in your browser and never uploaded. Windows version — 3.5 MB, no installation: details. Organizations: license.
What a DBF file actually is
A DBF is a header, a list of field definitions, and then records of identical length, one after another. That layout is what made it fast in the 1980s: the position of any record is a multiplication away. It also means every character occupies exactly one byte, long text lives in a separate memo file (.fpt or .dbt), and a record is never really removed, only flagged.
Those four properties — one-byte text, external memo, deletion flags, several dialects — are the source of nearly every problem people have with the format. The byte-level layout is described in DBF file structure.
Ways to open it
| Method | What you get | The catch |
|---|---|---|
| Microsoft Excel | Depends on the version; classic dBase III/IV tables may open directly | Support has been cut back over the years and covers only the oldest dialects; FoxPro types, memo files and non-default code pages are where it breaks |
| ODBC / OLE DB dBase driver | A connection from Excel via Data → Get Data → From Other Sources | The driver must match the bitness of Office, a data source has to be configured, and memo is often unreadable |
| LibreOffice Calc | Opens .dbf directly | Asks for a character set and does not always guess it; memo support is partial |
| Convert to CSV first | An intermediate text file | Two conversions mean two chances to damage codes and dates |
| A browser-based viewer | The table at once, export to XLSX when needed | A viewer, not an analysis tool |
What gets damaged on the way
Even when a file opens, the data can change without any warning.
- Codes with leading zeros become numbers — ZIP codes, SKUs, account numbers. The mechanism is the same as in CSV; see why Excel destroys leading zeros.
- Records flagged as deleted either show up like any other row or silently vanish, depending on the driver. That is why two programs report different row counts — see deleted records in DBF.
- Memo fields turn into blanks or block numbers when the
.fptor.dbtfile is not found — see memo files. - Accented and non-Latin text is decoded with the driver's code page rather than the file's — see garbled characters in DBF.
A safer way
If the job is to look, search, check or pull out a subset, you do not need Excel in the middle. Open the file in a viewer, confirm the encoding, filter what you need, and export the result straight to XLSX, where the column types are set deliberately.
If Excel is the destination for calculations, it still pays to open the DBF on its own first: see the structure, confirm the code page, drop the rows you do not need — and only then export. What lands in Excel is then what you chose, not what a driver decided.
Drag the table and its memo file into the window together, and the memo text is attached automatically. Nothing is uploaded: parsing happens inside the browser tab.
FAQ
Will Excel ever fully support DBF again?
Unlikely. dBase is treated as a legacy format, and the support that remains covers only the classic dialects. For anything newer, use a tool that reads the dialect directly.
Why does LibreOffice open it when Excel does not?
LibreOffice kept its own dBase reader. That does not make it complete: memo files and the less common field types are only partly supported.
Can I save back to DBF from Excel?
Depending on the version there may be a dBase III/IV save option, but it covers only classic dBase: no memo, field names limited to ten characters, no Unicode. A tool that writes DBF itself is the safer route.
Free for personal use. Your file is not uploaded to a server. Windows version — 3.5 MB, no installation: details. Organizations: license.