Database Schema Generator

Start with a Template: Click the ✨ Load Template button to choose from 5 pre-built database schema templates including E-Commerce, Blog Platform, Task Management, Social Media, and Learning Management System schemas. Templates provide a quick starting point for common database structures.

Or Start from Scratch: Begin with a blank canvas and build your custom database schema step by step using the ➕ Add Table button.

Import Existing Schema: Already have a schema? Use the 📥 Import JSON option to load a previously saved database schema and continue editing.

Zoom Controls: Use the zoom buttons in the top-right corner to zoom in (+), zoom out (-), or reset to 100%. The zoom level is displayed as a percentage. Keyboard shortcuts: Ctrl/Cmd + Plus to zoom in, Ctrl/Cmd + Minus to zoom out, Ctrl/Cmd + 0 to reset zoom.

Pan the Canvas: Click and drag anywhere on the canvas background (not on tables) to move around your workspace. Essential for working with large database schemas containing many tables.

Mouse Wheel: Scroll with your mouse wheel or trackpad to zoom in and out smoothly at the cursor position.

Add New Tables: Click the ➕ Add Table button in the toolbar to create a new database table. Each table starts with one default field that you can customize.

Move Tables: Click and hold the ⋮ drag handle icon in the table header, then drag to reposition tables anywhere on the canvas. Tables automatically snap to a grid for clean alignment when Snap to Grid is enabled.

Rename Tables: Click directly on the table name or click the ✏️ edit button in the table header to rename a table. Press Enter to save or Escape to cancel. Use meaningful table names that reflect your database structure (e.g., "users", "products", "orders").

Delete Tables: Click the 🗑️ trash icon in the table header to remove a table. This will also remove any relationships (foreign keys) connected to that table.

Add Fields: Click the Add Field button within any table to create a new column. Each field represents a column in your database table.

Edit Fields: Click on any field row in a table to open the comprehensive field editor panel on the right side. The panel displays all field properties including name, data type, constraints, and relationships.

Field Name: Enter a descriptive name for your database column (e.g., "email", "created_at", "price"). Use lowercase with underscores for best practice.

Data Types: Choose the appropriate SQL data type for your field. Options vary by database:

• PostgreSQL: INTEGER, BIGINT, SERIAL, VARCHAR(255), TEXT, BOOLEAN, DATE, TIMESTAMP, TIMESTAMPTZ, JSON, JSONB, UUID, DECIMAL, and more
• MySQL: INT, BIGINT, VARCHAR(255), TEXT, BOOLEAN, DATE, DATETIME, TIMESTAMP, JSON, DECIMAL, FLOAT, DOUBLE, ENUM, SET
• SQLite: INTEGER, TEXT, REAL, BLOB, NUMERIC

Close Panel: Click the ✕ button in the top-right of the field editor panel to close it and return to full canvas view.

Primary Key (PK): Check this box to mark a field as the primary key. Primary keys uniquely identify each record in a table. Most tables should have a primary key (commonly an "id" field).

Not Null: Enforce that this field must have a value - it cannot be empty or null. Essential for required fields like usernames or email addresses.

Unique: Ensure all values in this field are unique across all rows in the table. Useful for email addresses, usernames, or any field that should not have duplicates.

Auto Increment: Automatically generate sequential numbers for this field (typically used with integer primary keys). The database will assign values like 1, 2, 3, etc.

Default Value: Specify a default value that will be used if no value is provided when inserting a new record. Examples: "0" for numbers, "CURRENT_TIMESTAMP" for timestamps, "true" for booleans.

What are Foreign Keys: Foreign keys create relationships between tables by linking a field in one table to a field in another table. This is fundamental to relational database design.

Add Foreign Key: In the field editor panel, scroll to the Foreign Key section. Check the "Is Foreign Key" checkbox to enable foreign key configuration.

Relationship Types:

