Compress and pack DBF database files
DBF is the table format behind dBASE, FoxPro, Visual FoxPro, and Clipper. It's still used by accounting and point-of-sale systems, government datasets, and every GIS shapefile. DBF tables have one quirk that makes them grow: when a record is deleted, it isn't removed. It's only marked as deleted and stays in the file, invisible but taking up space, until someone packs the table. This tool packs tables in your browser, removes leftover bytes, and then compresses them for storage or sharing.
Your data never leaves your computer.
How to use it
- Choose one or more
.dbffiles, or drag them onto the box. - Check each table's details: format, record count, how many records are marked deleted, and a preview of the data.
- Download the packed table, a ZIP or gzip for storage, or a CSV copy to open in Excel or Google Sheets.
What packing does
Packing is the same operation as dBASE's PACK command, FoxPro's PACK, and the "pack" or "purge" function in many DBF-based programs. Every record that isn't marked deleted is copied, in its original order and byte for byte, into a new table with an updated record count. The table structure, field definitions, and header settings stay exactly the same.
After packing, the tool reads the new table back and compares every remaining record with the original. The green Verified badge means they're identical.
| Download | What it is | Use it for |
|---|---|---|
| Packed DBF | The same table without deleted records | Putting back into your application |
| ZIP | The packed table, compressed. DBF files usually shrink 80 to 95 percent, because fixed-width fields are full of padding. | Email, sharing, and backups |
| Gzip | The same compression in a single-file format | Archives and data pipelines |
| CSV | The live records as comma-separated text in UTF-8 | Opening in Excel, Google Sheets, or a database |
Things to know before packing
- Deleted records are gone for good. dBASE's
RECALLcommand can't bring back records after a pack. Keep the original file until you're sure you don't need them. - Index files need rebuilding. Packing changes record numbers, so an index file (
.mdx,.cdx,.ndx,.ntx) will point at the wrong rows. Tables flagged as having an index are left unpacked unless you choose otherwise. If you do pack them, runREINDEXin your application afterward. - Memo files stay as they are. Tables with memo fields keep long text in a separate
.dbtor.fptfile. Keep it next to the packed table under the same name. Notes from deleted records stay in the memo file, since compacting it would mean rewriting every memo reference. - Shapefiles need care. In a shapefile, the
.dbfrows must match the shapes one to one. Don't pack the.dbfof a shapefile. Use the ZIP or gzip download instead.
Frequently asked questions
Are my files uploaded?
No. Tables are read, packed, and compressed inside your browser, and nothing is sent anywhere.
Which DBF versions are supported?
dBASE III, IV, V, and 7, FoxBASE, FoxPro 2, Visual FoxPro, and Clipper tables. The tool shows which format it detected.
My table didn't get smaller. Why?
If no records are marked deleted, there's nothing to pack, which is common for tables that were packed recently or never had deletions. The ZIP and gzip downloads still shrink DBF files dramatically.
The accented letters look wrong in the preview. What do I do?
Older DBF files often use DOS code pages. The tool reads the table's language setting, but some programs don't set it. Pick a different encoding from the list, such as DOS 850 for Western European data. The table file itself is never re-encoded.
Can it repair a damaged DBF?
No. If the header doesn't match the file size, the table is left unchanged and the tool explains why, so a damaged file is never made worse. ZIP and gzip still work for safekeeping.
Can I convert DBF to CSV or Excel?
Yes. Use the CSV download, which opens directly in Excel and Google Sheets. Dates are written as YYYY-MM-DD, and memo fields show their memo block number.