Download and set up pgAdmin for PostgreSQL
Get pgAdmin from the official project website and choose the installer for your operating system. You’ll also need a PostgreSQL server to connect to. The client installation and the database server are separate parts of the setup.
Choose the official installer
The pgAdmin download page links to Windows, macOS, Linux and container options. Follow the current requirements on the platform page rather than choosing a package solely because its filename appears in a search result. Older searches for pgAdmin 3 refer to an earlier generation; begin with the current pgAdmin 4 documentation for a new installation.
On a work computer, use the installation method your administrator supports. If you prefer Homebrew or a Linux package manager, check the package’s publisher, architecture and version before installing. An unofficial mirror is unnecessary when the project provides a suitable package.
Prepare the connection details
- The PostgreSQL host and port supplied by the server owner.
- A database name and a PostgreSQL role permitted to connect.
- The role’s password or the approved authentication method.
- The required TLS settings and network access.
Do not substitute your pgAdmin application login for a PostgreSQL database password. For a hosted database, localhost usually points at the wrong machine. Use the connection walkthrough once the application opens.
Desktop or browser deployment?
For individual desktop work, an installer is a straightforward starting point. A shared web deployment introduces application accounts, server maintenance and network access decisions. Read the web and Docker guide before treating those as interchangeable setups.
When to consider another client
pgAdmin is a PostgreSQL-focused choice. If the same workday includes SQLite or MySQL, compare a multi-engine client. PlainDB supports those engines on Mac and Windows, with feature differences listed in its matrix. Use the PostgreSQL GUI checklist to evaluate a real connection and export workflow.