Setting up your project

Get your keys

1. 1Go to supabase.com/dashboard and create a project. The free tier is enough. Pick a region close to your users and save the database password somewhere safe (you won't need it for this guide).
2. 2In the left sidebar open Project settings (the gear icon), then API.
3. 3Copy the Project URL. It looks like https://abcdefghijkl.supabase.co.
4. 4Copy the anon public key. Newer projects call this the publishable key and it starts with sb_publishable_; either works. Do not copy the service role or secret key, it must never be in a browser app.

Paste them into the env file

1. 1In the project folder, copy .env.example to .env.local. On macOS or Linux: cp .env.example .env.local. On Windows: copy .env.example .env.local.
2. 2Open .env.local and fill in both values:

NEXT_PUBLIC_SUPABASE_URL=https://abcdefghijkl.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=sb_publishable_xxxxxxxxxxxxxxxxxxxx
NEXT_PUBLIC_SITE_URL=http://localhost:3000

.env.local is ignored by git, so your keys stay out of version control. When you deploy, set the same variables in the host's environment settings, with NEXT_PUBLIC_SITE_URL changed to your real domain: the confirmation and reset emails link back to it.

Create the database table

1. 1In the Supabase dashboard open SQL editor and click New query.
2. 2Paste the contents of supabase/migrations/0001_profiles.sql from your project and click Run. This creates a profiles table with row-level security and a trigger that fills it in when someone signs up.

Allow sign-in redirects

1. 1Open Authentication → URL configuration.
2. 2Set Site URL to http://localhost:3000. When you deploy, change it to your domain, the same value as NEXT_PUBLIC_SITE_URL.
3. 3Under Redirect URLs add http://localhost:3000/auth/callback**. Add your production domain the same way later, for example https://example.com/auth/callback**. The two stars let the link carry a next= parameter, which the password reset uses.
4. 4The site asks Supabase to send people to NEXT_PUBLIC_SITE_URL + /auth/callback; a destination that is not on the Site URL's domain or in the Redirect URLs is ignored and the email links to the Site URL instead.
5. 5Optional: under Authentication → Providers → Email, turn off Confirm email while developing so you can sign in immediately after signing up.

Try it

1. 1Restart npm run dev so the new env file is read.
2. 2Open http://localhost:3000/signup, create an account, confirm the email if required, and sign in. You land on /account, where you can edit your name; it reads and writes your row in the profiles table.
3. 3Try Forgot password? on the sign-in page: the email link opens /reset-password with a recovery session so you can choose a new password.

Production email (recommended before launch)

1. 1Supabase's built-in mailer sends only a few emails per hour and is meant for testing. Before real users sign up, switch to your own SMTP.
2. 2If you enabled Resend: open Authentication → SMTP Settings, turn on Custom SMTP, and enter host smtp.resend.com, port 465, username resend, password = your Resend API key, sender = your EMAIL_FROM. Any other SMTP provider works the same way.
3. 3Under Authentication → Email Templates you can reword the confirmation and reset emails.

Google sign-in (optional)

1. 1In Google Cloud Console create an OAuth client ID of type Web application. Add https://YOUR-PROJECT-REF.supabase.co/auth/v1/callback as an authorised redirect URI (the exact value is shown in Supabase under Authentication → Providers → Google).
2. 2In Supabase open Authentication → Providers → Google, enable it, and paste the client ID and secret.
3. 3Set NEXT_PUBLIC_AUTH_GOOGLE=1 in .env.local and restart. A Continue with Google button appears on the sign-in and sign-up pages.

Prefer the CLI to the SQL editor?

1. 1Run npx supabase@latest login, then npx supabase@latest link --project-ref YOUR-PROJECT-REF (the ref is the first part of your Project URL).
2. 2Run npm run db:push to apply every file in supabase/migrations/. Re-run it whenever you add a migration.