Supabase PITR (point-in-time recovery), explained

Supabase PITR is an add-on that restores your database to any second within a retention window, instead of to last night’s backup. It works by continuously archiving write-ahead log files on top of physical backups. It costs $100/month per project for a 7-day window and replaces daily backups rather than adding to them.

This guide covers how it works, how it compares with daily backups, what the monthly bill comes to, what it does not cover, how long a restore takes, and how to turn it off.

How PITR works

Postgres writes changes to a write-ahead log before applying them to the data files, giving an ordered record of what happened to the database. One exception matters if you use it: UNLOGGED tables skip the WAL by design, so PITR does not cover their contents, just as crash recovery does not. PITR keeps those log files alongside a base backup. To reach any moment in time, you restore the base backup and replay the log up to that point. Supabase implements this with WAL-G, an open-source archival tool, combining physical backups with WAL archiving.

The archiving schedule is the part to understand. Supabase backs up WAL files at two-minute intervals by default, more often when a file crosses a size threshold or transaction volume is high, and not at all while the database is idle. Supabase’s docs put the worst-case RPO at two minutes: up to about two minutes of recent writes may not be archived yet when a failure hits. Plan with that figure, but before you put a number in a recovery plan, check the latest recovery point the dashboard shows, because that is the point you can restore to. On an idle database the newest restore point can be much older than two minutes. That is fine: there were no writes to archive, so that point still matches the current state.

For a table dropped at 14:32:06 none of this matters; you are targeting a moment in the past and the log for it was archived long ago. It matters for hardware failure, where the loss is whatever had not been archived at the instant things stopped.

Supabase PITR vs daily backups

Daily backups come with every paid plan. PITR is what you buy when a day of lost writes is too much. Here is how they compare:

Compared onDaily backupsPITR
What you can restore toThe moment each daily backup was takenAny second inside the window
Worst-case data lossUp to about 24 hours of writesAbout two minutes, Supabase’s stated worst case
How far back7 days on Pro, 14 on Team, up to 30 on Enterprise7, 14 or 28 days, depending on the window you buy
PriceIncluded in the plan (Pro is $25/month per organization)$100, $200 or $400/month per project, on top of the plan
Download a backup fileOnly on projects still on the older logical backup processNo. PITR runs on physical backups
Storage filesNot includedNot included
Once PITR is enabledSupabase stops offering themIt is your only way to restore on Supabase
Where the backups liveInside your Supabase accountInside your Supabase account

If you can re-create up to a day’s writes by hand, daily backups may be enough. If data loss has to stay within minutes, PITR is Supabase’s native option. Neither includes Storage files or gives you a copy outside Supabase, and deleting the project deletes its backups too.

How to enable it

PITR is a per-project add-on on the Pro, Team, and Enterprise plans, switched on under Project Settings → Add-ons. Two things to know before you turn it on:

Any compute size works. Supabase used to require at least a Small compute instance for PITR. Since November 2026 its docs say PITR is available on all compute sizes, so a project on Micro can turn it on without a compute upgrade.

Backups become physical backups. PITR runs on physical backups, and physical backups cannot be downloaded. If your project was on the older logical backup process with a download button in the dashboard, enabling PITR takes that button away.

What PITR actually costs

The add-on is priced by retention window and billed hourly in arrears, per project. If PITR is active for part of an hour, the whole hour is charged, so turning it on briefly to test it still costs money.

Recovery windowPer hourPer month
7 days$0.137~$100
14 days$0.274~$200
28 days$0.55~$400

Those numbers are the add-on alone. With the plan included, one Pro project with 7-day PITR comes to $25 for Pro plus $100 for the add-on, roughly $125/month, with the plan’s $10 in compute credits covering the default Micro instance. Supabase’s own billing example comes to $130 because it puts the project on Small compute. Prices as of November 2026.

Two more billing details. It is priced per project, so three projects cost three times as much. And the PITR add-on is not covered by the Spend Cap, so the limit that keeps other usage from running up your bill does not apply to it.

What Supabase backups cost overall: Free, Pro, PITR, and third-party tools

If you are pricing PITR, you are probably also asking what backups cost in general. Here are the options as of October 2026, with each option’s billing unit, because they differ: Supabase bills the plan per organization and PITR per project, while most services price a bundle of projects.

