JSON to MySQL Converter
Paste a JSON sample to instantly generate matching MySQL CREATE TABLE statements, with nested objects split into related tables and NULL/NOT NULL inferred automatically. Free online developer tool.
Paste JSON
MySQL CREATE TABLE
CREATE TABLE statements will appear here...
Free JSON to MySQL Converter
Paste a JSON sample to instantly generate matching MySQL CREATE TABLE statements. Nested objects become separate tables with a foreign-key comment describing the relationship, and columns are marked NULL or NOT NULL based on what your sample shows.
How to Use It
Paste any JSON object into the input box, or click "Load Example" to see a sample run. The converter parses your JSON, infers a column type for every scalar field, and generates oneCREATE TABLE statement for the top-level object plus one additional statement for every nested object it finds. Arrays of primitive values are called out in a SQL comment noting that a separate join table would be needed for proper normalization — this tool does not attempt to build those join tables automatically.
Example
Given {"name": "Ann", "signedUpAt": "2024-01-15T10:00:00Z", "tags": ["a","b"], "address": {"city": "NYC"}}, the tool generates a root table with name VARCHAR(255) NOT NULL andsigned_up_at DATETIME NOT NULL, a comment noting tags would need a join table, and a separate root_address table with a foreign key column referencingroot.id.
Common Use Cases
- Sketching out a relational schema quickly from an existing API response or export.
- Getting a starting point for migrating a document-shaped payload into MySQL.
- Seeing at a glance which nested objects will need their own tables and foreign keys.
- Speeding up database design reviews by generating a first draft to refine by hand.
FAQs
Does this tool fully normalize my data?
No — proper normalization (join tables for arrays, choosing the right key types, indexes, and so on) is out of scope for an automated converter. Nested objects get their own table with a clearly commented foreign-key relationship, and arrays of primitives get a SQL comment flagging that a join table would be needed, so you can finish the design by hand.
How are column types chosen?
Strings map to VARCHAR(255) unless they look like an ISO-8601 timestamp, in which case they map to DATETIME. Whole numbers map to BIGINT, decimals map toDOUBLE, and booleans map to BOOLEAN.
Is my JSON uploaded anywhere?
No — parsing and SQL generation happen entirely client-side in your browser. Nothing you paste is sent to a server.