Is converting FoxPro to XLSX 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 FoxPro data keep its types in XLSX?

Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real XLSX 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 FoxPro to XLSX

Upload a .dbf file and get back a XLSX 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 XLSX

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

Your data	XLSX type
Whole number	number
Decimal (money)	number
Floating point	number
True / false	boolean
Date	date
Date and time	date
Short text	text
Long text	text
Binary data	hex text

Working from a FoxPro table

FoxPro extended the dBase file layout with types dBase never had, and gave its memo files a different format and a different extension. Both of those differences change what comes out the other side, and both are read from the file.

→The FoxPro-only field types are read as themselves: Currency (Y) becomes an exact decimal rather than a float, Integer (I) a 64-bit integer, DateTime (T) a timestamp, Double (B) a floating-point number.
→Memo text is expected in a .fpt, chosen from the Visual FoxPro and FoxPro 2.x version bytes 0x30, 0x31, 0x32, 0xF5 and 0xFB, rather than in the dBase .dbt.
→Only the .dbf itself is read. A table bound to a Visual FoxPro database container keeps its long field names and relations in the .dbc, so columns arrive under the short names in the table header.

Sheet names and cell types

The workbook is generated rather than exported out of Excel, so every choice in it is one the converter made. The two that show up the moment you open the file are what the sheet is called and what type each cell turned out to be.

→The sheet takes the table's name cut to 31 characters, which is Excel's own limit for a tab, while the workbook file keeps the name in full - so a long table name is complete in the file name and shortened on the tab inside it.
→Dates and timestamps become genuine date cells, formatted yyyy-mm-dd and yyyy-mm-dd h:mm:ss, rather than strings that merely look like dates. Sorting and date arithmetic work on them with no conversion step first.
→A text column of digits stays text: a value like 01234 is written into a string cell, and Excel shows it as it was stored instead of dropping the zeros the way it does when the same data is opened from a CSV.

Reading FoxPro

→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 XLSX

→One file per table. Booleans stay booleans and numbers stay numbers.
→Excel has no fixed-point type, so decimals become numbers — use a database target if exactness matters.

What you get

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

Questions

Is converting FoxPro to XLSX 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 FoxPro data keep its types in XLSX?: Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real XLSX 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.