DBF to Excel
Open a dBase or FoxPro table in Excel, right here on your device.
Conversion desk
On this device
Start with a file
Drop your file here or choose one from your device.
DBF · 5 files at a time, free
Its new format
FromDBF
ToExcel
Converted on this device. Nothing is uploaded.
Your file's short trip
DBF to XLSX
Your file is next.
- Read records
- Build the sheet
- Write the Excel file
- Ready
When a workbook beats a text file
Someone hands you a .dbf from an old FoxPro ledger, a dBase mailing list or a GIS project, and you want to look through it, filter it and perhaps pass it on. A workbook is the friendliest home for that. Excel, Numbers and LibreOffice all read XLSX, and the cells arrive typed: dates are dates, numbers are numbers, and codes stored as text, such as 00742, keep their leading zeros.
That typing is the main reason to pick XLSX over CSV. A CSV is plain text, so the program that opens it has to guess each column's type, and the guess depends on your regional settings. In a workbook, there's nothing to guess.
Converting a DBF to Excel, step by step
- Leave Text encoding on From the file to begin with. If letters come out wrong, change it and add the file again; the encoding guide shows how to tell which one a table needs.
- Drop the .dbf, together with its .dbt or .fpt memo file if it has one, or press Choose file and select both.
- Each table becomes its own workbook, on a sheet named after the file. The first row holds the field names, so filters and pivot tables pick them up straight away.
- Download the workbook, or use Download all (.zip) once you've converted several tables.
What's preserved, what changes
| What | Result |
|---|---|
| Records and values | Preserved 1,471 records read from 29 of our 30 test files. |
| dBase, FoxPro and Visual FoxPro files | Preserved Version bytes in our test files: 0x02, 0x03, 0x30, 0x31, 0x32, 0x83, 0x8B, 0x8C and 0xF5. |
| Field types | Preserved Read in our test files: auto-increment (+), double (B), text (C), date (D), float (F), integer (I), logical (L), memo (M), number (N), date-time (T), varchar (V) and currency (Y). |
| Declared decimals | Preserved Shown through a number format, so 3 in a two-decimal field appears as 3.00 and stays a number (47 such fields in our test files). |
| Memo text (.dbt and .fpt) | Preserved Read when you add the memo file along with the .dbf: 596 memo values in 6 test files. |
| Text encodings | Preserved Taken from the file's language driver byte, or chosen by you. In our test files: GBK, UTF-8, Windows-1251, Windows-1252 and Windows-874. |
| Dates before 1 March 1900 | Approximated Written as text such as 1850-01-01, because Excel's calendar can't hold them safely; later dates become real date cells (397 of 1,288 dates in our test files). |
| Text over 32,767 characters | Approximated Cut to Excel's cell limit, with a count in the notes. DBF to CSV keeps the whole text. |
| Tables over 1,048,575 rows | Approximated Split across several sheets, since one Excel sheet holds no more. DBF to CSV keeps one file. |
| Records marked as deleted | Not converted Left out, as dBase does when it packs a table (4 in our test files). |
| OLE and picture fields | Not converted Left out, and named in the notes (1 in our test files). |
| Tables over 8,000,000 cells | Not converted Too large for an XLSX made in the browser. DBF to CSV converts them. |
Preserved: arrives as it is. Approximated: arrives in a simpler form, as the row describes. Not converted: stays behind.
The rows that apply only to Excel come from the workbook format itself. A cell holds a limited amount of text, so a very long memo is cut there, and the notes count each one. A sheet holds a limited number of rows, so a longer table continues on sheets named like "Orders (1)" and "Orders (2)", each with its own header row. And a workbook made in a browser tab has to fit in memory all at once, which is where the cell budget comes from. None of these limits applies to DBF to CSV.
How the cells come out
- Dates become real date cells shown as 2024-01-31, so they sort and filter by date. Date-time fields from Visual FoxPro keep their time of day.
- Dates before 1 March 1900 stay as text. Excel's calendar counts a 29 February 1900 that never existed, so earlier dates can't be stored safely as date cells.
- Numbers stay numbers. A field declared with two decimals is formatted to show both, so 3 appears as 3.00 and still adds up in formulas.
- Whole numbers above 9,007,199,254,740,991, where spreadsheet numbers start to skip values, arrive as text, so no digit is rounded away. Excel shows only 15 significant digits, so a 16-digit ID below that limit looks rounded there, though the file holds every digit.
- True/false fields become TRUE and FALSE cells; a field that was never set stays empty.
- Memo text arrives in full, up to Excel's limit for a single cell.
Large tables
A workbook is built whole, in memory, before you can download it. That's why we ask before starting a DBF over 25 MB here, a much lower point than for CSV, and why a table with more cells than the budget above is stopped before its rows are read. You'll see "This table has more cells than one workbook can hold here": convert that table with DBF to CSV instead, which writes rows as it reads them and has no cell budget.
If something looks off
- A memo cell stops mid-sentence. The text was longer than an Excel cell holds. The notes count how many were cut, and a CSV keeps them whole.
- The workbook has several numbered sheets. The table had more rows than one sheet holds. Each sheet repeats the header row, so the parts line up if you join them in a database later.
- Some dates look like text. Dates before 1 March 1900 are written as text such as 1850-01-01, and the notes don't count them. A value that isn't a valid date keeps its original characters, and the notes count it as an unreadable date.
- An empty memo column, odd letters, or "This file looks damaged…" These come from reading the DBF, which works the same way as for CSV. The DBF to CSV troubleshooting list covers each one.
Try it with a sample file
Download sample-world-countries.dbf (519 KB) and drop it above. It's the country table behind Natural Earth's world map, and it's in the public domain. Once it opens in your spreadsheet, sort the population column, POP_EST, from largest to smallest: the values are numbers, so the most populous countries rise straight to the top.
Source and details: sample file notes.
Plans
Free and Pro
The free plan is the real product, not a trial. Pro is for people who convert in bulk, and it isn't open yet.
| Feature | Free | Pro |
|---|---|---|
| Single files | Free, no watermark, no wait | Same |
| Files at a time | Up to 5 | Up to 100 |
| ZIP and folder input | Pick the files instead | Yes |
| Large files | Works; may be slow on some devices | Built for them |
| Account | None needed | Optional |
| Where files go | Nowhere: converted on your device | Nowhere: converted on your device |
| Price | $0 | Week Pass $6 · Pro $7/month or $48/year · coming soon |
Privacy
Check it yourself
You don't have to take our word for it. Your browser can show you exactly what this page sends.
- Open your browser's developer tools (F12, or Option + Command + I on a Mac) and choose the Network tab.
- Convert a file on this page.
- Look through the requests. None of them carries your file: the page loads its code once, then the conversion runs in a Web Worker on your device.
- For a stronger test, turn off Wi-Fi after the page loads, then convert again. It still works.
The conversion worker runs under its own Content Security Policy, which blocks every network request:
default-src 'none'; script-src 'self'The page itself may only talk to this site and our cookieless analytics:
connect-src 'self' https://gateway.umami.is