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

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

Upload a .dbf file and get back a MariaDB SQL script you can load straight into your database. 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 MariaDB

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

Your data	MariaDB type
Whole number	BIGINT
Decimal (money)	DECIMAL(10,2)
Floating point	DOUBLE
True / false	TINYINT(1)
Date	DATE
Date and time	DATETIME
Short text	VARCHAR(255)
Long text	LONGTEXT
Binary data	LONGBLOB

Working from an xBase table

xBase is the family name for the record layout dBase defined and Clipper, FoxBase and FoxPro adopted. A file from any of them opens here; the differences live in the header bytes, and those are read rather than assumed.

→Records deleted but never packed are still physically present, flagged with an asterisk. They are skipped, so the converted table holds the rows the application showed and not the ones it hid.
→Clipper is the trap in this family: it wrote version byte 0x03 even for tables with memo columns, so a naive reader picks the wrong memo layout and dies with "unpack requires a buffer of 8 bytes". That case is handled here.
→The header gives each field an 11-byte name slot, so xBase column names are at most 10 characters - a limit that follows the data into the target unless you rename the columns there.

What MariaDB gets, and how it differs

MariaDB and MySQL are close enough here that one dialect serves both, and picking MariaDB does not select a different code path: the script is byte for byte the one a MySQL conversion produces. The differences worth flagging are in what you do with it.

→The README packed beside the script names both engines in its load command, because the invocation is the same either way - the file is piped into a client rather than executed by the server.
→The CREATE DATABASE line in that README asks for utf8mb4_unicode_ci and not for utf8mb4_0900_ai_ci, which is MySQL 8's default. MariaDB has never implemented the 0900 collations, and unicode_ci is the one both engines have.
→Date-and-time columns are declared DATETIME rather than TIMESTAMP, so what loads is the wall-clock value the source held. No session time zone is applied on the way in, and none is applied when you read it back out.

Reading xBase

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

→Tables are created as InnoDB with utf8mb4, so emoji and CJK text survive the load.
→Backslashes are escaped, because MySQL treats them as escape characters by default.
→Text columns of unknown length become TEXT rather than a guessed VARCHAR that could truncate your data.
→Inserts are batched, and identifiers are capped at MySQL’s 64-character limit.

What you get

A ZIP containing dump.sql, plus a README with the exact command to load it. If anything about your data needed a judgement call, a _warnings.txt explains it.

Load this dump into MySQL or MariaDB:

  mysql -u USER -p DATABASE < dump.sql

Create the database first if it does not exist:

  mysql -u USER -p -e "CREATE DATABASE DATABASE CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;"

Questions

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