How to view a Supabase database: tables, SQL and desktop clients
For a quick look at Supabase rows, open your project’s Table Editor. Use SQL Editor when you need a query, or connect a desktop PostgreSQL client when you work across databases. Here’s how to get started and check that you’re viewing the right data.
Choose a way to inspect your data
| Your task | Starting point |
|---|---|
| Look at one table’s rows and columns | Supabase Table Editor |
| Join tables or calculate a summary | Supabase SQL Editor |
| Work across several database connections | A desktop PostgreSQL client |
| Manage Auth, Storage or Edge Functions | The relevant Supabase dashboard section |
View tables in the dashboard
Sign in to Supabase and open the intended project. Choose Table Editor, select the schema containing your application tables, and open a table. If the result is empty, check the project and schema first. Development and production can have tables with the same name and different data.
Supabase’s tables documentation explains how schemas organize tables and how the dashboard works with them. Start by inspecting existing data. You do not need to create a table, disable security or modify a row just to understand the schema.
Inspect the schema with SQL
In SQL Editor, run this metadata query to see the columns visible to your database role. It reads the catalog rather than your application’s row contents:
SELECT table_schema, table_name, column_name, data_type
FROM information_schema.columns
WHERE table_schema = 'public'
ORDER BY table_name, ordinal_position;If your application uses another schema, replace public. An empty result is a prompt to check the schema, project and role; it is not evidence that every table in the database is empty.
Next, inspect a bounded sample. This illustrative query assumes your own table has an id and a title column; replace them with names from your schema:
SELECT id, title
FROM public.tasks
ORDER BY id
LIMIT 50;Choose only the columns you need. A limit keeps the output manageable, but does not guarantee a cheap query when sorting or filtering a large table.
Use a desktop client for repeated work
Copy the database connection details from your project’s Connect panel and follow our Supabase connection guide. A database password is different from a project API key. Use the documented endpoint for your network and tool, with TLS enabled.
plainDB connects to the PostgreSQL database behind Supabase. It provides a desktop workspace for database browsing and SQL work; it does not administer every Supabase service. Check the Mac and Windows feature matrix before choosing a workflow.
Why can I see rows here but not in my app?
Compare the identity and permissions used by each route. Dashboard administration, a direct database role and an authenticated API request can have different visibility. Seeing a row in an administrative tool does not prove an application user can read it. Use Supabase’s RLS guide to test the intended role; do not turn RLS off as a viewing workaround.
Continue with the SQL Editor walkthrough or export checklist.