DBF to Excel Converter

Common Use Cases

• ArcGIS shapefile attributes — Shapefiles ship with a companion .dbf holding all attribute data. GIS analysts frequently need that table in Excel for reporting, pivot tables, or sharing with stakeholders who don't run GIS software.
• Legacy FoxPro and dBase III/IV exports — Older accounting, inventory, and point-of-sale systems built on Visual FoxPro or dBase still export .dbf directly. If the application is gone, this tool gets the data out without needing the original runtime.
• Government and public data portals — Several county assessor offices, census data archives, and FEMA flood-zone datasets still distribute records in DBF format. Converting to XLSX makes them usable in Excel, Google Sheets, or Power BI without installing specialized readers.
• Real estate and property databases — MLS bulk exports and county parcel data are routinely delivered as .dbf files. Agents and analysts need these in a spreadsheet to filter, sort, and generate reports.
• Sensitive on-premise data — DBF files from HR, patient management, or financial systems should never leave the building. Because this converter runs entirely client-side, the file never reaches a server — an important compliance point for HIPAA or GDPR workflows. You can also use our DBF Validator to inspect the file structure without converting.
• One-time data rescue from decommissioned software — When a legacy application is retired and the original database engine is no longer available, DBF files are often the only surviving data artifact. Extracting them to Excel preserves the data in a universally readable format.

Example Conversion

Input: parcels.dbf — a county assessor file with 12,400 records and 18 fields: PARCEL_ID (C/15), OWNER (C/50), ASSESSED (N/12,2), LAND_USE (C/4), LAST_SALE (D/8), and EXEMPT (L/1), among others.

Output: parcels.xlsx with a header row using the original field names, 12,400 data rows, numeric columns typed as numbers, the date column converted from the raw YYYYMMDD string to YYYY-MM-DD text, and the logical column rendered as true/false.

The most common confusion point in DBF-to-Excel conversion is the date field. DBF stores dates as 8-character ASCII strings in YYYYMMDD format — no separators, no timezone, no null representation. A blank date field is eight spaces. If you import 20231105 into Excel without reformatting, Excel treats it as a plain number. This tool converts DBF date fields to YYYY-MM-DD text, which Excel parses correctly when you apply a date format to the column.

If your DBF has a large number of deleted records — rows marked for deletion but not yet physically removed — they will be skipped during conversion and reported in the warnings panel. This is normal for FoxPro databases that haven't been "packed." If you need deleted records included, use the DBF Validator to inspect the raw record flags first.

About This Tool

The DBF to Excel Converter parses the binary DBF format directly in your browser using the Web File API and ArrayBuffer. It supports the most common DBF variants: dBase III (version byte 0x03), dBase IV (0x04), dBase III with memo (0x83), dBase IV with memo (0x8B), and Visual FoxPro (0x30). The resulting .xlsx file is generated client-side using SheetJS and downloaded directly without any server round-trip.

Excel is the right destination for most DBF migrations — XLSX handles variable-length strings, mixed types per column, and files up to about one million rows, which covers virtually all real-world DBF files. If your downstream process needs flat text rather than a spreadsheet, our DBF to CSV converter is a better fit for piping into pandas, R, or a database import. Excel is better when the recipient needs to filter, chart, or pivot the data without writing any code.

Practically: if the DBF came from a GIS tool or a legacy business application, convert to XLSX. If it's going into a data pipeline, convert to CSV instead. Most people doing a one-time data rescue want Excel.

How It Works

DBF vs Excel — Which Format Should You Keep?

DBF was designed for embedded database engines: fixed-width binary records, a 10-character field name cap, and no native support for Unicode. It is compact and fast for sequential reads, which is why dBase and FoxPro used it for decades. But it requires a parser to open — Excel has dropped native DBF import support in recent versions, and most users will see a blank or garbled file if they double-click a .dbf.

Excel XLSX is the right long-term format for any DBF data that humans need to read, filter, or share. It supports long field names, mixed types, formulas, and charts. The tradeoff is that XLSX is not a database — it doesn't support indexes, relationships, or concurrent writes. If the DBF is part of an active application that writes to it, keep the DBF and convert only for reporting.

The sharper point: DBF is fine as a source-of-truth if the original application still runs. If the application is gone or the data needs to be used by non-technical staff, Excel is the right format and there is no practical reason to stay in DBF.

Limitations

• Memo fields not included — DBF Memo fields (type M) store their data in a separate .dbt or .fpt file, not inside the .dbf itself. This tool only reads the .dbf, so memo columns will appear as placeholder values. If memo content is critical, you'll need a tool that can read the companion file alongside the main DBF.
• Codepage and encoding — DBF files produced by older DOS-era applications often use CP437 or CP850 encoding rather than Windows-1252 or UTF-8. Accented characters and special symbols may appear garbled in the output if the file was written with a non-Latin codepage. The DBF header stores a codepage ID in byte 29, but this field is often set to zero in files produced by FoxPro and Clipper.
• Excel row limit — Excel worksheets are capped at 1,048,576 rows. Very large DBF files (some GIS datasets exceed this) will be truncated. Convert to CSV instead for datasets above ~1 million records and use Power Query or a database for analysis.
• Unsupported version bytes — Some proprietary extensions of the DBF format (used in Clipper 5, dBase VII, or certain GIS tools) have non-standard version identifiers and field types. The converter will report the version byte and skip records it cannot parse.
• Deleted records are skipped silently unless flagged — A surprising edge case: DBF files from applications that never run a "pack" operation can have 30–50% of their rows marked as deleted but still physically present in the file. The warnings panel will tell you how many were skipped, but if you expected a certain record count, this is why the number doesn't match.