TutorialApril 6, 2026

Postgres GUI Tutorial: Query & Browse Your PostgreSQL Database from the Browser

A complete walkthrough of the DevToolSets Postgres GUI — connect to any PostgreSQL server, explore tables, run SQL, review query history, and save connections securely.

What You'll Learn

How to connect using a connection URL or individual fields
Browsing database tables and viewing their structure
Writing and executing SQL queries
Reading query results and performance timing
Using query history to re-run past statements
Saving encrypted credentials for quick reconnection
Configuring SSL modes for secure connections

Prerequisites

Before you start, you'll need:

A running PostgreSQL server (local or remote)
A database user with appropriate permissions
The connection details: host, port, username, password, and database name

Tip: For a quick test, a local PostgreSQL instance with the default postgres user works fine.

Step 1: Connecting to Your Database

The Postgres GUI offers two connection modes. Pick whichever you prefer.

Scheme mode (connection URL)

Paste a full PostgreSQL connection string into the URL field:

postgresql://user:password@host:5432/dbname

This is handy when you already have a connection string from your hosting provider or .env file.

Standard mode (individual fields)

Fill in each field separately:

Host — defaults to localhost
Port — defaults to 5432
Username — your database user
Password — the user's password
Database — the database to connect to
SSL — choose from disable, require, prefer, or verify-full

Open the Postgres GUI

Navigate to the Postgres GUI tool. You'll see the connection panel.

Choose your mode and fill in details

Toggle between Scheme and Standard using the tabs at the top of the form. Enter your credentials.

Click Connect

The tool tests the connection and loads your database tables. If successful, you'll see the connected view with a query editor and table browser.

Step 2: Browsing Tables

View the Tables tab

Once connected, the bottom panel shows a Tables tab listing all tables in the public schema. Each entry shows the table name, column count, and estimated row count.

Click a table to inspect it

Clicking a table name automatically runs a SELECT * FROM tablename LIMIT 200 query, showing you the data in the Results tab. This is a quick way to peek at any table's contents without writing SQL.

Step 3: Running SQL Queries

Write your SQL

The query editor is on the right side of the connected view. It comes pre-filled with a sample query:

SELECT current_database(), current_user, version();

Replace it with any SQL you want to run.

Execute

Click the Run button or use the keyboard shortcut. The query is sent to your PostgreSQL server and results appear in the bottom panel.

Read the results

The Results tab shows your query output in a table format. Above the results, you'll see the execution time so you can gauge query performance.

If there's an error, it's displayed clearly with the PostgreSQL error message so you can debug quickly.

Example queries to try

SELECT tablename FROM pg_tables WHERE schemaname = 'public';

SELECT column_name, data_type FROM information_schema.columns WHERE table_name = 'your_table';

SELECT pg_size_pretty(pg_database_size(current_database()));

Step 4: Using Query History

Every query you run is saved to a local history (stored in IndexedDB, up to 20 entries). This makes it easy to revisit and re-run past queries.

How it works

Switch to the History tab in the bottom panel
You'll see your recent queries listed with timestamps
Click any entry to re-run it instantly
History persists across sessions — it's stored in your browser
Older entries are automatically pruned when the limit is reached

Step 5: Customizing the Layout

The connected view uses a resizable split layout. You can drag the dividers to adjust the space between panels:

Drag the horizontal divider between the connection info and query editor to give more room to either side
Drag the vertical divider between the top panels and the bottom results/tables area to see more results or more of your query

Step 6: Saving Credentials for Quick Access

Tired of typing your connection details every time? Save them locally in your browser, encrypted with a PIN.

Check "Save credentials in browser"

On the connection form, tick the checkbox. Two new fields appear: a label and a master PIN.

Set a label and PIN

Give the connection a recognizable name (e.g. "Production DB" or "Local Dev"). Choose a 4-6 digit numeric PIN. Your credentials are encrypted with AES-256-GCM using a key derived via PBKDF2 and stored in IndexedDB.

Reconnect later

Next time you visit, your saved connections appear at the top of the connection panel. Click one, enter your PIN, and click Unlock — your fields are filled in automatically.

Delete a saved connection anytime by clicking the ✕ button next to it. Credentials are never sent to any server — everything stays in your browser.

Configuring SSL

When connecting to remote PostgreSQL servers (especially cloud-hosted ones), you'll likely need SSL. The Standard connection mode offers four SSL options:

disable — No SSL. Fine for local development.

prefer — Use SSL if the server supports it, fall back to plain otherwise.

require — Always use SSL, but don't verify the server certificate. Good for most cloud providers.

verify-full — SSL with full certificate verification. The most secure option.

Tips & Best Practices

Use a read-only database user when you just need to browse — it prevents accidental data modifications
Add LIMIT to your queries when exploring large tables to keep results manageable
The execution time shown after each query is the server-side time — use it to identify slow queries
The connection is automatically cleaned up when you close the tab or navigate away, so you don't need to worry about lingering sessions
Query history is per-browser and stored locally — it won't sync across devices
For cloud databases (AWS RDS, Supabase, Neon, etc.), use require SSL mode and the connection string from your provider's dashboard

Ready to try it out?

Open Postgres GUI →