Skip to workspace
PixelOkay

Database Designer

Local workspace
Tools
Entity relationship diagram
100%
Drag tables to move · Drag background to pan · Scroll to zoom
  
 
  
 
  
 
DATA INTEGRITY
New relationship
 
Connect child foreign-key columns to a parent primary key or unique index. Use Ctrl/⌘ to select multiple columns in the same table order. Composite keys must match in count and order.
 
  
 
  
Project tools
  
CODE-TO-DIAGRAM WORKFLOW
Import text schema
 
Paste a supported SQL DDL script or DBML text. Validate first; replacement is explicit and checkpoints your current working draft. Advanced SQL and DBML grammar may be unsupported.
    
Text imports retain schema structure but regenerate diagram positions and internal IDs. JSON remains the lossless editable project format.
 
Paste a schema and select Validate.
 
   
LOCAL WORKSPACE
Project library
 
Save named copies in this browser. Opening a copy makes it your working draft; later edits will not overwrite the saved copy until you choose Update. Download JSON for a backup outside this browser.
 
 
  
Restore points
Browser-only checkpoints. Export a JSON backup before clearing your browser data.
 
Schema comparison
Read-only structural differences. This is not a safe SQL migration generator; renames appear as removed and added objects.
      
 
Using Database Designer
Design tables and relationships in the visual workspace, or import supported SQL and DBML. Save an editable JSON project before sharing SQL or a diagram.
SQL and DBML support is a documented subset, not a live database connection or migration service. Review generated DDL before applying it. Browser drafts and named local copies are separate from downloaded backups.
 
 
Hand off a two-table schema with its editable source
 
projects: id (integer, primary key), name (text)
tasks: id (integer, primary key), project_id (integer), title (text)
Relationship: tasks.project_id references projects.id
 
  1. Build this authored planning schema using Add table and the column inspector. Set each id as a primary key and use compatible integer types for project_id and its referenced column.
  2. Create a relationship with tasks as the child and projects as the parent. Review deletion/update behavior deliberately; a line on the canvas is not a decision about how records should be deleted.
  3. Open Schema checks and inspect the SQL preview for the selected PostgreSQL, MySQL or SQLite dialect. Resolve reported issues and read the generated DDL before considering it for a real database.
  4. Save an editable JSON project first. Export SQL for DDL review, an SVG/PNG for discussion, or the Markdown data dictionary for field descriptions; these have different handoff purposes.
  5. If comparing a revised JSON project, read removed/added objects carefully. Structural comparison does not establish a safe migration or infer a rename.
 
Original schema blueprint, not a generated SQL file or executed database. SQL/DBML support is bounded; text imports regenerate positions and internal IDs, while JSON retains the editable project. Browser copies/checkpoints are not external backups. Use SQL Formatter for a separate formatting task; it does not validate or apply this schema.
 
 
Choose an ER diagram or database schema handoff
  
Database Designer questions
 
Can I import SQL and update my live database?
You can import supported table definitions for planning. The tool does not connect to a database, execute SQL or apply migrations. Review generated DDL, constraints and unsupported syntax in your own database workflow.
 
Is a saved browser project a backup?
Browser drafts, the local project library and restore checkpoints stay in browser storage and can be cleared or become unavailable. Download project JSON before a significant change; a diagram image cannot restore the editable schema.
 
Related tools