No processing of your file contents takes place on any server. You need no data-processing agreement with gottrix to handle confidential or business documents.
Hosted in GermanyGlobal Content Delivery
Origin servers at Hetzner in Germany, delivered worldwide through a content delivery network. Your file contents are never transmitted in the process - they never leave your device.
The dBase table format (.dbf) dates back to the 1980s but is still very much alive today - most notably as the attribute table of every Esri shapefile (.shp), and in older accounting and inventory systems. If you want to inspect this attribute data without GIS software or a legacy tool, CSV is the fastest route.
This tool reads the file entirely locally in the browser - directly against the dBase file format: header data, field descriptors and the fixed row length are evaluated byte by byte. Character fields, numbers, booleans and dates (to ISO format YYYY-MM-DD) are typed correctly. Records marked as deleted are skipped, exactly as every current dBase tool does.
An honest note: memo fields (type M) point to a separate companion .dbt file, which is not provided here - those columns therefore stay empty instead of showing a meaningless pointer value. For the actual attribute data (numbers, text, dates, booleans), the result is complete.
Specifications
Specifications
Input formats
DBF
Output format
CSV
Batch processing
No
Processing
Locally in your browser (JavaScript)
File upload
None
In 3 steps
Drop or pick your .dbf file.
The tool reads header, fields and rows locally.
Download the CSV file.
Limitations: Memo fields (type M) stay empty, since the companion .dbt file is not supplied. Records marked as deleted are skipped. Text is read in the matching encoding, auto-detected from the file header's own language driver ID (including Windows-1251 Russian, GBK Chinese, Shift-JIS Japanese, EUC-KR Korean, Big5 Traditional Chinese, Windows-1250/1253/1254/1257 and more); when that ID is missing or unsupported, the text is first checked for valid UTF-8 and read as UTF-8 if so, otherwise decoding falls back to Windows-1252. Very large tables need memory.
FAQ
Is my file uploaded?
No. The conversion runs entirely locally in the browser.
Does this work with the .dbf from a shapefile?
Yes, that is one of the most common use cases - a shapefile’s attribute table.
What happens to memo fields?
They stay empty, since the companion .dbt file is not provided - a deliberate, honest omission rather than a meaningless pointer value.
Are deleted records shown?
No, records marked as deleted are skipped.
Which dBase versions are supported?
dBase III, IV and 5, plus compatible variants with and without the memo flag.