timetobail
My stack

Supabase · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Supabase legacy anon and service_role keys?

Time to Bail · Boarding pass

FromSupabase legacy anon and service_role keys
ToYour pick

Act. You can stay.

Supabase is deprecating these keys by the end of 2026. No exact day is given yet, so switch keys now.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
No set date
Check the notice for the date on your plan.
Time left
No set date
Status
Act

Supabase deprecates anon and service_role keys by the end of 2026

Supabase is deprecating the legacy anon and service_role API keys by the end of 2026. It has not given an exact day. Apps should switch to publishable and secret keys now.

What to do next

Tick steps as you go. Your progress stays in this browser.

  1. Create the new keys

    In the Dashboard, open Settings > API Keys and create a publishable key and a secret key.

  2. Swap keys in your code

    Put the publishable key in client code and the secret key in backend code and Edge Functions.

  3. Check, then turn off the old keys

    Make sure nothing uses the anon or service_role keys, then deactivate them in the Dashboard.

Facts we checked

Facts and their sources
Deprecated byThe end of 2026; Supabase gives no exact day ("Late 2026, TBC")[1]
KeysThe legacy anon and service_role API keys[1]
Use insteadPublishable keys (sb_publishable_...) and secret keys (sb_secret_...)[1]
Can both work at once?Yes. New keys do not revoke the old ones[1]
If you do nothingYour app will break when the legacy keys are removed[2]
Restored projectsProjects restored from November 1, 2025 no longer get legacy keys[2]
Apps that use the legacy keysMust switch before the keys are removed[2]

Sources

Check it yourself. Every fact above links here.

  1. Understanding API keys Supabase · primary · checked Oct 13
  2. Upcoming changes to Supabase API keys Supabase · primary · checked Oct 13
  3. Migrating to new API keys Supabase · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Supabase legacy anon and service_role keys? Act. You can stay. Supabase is deprecating these keys by the end of 2026. No exact day is given yet, so switch keys now.

On our scale this is Act: change a setting or plan before the date. You can stay.

Supabase is deprecating the legacy anon and service_role API keys by the end of 2026. It has not given an exact day. Apps should switch to publishable and secret keys now.

Here are the facts we checked:

  • Deprecated by: The end of 2026; Supabase gives no exact day ("Late 2026, TBC") (Supabase)
  • Keys: The legacy anon and service_role API keys (Supabase)
  • Use instead: Publishable keys (sb_publishable_...) and secret keys (sb_secret_...) (Supabase)
  • Can both work at once?: Yes. New keys do not revoke the old ones (Supabase)
  • If you do nothing: Your app will break when the legacy keys are removed (Supabase)
  • Restored projects: Projects restored from November 1, 2025 no longer get legacy keys (Supabase)
  • Apps that use the legacy keys: Must switch before the keys are removed (Supabase)

You can stay on Supabase. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Supabase is the main source for this page. Supabase has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Apps that use the legacy keys: Must switch before the keys are removed.

There is no single date for everyone. Check the date in your own account.

What to do now

  1. Create the new keys. In the Dashboard, open Settings > API Keys and create a publishable key and a secret key.
  2. Swap keys in your code. Put the publishable key in client code and the secret key in backend code and Edge Functions.
  3. Check, then turn off the old keys. Make sure nothing uses the anon or service_role keys, then deactivate them in the Dashboard.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Supabase legacy anon and service_role keys can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product