DBF is a table format from the xBase family
A file ending in .dbf normally stores a database table: a defined set of columns followed by records that share the same layout. The format became widely known through dBASE and was later used or extended by FoxBASE, FoxPro, Visual FoxPro, Clipper and many accounting, geographic and administrative applications.
There is no single universal “DBF format.” The extension identifies a family whose members share the same general design but differ in version signatures, field types, memo storage, encodings and database features. Identifying the producing application is therefore part of reading the data correctly.
How a DBF file is organized
The beginning of the file is a header. It records information such as the format version, a last-update date, the declared record count, header length and record length. Field descriptors then define each column: its name, type, width and, for numeric fields, decimal count. A terminator marks the end of this description.
Traditional records are fixed-length. The first byte commonly stores a deletion flag, followed by the bytes allocated to every field. Fixed positions made records fast to navigate on early computers, but they also mean that a wrong field width or record length shifts the interpretation of every later value.
| Part | Purpose | Typical validation |
|---|---|---|
| Version byte | Identifies a DBF generation or feature family | Compare with field types and memo companions |
| Header values | Declare record count and structural lengths | Compare declared size with physical file size |
| Field descriptors | Define column names, types and widths | Confirm widths add up to the record layout |
| Record area | Stores deletion state and field values | Sample early, middle and late records |
A DBF may depend on other files
Long notes and binary content often live outside the DBF. Visual FoxPro generally uses an FPT memo file, while dBASE variants commonly use DBT. The DBF record contains a pointer; losing the companion can leave an otherwise readable table with empty memo fields.
Indexes such as CDX, IDX and NTX store keys and ordering information. They are different from memo files: a viewer can usually read physical DBF records without an index, but the original application may depend on indexed order, uniqueness rules or filter expressions.
Why DBF files still matter
- Long-running payroll, inventory and accounting systems may retain decades of records in DBF tables.
- Geographic software has historically paired shapefile geometry with DBF attribute tables.
- Government and research datasets sometimes use DBF for compatibility with established workflows.
- Archived custom applications may contain the only surviving copy of business history.
The age of the format does not make the records disposable. A small DBF can contain identifiers, personal information or transaction history that requires the same access controls as a modern database.
Inspect before converting
Duplicate the complete source folder, keep the untouched archive, and open only the working copy. Use DBF Viewer Pro to inspect the schema and sample records locally. Confirm memo pairing, character encoding, deleted-record handling and record counts before producing CSV or importing into another database.
Continue with the DBF field types reference to interpret columns, or read the dialect comparison when the source application is known.