Render connection guide
Render PostgreSQL Connection String
Choose the internal or external Render Postgres URL and connect from an app, psql, or a Mac database client.
Use the connection value generated by Render, keep it in an environment variable, and test it before changing application code. The URI shape below is a template, not a credential to paste unchanged.
- URI scheme
- postgresql://
- Default PostgreSQL port
- 5432
- Credential handling
- Environment variable or secret manager
- First test
- psql "$DATABASE_URL" -c "select current_setting('server_version');"
Connection string template
postgresql://USER:PASSWORD@HOST/DB_NAME?sslmode=requireReplace every uppercase placeholder. Percent-encode reserved characters in URI usernames and passwords.
Where to get the Render values
Open the Render Postgres dashboard and copy an Internal Database URL for Render services in the same region or an External Database URL for your local machine and outside services.
The failure mode worth checking first
The internal hostname only resolves on Render's private network. External connections should use TLS and the external URL. Treat the copied URL as a secret because it includes the password.
Test the connection
Run a cheap read-only command before migrations or application startup. That separates network, TLS, and authentication errors from framework configuration problems.
Connection check
psql "$DATABASE_URL" -c "select current_setting('server_version');"Open it in PostgresGUI
Paste the PostgreSQL URI into PostgresGUI or enter the same host, port, database, user, password, and SSL mode as separate fields. A desktop connection is useful for checking the visible schemas and role permissions before debugging the application layer.
Questions that come up
Should the connection string be committed to Git?
No. Commit an example with placeholders and load the real value from an environment variable or secret manager.
Why does a password with @ or # break the URI?
Those characters have meaning inside a URL. Percent-encode the username and password, or use a structured connection API instead of assembling a URL by hand.
Do I need sslmode=require?
Most hosted PostgreSQL services require TLS. For strict certificate and hostname verification, use sslmode=verify-full with the provider's trusted root certificate when the client supports it.