DBF to Excel Converter
Convert a dBASE .dbf table to a real Excel worksheet with typed cells. Legacy code pages decoded correctly and deleted rows excluded.
Complete the security check to begin
A forty-year-old table, opened as a modern spreadsheet
The .dbf table arrived with dBASE in 1983 and outlasted it completely. FoxPro and Clipper used it, a very long tail of accounting, inventory and point-of-sale systems still write it, and every GIS shapefile keeps its attribute table in one. If something exported a .dbf for you, or a shapefile lost its companion files and left the table behind, this turns it into a worksheet you can just open.
The reason to come here rather than to CSV is typing. A CSV is undifferentiated text, so Excel applies its import guesses on the way in — and the guesses go wrong in familiar ways, most notoriously turning an identifier made of digits into a number and stripping its leading zeros. A .dbf already states what each column is in its header, and that information is carried straight into the worksheet: numbers as numbers, logicals as real true and false values. Nothing is left to be inferred.
Legacy text, decoded from the file’s own header
A .dbf is older than the convention that a file should declare its text encoding. What it does carry is one byte in the header naming the code page its text was written in, and ignoring that byte is why so many DBF exports arrive as mojibake for anything beyond plain English.
This reads it, and handles the Windows, DOS and Mac code pages dBASE and FoxPro actually used — Hebrew, Cyrillic, Greek, Turkish, Baltic, Central European, Thai, Chinese, Japanese and Korean among them. Because the output is a genuine .xlsx, the decoded text is stored as Unicode, so there is no second chance for the encoding to be misread when Excel opens it.
Deleted rows stay deleted, and no cell becomes a formula
dBASE deletion only ever set a flag; the bytes stayed put. A table in service for twenty years may still hold records deleted a decade ago, and this converter hides them the way every database and GIS tool does — exporting them would be handing back data someone deliberately removed.
Cell contents are also neutralised against formula injection: any text beginning with a character Excel would read as the start of a formula is kept as text. Legacy tables contain all kinds of raw content, and a spreadsheet that silently evaluates a value taken from a data file is a well-understood attack route. Numbers, dates and booleans are untouched by this — they stay typed.
If your table is bigger than 20,000 rows
Use DBF to CSV, which goes to 100,000. The difference in ceilings is not arbitrary: we measured worksheet construction at around eight times the cost of writing the same rows as text, so the heavier output gets the lower limit. The CSV is written with a byte-order mark so Excel still reads the encoding correctly when it opens it. To query rather than browse the data, CSV to SQLite turns that export into a real database. Both conversions are on the API — this one at /api/convert/dbf-to-xlsx.
About Converting DBF to XLSX
DBF is the table format dBASE introduced in the early 1980s, and it outlived the program by decades: FoxPro, Clipper, countless accounting and inventory systems and every GIS shapefile store their records in it. A fixed-width header declares each column’s name, type and width, and the rows follow as fixed-width text — simple enough that the files are still readable forty years on. When you need to move away from DBF, the usual reason is simple: column names are capped at ten characters.
Converting your DBF data file to XLSX solves that. XLSX is the modern Microsoft Excel format — a ZIP of XML that stores multiple sheets, formulas, charts and formatting. It is the standard for business spreadsheets. In practice you gain formulas, charts and multiple sheets and open xml standard. PrivConvert runs the whole DBF-to-XLSX conversion in server memory and deletes your file the instant the XLSX is ready — nothing is stored, logged or reused.
When this conversion helps
- You need formulas, charts and multiple sheets
- You need open XML standard
- You need compact and robust
- Escaping a proprietary DBF file for the open XLSX standard
- Sharing a DBF data file with someone whose software expects XLSX
Tips for best results
- After converting, open the XLSX and skim the formatting — complex layouts occasionally need a small touch-up.
- Files up to 250 MB are supported, and you can batch-convert several DBF files at once; each is processed privately and deleted immediately.
How to Convert DBF to XLSX Online
Here is how a DBF → XLSX conversion works on PrivConvert, from start to finish. The key change: you move from the proprietary DBF format to the open XLSX standard.
Drag and drop your file into the upload area, click to browse your device, or paste a URL to a file hosted online. You can upload files up to 250 MB and batch convert up to 20 files at once.
Once uploaded, the conversion from DBF to XLSX starts automatically. The process runs entirely in an isolated environment - your data never leaves the secure pipeline.
Your converted file is ready instantly. Click the download button to save it to your device. The file is deleted from memory immediately after download.
What makes this DBF-to-XLSX converter different
Privacy here is not a checkbox. Every DBF-to-XLSX conversion is engineered so your data never lingers, leaks or gets reused.
Runs in any modern browser on Windows, macOS, Linux, Android and iOS — no install, plugin or desktop software needed.
Each job runs in an isolated in-memory sandbox, so most conversions finish in seconds instead of waiting in a queue.
We never keep a copy. Once your XLSX is delivered, both the original and the result are gone — there is nothing left to leak or misuse.
Every conversion runs in its own locked-down process with no network access, so files can never leak or interfere with one another.
DBF vs XLSX - Format Comparison
| Feature | DBF | XLSX |
|---|---|---|
| File extension | .dbf | .xlsx |
| Full name | dBASE Table | Office Open XML Spreadsheet |
| Introduced | 1983 | 2007 |
| Encoding | Binary | Binary |
| Editable | — | Yes |
| Open standard | No | Yes |
| Supported by PrivConvert | Yes (as input) | Yes (as output) |
| Privacy-safe conversion | In-memory, zero storage | |
| Max file size | 250 MB per file | |
| Batch support | Up to 20 files simultaneously | |
Why people pick PrivConvert for XLSX
Thousands of people trust PrivConvert with their files because privacy here is structural — enforced by how the service runs, not just promised.