Is converting mysqldump 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 mysqldump 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 mysqldump to MariaDB

Upload a .sql 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 a mysqldump file

mysqldump writes a plain-text .sql file with a very consistent shape, which makes it one of the easiest dumps to read: its own syntax announces the dialect, and its rows are inline rather than in a separate archive.

→Every mysqldump file contains ENGINE=InnoDB or AUTO_INCREMENT, which is exactly what the dialect detection looks for, so backtick-quoted identifiers and MySQL types parse without you choosing anything.
→mysqldump packs many rows into one extended INSERT by default, and each tuple in it becomes a row, so there is no need to dump again with --skip-extended-insert.
→The file is decoded as UTF-8 with unreadable bytes replaced, so a legacy latin1 dump arrives with damaged accented text. Dump with --default-character-set=utf8mb4, or run the file through iconv first.
→mysqldump --tab is not a dump at all: the schema goes to a .sql file and the rows to headerless tab-separated .txt files. Neither half is convertible on its own, and the data files have no header row to name their columns, so dump again without --tab.

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 mysqldump

→Parsed with a real SQL parser, not regular expressions, so a value containing a closing parenthesis or a semicolon cannot split a row in half.
→CREATE TABLE types, primary keys, NOT NULL and AUTO_INCREMENT are all read from the dump.
→The source dialect is detected from the dump itself — MySQL, PostgreSQL and SQL Server dumps all parse.

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 mysqldump 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 mysqldump 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.