OptionPriceWhat you get
Supabase Free$0No scheduled backups you can use. Supabase's docs say up to 7 daily backups exist and unlock on upgrade; on Free you export yourself with pg_dump or the CLI
Supabase Pro$25/month per organization, plus compute per projectDaily backups, 7-day retention; Team ($599/month) keeps 14 days
PITR add-on$100 / $200 / $400 per month per project, on top of the planRestore to any second in a 7 / 14 / 28-day window; database only
DatabasusFree, self-hostedpg_dump backups with restore tests, on a server you run
SupabackupFree tier (1 job); Pro $9/month for 3 backup jobsDatabase dumps to your Google Drive: weekly on the free tier, daily on Pro
ReviveDBFree tier (1 project); Pro €9/month for 3 projectsDatabase, Storage files and Edge Functions to EU-hosted storage, each backup restore-tested
BackProve$12/month for up to 3 projectsDatabase plus Storage files, restore-tested daily
SimpleBackupsFree tier; paid from $49/monthDatabase and Storage to storage you choose; no automated restore test
BackupDrillFree (1 project, weekly); Solo $19/month for up to 5 projectsDatabase, plus Storage files once you add the project's Storage S3 keys, into your own bucket, with daily restore drills on paid plans

Two things the table doesn’t show. Everything Supabase sells here stays inside your Supabase account: delete the project and its backups go with it, and a billing suspension puts them out of reach until the invoice is paid. And only four of these options restore a backup to check that it works: Databasus, ReviveDB, BackProve, and BackupDrill. The native options and the other services tell you a backup file exists, not that it restores.

What it covers, and what it does not

AssetUnder PITR
Tables, rows, indexes, functions, policiesCovered, except UNLOGGED tables, which never reach the WAL
Auth users (they live in the database)Covered
Storage files uploaded via the Storage APINot covered (metadata only)
Edge FunctionsNot covered
Project settings, API keys, Realtime configNot covered
A copy outside SupabaseNot covered: physical backups cannot be downloaded

The Storage row is the costly one, though the damage is partial rather than total. The object store is not rolled back with the database, so restoring to 14:00 yesterday leaves files that existed then and still exist working normally. What breaks is anything that changed after 14:00: files deleted since then come back as storage.objects rows pointing at objects that are gone, and files uploaded since then stay in the bucket as orphans with no row describing them. Your app can’t see them, but they are still on your storage bill. If you restore into a new project instead, it is simpler and worse: none of the files come with it. The Storage backup guide covers the separate copy those files need. PITR does not back them up at any price.

How to run a PITR restore, and how long it takes

The steps are short: Database → Backups, the Point in Time tab, pick the timestamp, confirm. Two things to decide before you click. First, the timestamp is entered in the timezone the dashboard shows. Check it instead of assuming UTC: a few hours off can take you to a point after the mistake you are trying to undo. Second, an in-place restore overwrites the current database. Everything written between your target time and now is discarded, including correct writes made after the mistake. If you can’t lose those, use Restore to a new project from the PITR timestamp instead, then move only the rows you need across. It leaves production up while you work.

How long it takes is harder to pin down, and Supabase does not publish a number. Its troubleshooting docs name three things that drive it: the time since the last full backup, which Supabase takes weekly; how much WAL has been written since then; and the size of the database. An in-place restore keeps the project offline until it finishes. Restoring a busy database to a point several days after its last full backup means more WAL to replay, which can mean a longer outage.

We have not timed a Supabase PITR restore. What we have timed is the other way back: restoring a pg_dump file, the kind of backup you keep outside Supabase, into a fresh Postgres. On a 2 vCPU machine with durability settings turned off on the target, a 10 GB database took about 12 minutes, and most of that went to rebuilding indexes and foreign keys rather than loading rows. The numbers by size are in our Postgres restore time benchmark. PITR reduces how much data you lose, but a restore still takes time, and an in-place restore still means downtime.

How to remove point-in-time recovery (and what happens to your backups)

Same place you enabled it: Project Settings → Add-ons, remove the Point-in-Time Recovery add-on. Because billing is hourly, charges stop from the time of removal rather than at the end of a billing cycle. A project that ran PITR for a weekend is billed for a weekend.

Turning PITR off does not bring back downloadable backups. Supabase’s docs state that when PITR is disabled, new backups are still taken as physical backups only, and physical backups are not available for direct download. If you planned to disable PITR to get files you can keep, that won’t work. You need your own logical dump, which the .sql export guide covers. You can run that dump at any time, before or after removal; disabling PITR does not affect pg_dump. What you lose is the ability to restore to a moment between backups. The plan’s scheduled backups still exist and still restore, and the backups page lists them. Supabase’s docs don’t say how long earlier recovery points stay available after PITR is turned off. If there is a specific moment you might need, such as the state before a migration or last Tuesday’s data, restore or clone to it while PITR is still on.

Is Supabase PITR worth it?

