DBF to CSV / XLSX / JSON
Parse legacy FoxPro & dBase III/IV binary .dbf tables — 100% private client-side processing.
Active Converter
DBF to Excel / CSV / JSON: Parsing Binary dBase III, IV & Visual FoxPro Tables
Technical Anatomy of the Binary .DBF Format
Originally introduced by Ashton-Tate for dBase II/III in the 1980s and extended by Clipper and Microsoft Visual FoxPro, the .dbf format remains embedded in thousands of ERP systems, municipal tax rolls, accounting packages, and ESRI GIS Shapefiles. A .dbf file consists of three binary sections: a 32-byte File Header, a variable array of 32-byte Field Descriptors terminated by 0x0D, and fixed-width Data Records terminated by 0x1A (EOF).
Byte 0x00 identifies the xBase dialect (0x03 for dBase III/FoxPro without memo, 0x83 with .dbt memo, 0x30 for Visual FoxPro). Bytes 0x04–0x07 store the total record count as an unsigned 32-bit little-endian integer. Each 32-byte field descriptor declares an 11-byte null-padded column name, a 1-byte data type (C Character, N Numeric, D Date YYYYMMDD, L Logical T/F), and the exact column byte width. Every data row begins with a 1-byte deletion flag: 0x20 (active) or 0x2A (*, soft-deleted).
Binary dBase III Header Layout vs. Converted JSON / Excel Output
# Raw .DBF Binary Header (First 32 Bytes):
03 1A 0B 14 02 00 00 00 61 00 29 00 00 00 ...
| | | | |
| YY/MM/DD RecordCnt=2 Hdr=97 RecLen=41
Version=dBase III
# Field Descriptor (32 Bytes) + Record (0x20 active flag + fixed-width ASCII):
[0x20] "INV-1042 " "20261120" " 1450.50"
# Converted Excel / CSV Output:
INVOICE_NO,INV_DATE,AMOUNT
INV-1042,20261120,1450.50
Real-World Software & Hardware Ecosystem
Accountants, GIS analysts, and IT migration teams routinely pull .dbf files from Visual FoxPro 9, Sage / Peachtree legacy ledgers, ESRI ArcGIS and QGIS Shapefiles, Clipper/Harbour POS terminals, and government census portals. Modern Microsoft Excel dropped native .dbf save support years ago and frequently mangles legacy DOS codepages (CP437, CP850, CP1256 Arabic) when opening xBase files directly.
Troubleshooting & Edge Cases
- Truncated 10-Character Column Names: Classic dBase III strictly caps column names at 10 ASCII characters plus a null byte. If you see abbreviated headers like
CUST_ADDR1, that truncation originates inside the source.dbfspecification itself. - Visual FoxPro 263-Byte Backlink Block: Visual FoxPro tables attached to a
.dbcdatabase container insert a 263-byte backlink after the0x0Dfield terminator. Our parser reads the exact header byte offset at0x08–0x09so record alignment never drifts. - Arabic & Accented Character Mojibake: Keep the UTF-8 BOM Smart Auto-Fix toggle enabled when exporting CSV so Excel opens accented and international names cleanly without broken symbols.
32-Byte dBase III / IV File Header Byte Map
| Byte Offset | Size | Encoding / Meaning |
|---|---|---|
| 0x00 | 1 byte | Version flag (0x03 dBase III, 0x83 w/ DBT memo, 0x30 Visual FoxPro). |
| 0x01–0x03 | 3 bytes | Last modification date (YY since 1900, MM, DD). |
| 0x04–0x07 | 4 bytes | Unsigned 32-bit little-endian total record count. |
| 0x08–0x09 | 2 bytes | Exact byte offset where data records begin (header + descriptors + 0x0D). |
| 0x0A–0x0B | 2 bytes | Fixed byte width of each record (including the leading 0x20/0x2A flag). |
| 0x1D | 1 byte | Language Driver ID (LDID) specifying DOS/Windows codepage (e.g., 0x03 CP1252). |
Migrating ESRI Shapefile .DBF Attributes & FoxPro Ledgers
When auditing municipal property parcels or legacy FoxPro accounting backups, always verify that soft-deleted rows (0x2A) are excluded before summing financial totals. If you later need to merge edited Excel columns back into a GIS Shapefile, preserve the exact row order and unique FID/OBJECTID key column so polygon geometries stay linked to their attributes in QGIS.
Auditing Legacy Codepages & Numeric Precision in Accounting Exports
Because dBase III/IV stores numeric (N) and floating-point (F) fields as right-aligned ASCII strings padded with leading spaces (for instance, " 1450.50"), precision loss from binary floating-point rounding never occurs inside the raw .dbf file itself. When opening converted sheets in Excel for tax or inventory audits, verify that large account numbers or national tax IDs stored in Character (C) columns retain their leading zeros, and cross-check the total active row count against the 32-bit record counter in header bytes 0x04–0x07 minus any 0x2A soft-deleted rows.
Frequently Asked Questions
It reads the fixed 32-byte binary file header (version byte at 0x00, last-update YY/MM/DD at 0x01–0x03, 32-bit little-endian record count at 0x04–0x07, header length at 0x08–0x09, and record length at 0x0A–0x0B), then loops through 32-byte field descriptors until hitting the 0x0D terminator byte.
dBase uses soft deletion: every data row starts with a 1-byte status flag—0x20 (space) for an active record and 0x2A ('*') for a record marked for deletion before PACK is run. Respecting this flag prevents ghostly deleted invoices from reappearing in your Excel ledger.
In xBase databases, variable-length Memo text is stored outside the .DBF file in a companion .DBT (dBase) or .FPT (FoxPro) file; the .DBF column holds only a block pointer index. All standard Character (C), Numeric (N), Date (D), Logical (L), and Float (F) fields extract completely from the .DBF alone.
Yes. Every GIS Shapefile bundle stores polygon and coordinate attributes in a standard dBase III .dbf table. Converting it to .XLSX or .JSON lets you audit GIS attributes in Excel without opening QGIS or ArcGIS.