apps/docs/content/docs.v6/orm/tools/prisma-studio.mdx
Prisma Studio is a standalone visual database editor that lets you view and manipulate data directly in your browser. Prisma 7 introduces a brand new standalone Studio, built from the ground up to work everywhere, with or without Prisma ORM.
Unlike previous versions, the new Prisma Studio is SQL-driven and does not rely on the Prisma schema file at all. Instead, it introspects your database directly to understand the schema structure. This means you can use it with any supported database without needing a Prisma schema or project.
Note that Prisma Studio is not open source but you can still create issues in the prisma/studio repo. All "old Studio" issues are being closed as there won't be any further work on the previous version.
Prisma Studio is a standalone tool that only requires a database connection. You have two options:
Connect directly to any supported database using the --url flag:
npx prisma studio --url="postgresql://user:password@localhost:5432/dbname"
This approach works without any Prisma ORM setup—Studio will introspect your database schema directly.
If you have an existing Prisma project, Studio can read your database connection configuration:
prisma.config.ts configuration file with database connection details:::note
The new Studio does not read the prisma/schema.prisma file. It introspects your database directly to understand the schema structure.
:::
To launch Prisma Studio with any database, provide a connection URL:
npx prisma studio --url="postgresql://user:password@localhost:5432/dbname"
If you have a Prisma project, run the following command in your project directory:
npx prisma studio --config ./prisma.config.ts
Both commands start a local web server (default port 5555) and open Prisma Studio in your browser. Studio connects directly to your database and introspects the schema in real-time to provide a visual interface for your data—no Prisma schema file required.
Prisma Studio provides several key capabilities for working with your database:
Studio displays all tables from your database in a sidebar. Select any table to view its data in a table format. You can open multiple tables in separate tabs to work with related data simultaneously.
You can edit data in two ways:
Changes are accumulated and must be saved explicitly using the save button. This lets you make multiple edits before committing them to the database.
Create new records by clicking the "Add record" button. Studio provides appropriate input controls based on each field's data type:
Select one or more records using the checkboxes and click the delete button. Deletions require confirmation and are applied immediately (they cannot be batched with other changes).
Use the Filters menu to narrow down your data:
Customize your view:
Click any column header to sort by that field. Click again to toggle between ascending and descending order.
Studio supports keyboard shortcuts for common operations. Press <kbd>Cmd</kbd>+<kbd>/</kbd> (macOS) or <kbd>Ctrl</kbd>+<kbd>/</kbd> (Windows) to view all available shortcuts.
Studio displays visual indicators for different field types in your database:
These visual cues help you quickly understand your data structure as Studio introspects it directly from your database.
Prisma Studio currently supports the following databases: PostgreSQL, MySQL, and SQLite.
file: protocol right now in the database url for SQLitenode:sqlite module
NODE_OPTIONS=--experimental-sqlite environment variablebetter-sqlite3 as a dependency
pnpx, you'll need the --allow-build=better-sqlite3 flag:::tip[Using npx with better-sqlite3]
If you don't have node:sqlite available in your runtime or prefer not to install better-sqlite3 as a hard dependency (it adds ~10MB), you can use npx to temporarily install the required packages:
npx -p better-sqlite3 -p prisma prisma studio --url file:./my_file.db
This command:
better-sqlite3 without adding it to your project dependenciesbetter-sqlite3 in your project:::
Support for CockroachDB and MongoDB is not currently available but may be added in future releases. If you're using these databases:
When connecting to PostgreSQL databases, you may encounter this error if your connection string includes the schema query parameter:
unrecognized configuration parameter "schema"
This happens because the new Studio is standalone and passes your connection URL directly to the PostgreSQL driver without any processing. The URL you provide—whether via prisma.config.ts or the --url flag—must be a valid PostgreSQL connection string that only uses standard PostgreSQL connection parameters.
The schema parameter was a custom Prisma ORM parameter that worked in v6 and earlier, but PostgreSQL itself doesn't recognize it.
To resolve this issue, use the standard search_path parameter instead:
# ❌ This will cause an error
postgresql://user:password@host:port/database?schema=my_schema
# ✅ Use this instead
postgresql://user:password@host:port/database?options=-c%20search_path%3Dmy_schema
Alternatively, you can remove the schema parameter entirely if you're using the default public schema, as PostgreSQL defaults to it automatically.
For more details, see the related GitHub issue.
Caching issues may cause Prisma Studio to use an older version of the query engine. You may see the following error:
Error in request: PrismaClientKnownRequestError: Failed to validate the query Error occurred during query validation & transformation
To resolve, delete the following folders:
~/.cache/prisma on macOS and Linux%AppData%/Prisma/Studio on Windows