It gives you the finest recovery granularity available for a Supabase database. If losing a day of writes would be a serious business problem (a transactional app, anything with payments, anything where users create content all day), that is worth paying for, and $100/month is a reasonable price. No snapshot tool can restore a Supabase database to 14:32:06.

Where it fits poorly: it is priced per project, so the cost adds up fast across several small projects. It covers the database only. It keeps no copy outside Supabase: deleting the project removes its PITR history, and an account or billing problem can block access to it, so a disaster recovery plan needs a copy elsewhere. And it tells you nothing about whether a restore works until the day you run one.

PITR and an external backup have different gaps, so running both is not redundant: PITR for second-level recovery, a snapshot in your own bucket for a copy outside Supabase. The side-by-side comparison with BackupDrill goes through cost and coverage in detail, including when PITR is the better choice.

FAQ

How much does Supabase PITR cost?

The add-on is $100/month per project for a 7-day recovery window, $200/month for 14 days, and $400/month for 28 days, billed by the hour while it is active, and a partial hour is charged as a full hour. Those figures are the add-on alone. Add the $25 Pro plan and a single project with 7-day PITR comes to about $125/month in total. It runs on any compute size, and the plan's $10 in compute credits cover the default Micro instance. The add-on is not covered by the Spend Cap.

Is Supabase PITR worth it?

It is when losing a day of writes would be a real business problem: payments, orders, anything users create all day long. About $125/month for one project (the $100 add-on plus the Pro plan) buys you a restore to any second of the last 7 days. It fits poorly when you run several small projects, because it is priced per project, and it still covers only the database and keeps no copy outside Supabase.

How do I remove point-in-time recovery from a Supabase project?

Go to Project Settings, then Add-ons, and remove the Point-in-Time Recovery add-on. Billing stops right away. Before you turn it off, know that according to Supabase's docs, backups taken after PITR is disabled are still physical backups, and physical backups cannot be downloaded. Turning PITR off will not get you downloadable backup files.

How much do Supabase backups cost?

On the Free plan there are no scheduled daily backups you can restore or download. The exception is the snapshot taken when a free project is paused, which the dashboard lets you restore or download. Supabase may also take daily backups of free projects, but you can only access them after upgrading. So on Free you export the data yourself. Pro is $25/month and includes daily backups with 7-day retention. PITR is an add-on on top of Pro: $100/month per project for a 7-day window (about $125 with the Pro plan itself), $200 for 14 days, $400 for 28. Third-party services start free and run $9–$49/month; BackupDrill's paid plans start at $19/month.

Does Supabase PITR back up Storage files?

No. PITR covers the Postgres database only. Files uploaded through the Storage API live in a separate object store that a restore does not roll back, so the failure is a mismatch rather than total loss: files present at both the restore point and now still work, files deleted since the restore point come back as metadata rows pointing at objects that are gone, and files uploaded since become orphans in the bucket with no row describing them. If you restore into a new project instead, none of the files are there at all. Either way, Storage needs its own backup.

Does enabling PITR replace daily backups?

Yes. Once PITR is enabled, you no longer get daily backups to choose from; Supabase's docs say PITR is finer-grained, so you don't need both. Supabase still takes a daily physical snapshot and archives WAL every two minutes, and you restore by picking a moment instead of a day. Within the window, that is the better option. It also means all of your recovery depends on one mechanism at one vendor, with no copy kept anywhere else.

What is the RPO of Supabase PITR?

Supabase's docs give a worst case of two minutes. WAL files are archived every two minutes by default, sooner when a file fills up or traffic is heavy, and not at all while the database is idle. Daily backups, by comparison, can lose up to about 24 hours of writes.

How long does a Supabase PITR restore take?

Supabase does not publish a figure. Its docs say restore time depends on how long it has been since the last full backup, which is taken weekly, how much WAL has been written since then, and the size of the database. The project is offline while an in-place restore runs, so plan for downtime; restoring to a new project keeps production up while you work.

Sources

  • Supabase docs — Database Backups (PITR, WAL-G, retention by plan)
  • Supabase docs — Manage Point-in-Time Recovery usage (pricing)
  • Supabase docs — Manage Compute usage (instance pricing and credits)
  • Supabase — Pricing
  • Supabackup — plans
  • ReviveDB — pricing
  • BackProve — pricing
  • Supabase blog — Point in Time Recovery is now available
  • Supabase docs — Restore to a new project
  • Supabase docs — How long does it take to restore a database from a PITR backup
  • BackupDrill — Postgres restore time benchmark

Facts and prices last verified October 31, 2026 (PITR compute sizes on November 6, 2026) against the sources above. Written by the team behind BackupDrill.

Weighing $100/month against a copy you control? Read the side-by-side comparison, or start free and put a verified snapshot in your own bucket this afternoon.