Upload Your SQL
Select or drag in a UTF-8 .sql file containing MySQL or MariaDB INSERT INTO statements.
Fast, Secure & Easy
SQL to JSON Converter
Transform MySQL or MariaDB INSERT statements into a readable JSON array with preserved column names, decoded strings, native values, and consistent objects.
Private conversion
Pretty-printed JSON
Automatic daily cleanup
How to Convert SQL to JSON
Transform database insert records into structured JSON in three simple steps.
Select a Table
Optionally enter a table filter, then convert. Without a filter, the first table containing insert rows is selected.
Download JSON
Download a pretty-printed .json file containing an array of consistent objects ready for APIs, scripts, or applications.
Why Use Our SQL to JSON Converter?
A dependable way to transform database insert data into portable objects for modern development workflows.
Consistent Objects
Single-row and multi-row inserts become JSON objects. Missing properties are added as null when column lists vary.
Native JSON Values
SQL NULL, booleans, integers, and decimal values become native JSON types, while quoted SQL strings remain strings.
Table Filtering
Large dumps can contain several tables. Choose the table you need without mixing unrelated records into one JSON.
What Is an SQL Dump File?
An SQL dump is a text representation of database structure and data. MySQL and MariaDB exports commonly use CREATE TABLE statements for schemas and INSERT INTO statements for stored rows. This converter safely reads those statements as text and never executes uploaded SQL.
Why convert SQL to JSON?
JSON is widely used by APIs, JavaScript applications, backend services, test fixtures, data pipelines, and NoSQL imports. Extracting an SQL table to JSON makes legacy database records easier to use in modern software without running a database server.
How JSON objects are built
Explicit INSERT column lists are used first. When an INSERT omits its columns, the matching CREATE TABLE schema supplies them. Every row becomes an object, later columns expand the shared object structure, and unavailable properties become JSON null.
Frequently Asked Questions
Helpful answers about supported statements, SQL tables, JSON output, and file handling.
How do I convert an SQL file to JSON?
Upload the .sql dump, optionally enter a table filter, click “Convert to JSON,” and download the generated .json file.
Which SQL statements are supported?
The converter extracts MySQL or MariaDB-style INSERT INTO ... VALUES statements and can read matching CREATE TABLE definitions.
Is this SQL to JSON converter free?
Yes. The tool can be used without registration or special conversion software.
Can I convert one table from a full dump?
Yes. Enter the exact table name in the optional filter. If left blank, the first table containing supported insert rows is converted.
Are multi-row INSERT statements supported?
Yes. Each parenthesized value group becomes a separate object in the output JSON array.
Does the tool execute uploaded SQL?
No. The file is parsed strictly as text. No database connection is opened and no uploaded statement is executed.
What are the file limits?
The upload limit is 25 MB, with a maximum of 50,000 records and 500 properties.
Are uploaded files kept on the server?
The original SQL file is deleted immediately after conversion. Generated JSON files older than 24 hours are removed automatically.
Why is my SQL file not converting?
It may use unsupported COPY or vendor-specific syntax, lack INSERT column lists and a CREATE TABLE schema, contain unfinished quotes, or exceed a file limit.