• One-to-One (1:1): Each record in the first table relates to exactly one record in the second table. Example: User ↔ UserProfile
• One-to-Many (1:N): One record in the first table can relate to many records in the second table. Example: User → Posts (one user can have many posts)
• Many-to-Many (N:M): Records in both tables can relate to multiple records in the other table. Example: Students ↔ Courses (requires a junction table)

Select Referenced Table & Field: Choose which table and which field this foreign key points to. Typically, foreign keys reference the primary key of another table.

CASCADE Options: Control what happens when the referenced record is deleted or updated:

• CASCADE: Automatically delete/update this record when the referenced record is deleted/updated
• SET NULL: Set this field to NULL when the referenced record is deleted/updated
• RESTRICT: Prevent deletion/update of the referenced record if any records reference it
• NO ACTION: Similar to RESTRICT, but checks constraint at the end of the transaction

Visual Connectors: Relationships appear as labeled connector lines on the canvas, showing the relationship type (1:1, 1:N, N:M) and connecting the related tables. This provides a clear visual representation of your database structure.

Auto-Arrange: Click the 📐 Auto-Arrange button to access automatic layout options:

• Circular Layout: Arranges tables in a circle pattern - ideal for schemas with 5-10 tables
• Force-Directed Layout: Uses physics simulation to organize tables based on their relationships - great for complex schemas with many connections

Re-Arrange & Zoom to Fit: Click the 🎯 Re-Arrange button to center all tables and automatically zoom the canvas to fit all tables in view. Perfect after adding many tables or when tables are spread far apart.

Snap to Grid: Toggle the Snap to Grid option to enable/disable automatic alignment of tables to a grid. When enabled, tables snap to grid points for clean, aligned layouts.

Select your target database system to ensure generated SQL uses the correct syntax and data types:

• PostgreSQL: Popular open-source database with advanced features like JSONB, UUID, and TIMESTAMPTZ. Great for production applications.
• MySQL: Widely-used open-source database known for reliability and ease of use. Popular for web applications and WordPress sites.
• SQLite: Lightweight, serverless database perfect for mobile apps, embedded systems, and small-scale applications.

The available data types automatically update based on your database selection to show only compatible options.

Export Formats: Click the 📤 Export button to open the export modal with three format options:

• SQL: Generate complete CREATE TABLE statements with all constraints, foreign keys, and indexes. Ready to run directly on your database server. Includes CREATE TABLE IF NOT EXISTS syntax for safe execution.
• Prisma Schema: Export as a Prisma schema file for use with Prisma ORM. Includes model definitions, relations, and field attributes. Perfect for Next.js and Node.js applications using Prisma.
• JSON: Export the complete schema as JSON for backup, version control, or importing into other tools. Includes all tables, fields, constraints, relationships, and visual layout information.

Download or Copy: Click Download to save the schema as a file, or Copy to Clipboard to paste it directly into your code editor or database management tool.

Auto-Save: Your schema is automatically saved to browser local storage every time you make changes. Refresh the page and your work is preserved. You'll see a notification if a saved schema is found.

• Use Primary Keys: Every table should have a primary key to uniquely identify records. Use auto-incrementing integers or UUIDs.
• Normalize Your Schema: Break data into logical tables to reduce redundancy and improve data integrity. Avoid storing duplicate data.
• Choose Appropriate Data Types: Use the most specific data type that fits your data (e.g., INTEGER for whole numbers, not VARCHAR).
• Add Indexes: Consider adding indexes to fields used frequently in WHERE clauses, JOIN operations, or ORDER BY statements for better query performance.
• Use NOT NULL: Mark fields as NOT NULL when they should always have a value to prevent data quality issues.
• Meaningful Names: Use clear, descriptive names for tables and fields. Follow a consistent naming convention (e.g., snake_case).
• Document Relationships: Properly define foreign keys to maintain referential integrity and document how tables relate.
• Consider Timestamps: Add created_at and updated_at fields to track when records are created and modified.
• Plan for Scale: Think about how your schema will handle growth. Use BIGINT instead of INT for tables that may have millions of records.