Design database tables visually with column types, constraints, defaults, and generate CREATE TABLE SQL.
Instead of typing CREATE TABLE by hand, you lay the table out as a list of columns: each row gets a name, a data type, and the constraints that apply to it (NOT NULL, PRIMARY KEY, UNIQUE), plus an optional default value, and the page assembles the finished statement for you. Everything runs in the browser, so the design never leaves the page. What surprises most people is that the SQL is dialect-shaped: types, quoting, and auto-increment idioms differ between SQLite, MySQL, and PostgreSQL, and the generated text follows the conventions of whichever dialect the page targets. Check it against your engine before running it.
Each column in your table is one entry with a name, a data type, the constraints it carries (NOT NULL, PRIMARY KEY, UNIQUE), and an optional default value. The page assembles the CREATE TABLE statement from those entries in the order you defined them, so the final SQL is exactly as complete as the design: no primary key in the grid means no primary key in the output.
The deliverable is DDL text: CREATE TABLE statements for the tables you designed, ready to copy into a migration file or database client. The page generates text rather than executing anything, so validity is your check, not the page's. A type name your database does not recognize, or a default it cannot parse, fails at your engine, not in the editor.
The statement is written in the dialect conventions the page uses, which may not be the one you deploy to. SQLite, MySQL, and PostgreSQL accept different type names, quoting, and auto-increment syntax, so the same design produces different SQL on each. Check the output against your engine's CREATE TABLE rules before running it, and prefer types that exist everywhere, such as INTEGER and TEXT, when you want portability.
Only what the page exposes: the tool's scope is column types, constraints, and defaults. Indexes, table-level constraints, and engine-specific storage settings are not part of a column design, so expect to add them to the generated statement yourself or manage them in your migration tooling.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.