Is converting DBF to CSV free?

Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.

Will my DBF data keep its types in CSV?

Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real CSV types rather than everything becoming text. The mapping table above shows exactly what you get.

Do you store my file?

No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.

Convert DBF to CSV

Upload a .dbf file and get back a CSV file. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.

1Upload your file

Click to upload or drag and drop

CSV, Excel, SQLite, SQL, DBF (max 10 MB)

2Choose target format

How your data is typed in CSV

Generated from the converter's own CSV type mapping — this is what it actually emits, not an example.

Your data	CSV type
Whole number	text (CSV has no types)
Decimal (money)	text (CSV has no types)
Floating point	text (CSV has no types)
True / false	text (CSV has no types)
Date	text (CSV has no types)
Date and time	text (CSV has no types)
Short text	text (CSV has no types)
Long text	text (CSV has no types)
Binary data	text (CSV has no types)

Working from a .dbf file

A .dbf holds one table and describes its own fields in a header, so none of the structure has to be guessed. What it does not always hold is all of its data: long text lives in a second file beside it.

→The header is inspected before conversion, and if it declares a memo field with no companion file present the upload is refused with that companion's exact name - CUSTOMER.fpt, not "a memo file".
→That name is derived from your file's own stem plus the version byte in its header, and the check is case-insensitive because DOS-era files usually arrive in upper case.
→Upload the .dbf and its companion together in one request. Several files are accepted at once, and the 10 MB free limit applies to the total rather than to each file.

The shape of the CSV files you get

CSV is where the type information stops, so what is left to describe is the file itself: how a row is terminated, which fields are quoted, and how a value that used to have a type is spelled out as characters.

→Rows end with a carriage return and a line feed, the RFC 4180 ending, while a newline inside a quoted field stays the single character it always was. The encoding is UTF-8 with no byte-order mark in front of it.
→Quotes go on only where they are needed - a field holding a comma, a double quote or a newline - and a quote inside a field is doubled rather than escaped with a backslash. Every other field is written bare.
→Decimal values are written digit for digit and never through a floating-point number, so a money column that was exact in the source is still exact in the file. Booleans are written lower case, as true and false, which is the spelling this converter's own reader takes back as a boolean.

Reading DBF

→Numeric fields with decimals are read as exact decimals, not floats, so currency does not drift.
→Character field widths are read from the header and carried into the target.
→The code page declared in the file header is used, so Cyrillic, Western European and other legacy DOS encodings decode correctly instead of turning into mojibake. 157 code pages are recognised.
→Files written by dBase III or Clipper declare no code page at all — the header byte for it did not exist yet. For those, the most plausible encoding is chosen by inspecting the text, and the conversion tells you it had to guess. The API takes a sourceEncoding parameter (e.g. cp866) to force it instead of guessing, though the widget above does not have a control for it yet.
→Memo columns keep their text in a separate .dbt or .fpt file. If the .dbf declares one and it was not uploaded, the conversion stops and tells you which file to add, rather than handing you a table whose long text is silently blank.

Writing CSV

→One file per table, with a header row.
→NULL is written as an empty field, never the word "None".
→Binary data is written as hex, which is reversible.

What you get

A ZIP containing <table>.csv. If anything about your data needed a judgement call, a _warnings.txt explains it.

Questions

Is converting DBF to CSV free?: Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.
Will my DBF data keep its types in CSV?: Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real CSV types rather than everything becoming text. The mapping table above shows exactly what you get.
Do you store my file?: No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.