SSupabaseHelp Center

Guide

Change Compute Size

7 stepsAgent View (JSON)

Overview

Supabase allows you to scale your database infrastructure by upgrading your project's compute size. Changing compute size adjusts your database's memory allocation, CPU cores, and hourly cost—critical decisions for managing performance and expenses. This workflow guides you through accessing compute settings, selecting a new size tier, reviewing the impact, and either confirming or canceling the change. Understanding this process ensures you can confidently upgrade your project when traffic increases or performance optimization becomes necessary, while also providing a safety net to cancel changes before they take effect.

Before you begin

  • Active Supabase account with at least one existing project (free account acceptable)
  • Owner or admin-level permissions on the target project
  • Access to supabase.com and ability to log in to your account

Step by step

1
ClickProject Settings

Navigate to your project's settings by clicking the 'Project Settings' link in the left sidebar. This opens the main settings dashboard where all project configuration options are available.

Tip. Project Settings is typically one of the first items in the sidebar menu. If you don't see it, ensure you're logged into Supabase and viewing a specific project (not the organization overview).
Step 1
2
ClickCompute and Disk

Access the compute configuration panel by clicking 'Compute and Disk' in the settings menu. This section controls your database's resource allocation and associated costs.

Tip. This menu item may be grouped under 'Billing' or 'Infrastructure' depending on your Supabase UI version. Scroll down in the settings menu if you don't immediately see it.
Step 2
3
ClickNanoUp to 0.5 GB memoryShared CPU

Confirm your current compute size is Nano by clicking its radio button. This establishes the baseline for comparison when you select a larger size.

Tip. The Nano tier displays 'Up to 0.5 GB memory' and uses a shared CPU. This is the starting size for most new projects.
Step 3
4
ClickSMALL $0.0206 / hour 2 GB memory 2-core ARM CPU

Upgrade to the Small compute size by clicking its radio button. The Small tier provides 2 GB memory, a 2-core ARM CPU, and costs $0.0206 per hour, offering significantly more capacity than Nano.

Tip. Notice the pricing difference displayed on the Small option. Supabase bills by the hour, so the daily and monthly cost will scale accordingly. Consider your expected traffic pattern before committing.
Step 4
5
ClickNanoUp to 0.5 GB memoryShared CPU

Revert your selection back to Nano by clicking its radio button again. This demonstrates the ability to change your mind before finalizing, simulating a typical workflow where users explore options before committing.

Tip. You can switch between compute sizes multiple times before reviewing. The interface does not apply changes until you explicitly confirm them.
Step 5
6
ClickReview changes

Review the pending changes by clicking the 'Review changes' button. This opens a summary showing what will change (in this case, no actual change since you reverted to Nano), allowing you to verify details before committing.

Tip. The review screen typically shows the before-and-after compute configuration, estimated cost impact, and any migration notes. Take time to confirm the changes match your intentions.
Step 6
7
ClickCancel

Cancel the pending changes by clicking the 'Cancel' button. This discards any modifications and returns you to the compute settings page with your original configuration (Nano) intact.

Tip. Canceling at the review stage prevents any charges or infrastructure changes from taking effect. No action is billed or applied when you cancel.
Warning. Clicking 'Cancel' abandons all pending changes. If you intended to confirm the upgrade, you'll need to repeat the selection and review process.
Step 7

Confirm it worked

  1. 1You see the Project Settings page load successfully with the sidebar menu visible
  2. 2The 'Compute and Disk' option appears in the settings navigation menu
  3. 3Radio button options for compute sizes (Nano, Small, etc.) are displayed with their specifications (memory, CPU type, hourly rate)
  4. 4After clicking 'Cancel', the compute size remains unchanged at Nano and you return to the settings view without any pending changes

Common issues

Keep reading

Resize a virtual machine - Azure Virtual Machines | Microsoft Learn

# Resize a virtual machine - Azure Virtual Machines | Microsoft Learn Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets This article shows you how to change an existing virtual machine'

learn.microsoft.com

How to Resize an EC2 Instance (Change Instance Type)

How to Resize an EC2 Instance (Change Instance Type) # How to Resize an EC2 Instance (Change Instance Type) Step-by-step guide to changing the instance type of an EC2 instance, including compatibili

oneuptime.com

Change the size of a Persistent Disk  |  Compute Engine  |  Google Cloud Documentation

Change the size of a Persistent Disk | Compute Engine | Google Cloud Documentation # Change the size of a Persistent Disk If your virtual machine (VM) instance requires additional storage space or i

cloud.google.com