Neon connection strings: which branch, which pooler, which env?

Short answer: almost everything important in Neon lives under your project in the console at console.neon.tech.

The page people usually mean when they say "Neon connection string" is the project dashboard → Connection details (sometimes labeled Connection string). Copy the URI, pick the branch, pick pooled vs direct, move on.

Why Neon feels "easy" until it doesn't

Neon is simple when you have one project and one branch. It gets interesting the moment you have:

• a main branch for production
• a preview branch that CI created
• a personal branch you forgot about
• pooled connection for serverless
• direct connection for migrations

Same database product, five different strings, all of which look like Postgres URIs if you squint.

So "where's the connection string" is really "which branch + which pooler am I talking about?"

The pages I bounce between

I don't pretend these URLs never change — Neon iterates. But the destinations stay stable:

Console / projects — console.neon.tech
Pick the project. Always start here if you're lost.

Connection details — on the project page
This is the big copy button. Branch selector matters. Role matters. Pooled vs direct matters for Vercel / serverless.

Branches — project → Branches
Where preview databases come from. If prod looks fine and preview is empty, you're probably pointed at the wrong branch.

SQL Editor — project → SQL Editor
When you need to confirm "is the row actually there" without opening a local client.

Billing / usage — account level when something feels expensive
Neon is generous, but surprise scale still exists.

For a maintained jump list, see Neon on devlinkspad.

The classic Vercel + Neon mixup

You copy the connection string once. You paste it into Vercel Production. Everything works.

Two months later preview deploys fail. Or worse: preview writes to production.

Checklist I run:

1. Vercel env DATABASE_URL — which environments is it set for?
2. Is it the pooled string in serverless functions?
3. Did a Neon branch get deleted while Vercel still points at it?
4. Are you using the right role (not neon_superuser for the app if you don't need it)?

None of this is exotic. It's just easy to skip when you're tired.

If you only remember one habit

Don't paste connection strings into Slack. Don't screenshot them into Notion. Put them in Vercel / Doppler / wherever your secrets live, and treat the Neon console as the source you copy from, not the place you re-read every day.

And when you need the console again: ⌘K → neon beats re-finding the bookmark.

---

devlinkspad is not affiliated with Neon. Links go to official dashboards.