Supabase schema visualizer
Paste Supabase PostgreSQL table definitions and instantly see columns, primary keys, and foreign keys as a downloadable ER diagram. Everything runs in your browser.
Paste a Supabase schema above to generate a diagram.
What is a Supabase schema diagram?
Supabase stores application data in PostgreSQL schemas such as publicand connects user records to the managed auth schema. An ER diagram turns those SQL table definitions into a visual map of columns, primary keys, and foreign key relationships.
Use the visualizer when reviewing migrations, documenting a project, or understanding how application tables connect to profiles and users. It reads pasted SQL without connecting to your Supabase project.
Supported Supabase schema patterns
The parser handles PostgreSQL CREATE TABLE statements, schema-qualified table names, common column types, primary keys, and inline or table-level foreign keys. Include the definitions for referenced tables in the same input so each relationship can be drawn.
FAQ
What Supabase SQL can this visualizer parse?
The visualizer reads PostgreSQL CREATE TABLE statements, including schema-qualified names such as public.projects and auth.users. It recognizes columns, common PostgreSQL data types, inline or table-level primary keys, and REFERENCES or FOREIGN KEY constraints. Extensions, views, functions, triggers, indexes, and ALTER TABLE statements are outside the current parser.
How do I copy my Supabase schema into the visualizer?
Open the SQL editor or a local migration file and copy the CREATE TABLE statements you want to review. Paste those statements into the input above. Include every referenced table when possible so the visualizer can draw complete relationship lines. You can combine statements from multiple migration files into one input.
Does this tool connect to my Supabase project?
No. The tool does not request a project URL, database password, service-role key, or Supabase account access. It only scans the SQL text you paste and renders SVG in your browser. The schema is not uploaded to Basedash or sent to Supabase, which makes the tool suitable for reviewing local migrations.
Can the diagram show relationships to auth.users?
Yes, when the pasted SQL includes a CREATE TABLE definition for auth.users or another referenced auth table. Supabase manages the auth schema, so migration exports do not always include those definitions. You can add a minimal auth.users table containing the referenced columns when you want that relationship to appear in the diagram.
Are Supabase row-level security policies included?
No. Row-level security policies control which rows a user can access, but they do not change the table and foreign-key structure represented by an ER diagram. CREATE POLICY, ALTER TABLE ENABLE ROW LEVEL SECURITY, grants, and database functions are ignored. Review those statements separately when auditing authorization behavior.
How do I save the generated Supabase diagram?
Select Download SVG after the diagram renders. The browser saves a scalable vector file that can be opened directly, embedded in documentation, or attached to a pull request. Because SVG stays sharp at any size, it works well for architecture notes, migration reviews, and onboarding material.
Go from Supabase schema to dashboard
Connect Supabase to Basedash and build charts from your live data.