> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Advanced settings

> Manage the infrastructure behind your app's built-in backend (Cloud): check its resource health, resize it, increase database storage, export your data, and pause or remove it.

Advanced settings is where you manage the infrastructure behind a project's built-in backend (Cloud): its resource health, instance size, and database storage, plus data exports, pausing, and removal. To open it, go to **More → Cloud → Overview → Advanced settings**.

## Check your database's resource health

On all plans, Advanced settings opens with three cards: **CPU**, **Memory**, and **Disk**. Each card shows the last 24 hours as a row of hourly segments. Lovable highlights a segment when that resource was close to its limit during that hour, which the cards call pressure. Hover over a segment to see the hour it covers and whether pressure was detected. When the current hour is under pressure, the card also shows how much of that resource your database is using. A single hour of pressure can be temporary. Wait and check whether it continues before you resize.

The **Disk** card shows how much data your database reads and writes, not how full your storage is. To check storage, see [Increase database storage](#increase-database-storage).

When any card shows pressure in the last 24 hours, a notice below the cards reads **Your database reached a resource threshold**, with an **Ask Lovable** button. Click it to send a chat message that asks Lovable to find what is causing the pressure and suggest query or code changes that reduce the load, so you may not need a larger instance. This message is treated as standard build usage and consumes [credits](/introduction/credits-and-usage).

Lovable also alerts you when your instance reaches a resource limit:

* In **More → Cloud → Overview**, a **Cloud instance needs attention** notice opens Advanced settings so you can review the cards and resize.
* In the project chat, in the Publish dialog, and in **More → Cloud → Database**, a **Your app is under high load** notice appears with a **Resolve** button. The notice in the Publish dialog does not block publishing.
* The project owner receives a **Database limit reached** in-app notification that opens the project.

Click **Resolve** to send a chat message that asks Lovable to check whether the database is still under pressure, find the likely cause, and suggest query or code changes. The message is treated as standard build usage and consumes credits. When a larger instance is the right fix, Lovable shows the credit impact and offers the resize for your approval. Resizing from chat is available on Pro plans and higher. See [Ask Lovable to resize your instance](#ask-lovable-to-resize-your-instance).

<Tip>
  Before you upgrade, check whether slow queries are the real cause. See [Find and fix database performance problems](/features/database#find-and-fix-database-performance-problems).
</Tip>

## Upgrade instance

The **Database size** row shows your current instance size, the computing capacity your database runs on. Click **Manage**, choose a new size in the **Manage instance** dialog, and confirm the resize. A larger instance allows your app to handle more users and traffic. A larger instance also increases Cloud usage and uses more credits as your app usage grows.

* **Free plan users**: upgrade from **Tiny** to a larger instance by upgrading your plan at any time
* **Paid plan users**: choose a new instance size (**Tiny**, **Mini**, **Small**, **Medium**, **Large**, or **X-Large**). Larger sizes handle more traffic and cost more credits per hour while your app runs:
  * **Tiny**: great for trying things out
  * **Mini**: reliable for early projects
  * **Small**: room to grow with your app
  * **Medium**: extra capacity for growing apps
  * **Large**: steady choice for regular use
  * **X-Large**: built for high-demand apps

A resize takes a few minutes, with a brief interruption while the instance restarts. You can't make further changes until the resize finishes. You can choose a smaller size again later.

<Note>
  **Database size names changed on July 31, 2026.** The size previously called **Medium** is now called **Large**, the previous **Large** is now **X-Large**, and the previous **X-Large** is now **2X-Large**. **Medium** is now a new, smaller size that sits between **Small** and **Large**.

  No database was resized or upgraded, and hourly prices did not change. If your project runs on one of the renamed sizes, Advanced settings shows a **Database size names updated** notice.

  Some projects run on **2X-Large**, the largest size. It appears as your current size if your project uses it, but you can't select it, so a project that moves off it can't move back.
</Note>

### Estimated monthly Cloud cost

On all plans, workspace editors, admins, and owners can see **Estimated cost** under each size in the **Manage instance** dialog. Compare these monthly Cloud credit estimates before changing sizes.

Lovable uses your app's Cloud usage over the last 30 days to estimate the cost of each size. For new apps or apps without enough usage history, Lovable uses a default usage estimate instead.

The estimate includes your database server and other Cloud usage, such as storage. It excludes building with Lovable and AI usage in your app. Actual costs can change as your app's usage changes.

### Ask Lovable to resize your instance

On **Pro plans and higher**, you can also ask Lovable in the project chat to resize the instance instead of opening Advanced settings yourself. When you describe database slowness, Lovable can offer a resize approval card. The resize only applies after you approve it.

For example:

```text wrap theme={null}
My database feels slow under load. Resize my Cloud instance to a larger size.
```

Lovable checks that the instance size, rather than storage or a slow query, is the cause before it offers the resize. You can also choose a smaller size this way.

## Increase database storage

The **Database storage** row shows how much of your database storage your project uses. If storage is nearly full, click **Manage**, enter a new size in the **Increase database storage** dialog, and click **Increase storage size**. Confirm with **Increase storage**. When the new size is at least 1.5 times the current size, you also check a box to acknowledge that the increase raises storage costs.

A few constraints apply:

* The minimum size is 8 GB.
* Storage can only be increased, never decreased.
* You can change the storage size up to four times within 24 hours.
* A resize takes a few minutes. A larger storage size increases Cloud usage.

## Database location

The **Database location** row shows the region your database is hosted in and its PostgreSQL version. The region is set when Cloud is enabled and cannot be changed afterwards. See [Region selection](/features/cloud#region-selection).

## Export Lovable Cloud data

Use **Export project data** when you need a copy of your database, for example before you move your backend to another provider. For the full migration, see [Host backend and data on a managed provider](/tips-tricks/external-deployment-hosting#host-backend-and-data-on-a-managed-provider-supabase-example).

The export contains your full database, both structure and data. It does not include files in [storage](/features/storage), [Edge Function](/features/edge-functions) code, or your project's [secrets](/features/secrets), so plan to move those separately.

The export includes your users' accounts and their password hashes, the scrambled form in which passwords are stored. If you restore the export into a Supabase project, your users keep their passwords. Sign-in provider settings and your project's API keys are not part of the database, so configure them again at the destination. Users who are signed in when you switch need to sign in again. After restoring, test that sign-in works. See [Supabase's guide to migrating users between projects](https://supabase.com/docs/guides/troubleshooting/migrating-auth-users-between-projects).

<Steps>
  <Step title="Open Advanced settings">
    In your project, go to **More → Cloud → Overview → Advanced settings**.
  </Step>

  <Step title="Open the export dialog">
    In **Export project data**, click **Export data**.
  </Step>

  <Step title="Start the database export">
    In the **Database** card, click **Export**. In the confirmation dialog that appears, click **Start export**.
  </Step>

  <Step title="Download the export when it is ready">
    Lovable emails you a download link when the export is ready. Lovable also saves the export to your project's Cloud storage, so you can download it from **More → Cloud → Storage**. You can't download exports after you remove Cloud.
  </Step>
</Steps>

<Note>
  Lovable exports databases that use up to 15 GB of storage, and the export file itself can be at most 5 GB. You can request one export every 24 hours.
</Note>

You can only export while your backend is running. If the project is [paused](#pause-cloud), including when it pauses because your workspace ran out of credits or reached a credit limit, resume it first. See [What happens when you run out of credits](/introduction/credits-and-usage#what-happens-when-you-run-out-of-credits).

To download storage files, go to **More → Cloud → Storage**. Storage files are separate from your database, and the database export does not include them. See [Storage](/features/storage).

## Pause Cloud

If you want to save credits on a project you're not actively using, choose **Pause Cloud** to pause its backend: database, authentication, storage, and Edge Functions. You can resume the project at any time.

Lovable automatically pauses Cloud projects after a period of inactivity, so you usually don't need to pause an idle project yourself. Pause manually when your project has scheduled jobs or other background activity that keeps it active, because automatic pausing does not apply to those projects.

### How to pause your project

To pause your project, go to **More → Cloud → Overview → Advanced settings**, then in **Pause Cloud**, click **Pause**. In the confirmation dialog that appears, click **Pause Cloud**.

While paused, your backend is unavailable, and your published app can't read or write data until you resume.

### Resume a paused project

When a project is paused due to inactivity or because you paused it, open it in the editor and click **Wake up** in the project chat notice or on the paused project card in **More → Cloud → Overview**.

The paused project card in **More → Cloud → Overview** says why the project is paused. Three pauses need more than **Wake up**:

* **Your workspace is out of credits.** Add credits, then click **Wake up**. A top-up does not wake the backend by itself. See [What happens when you run out of credits](/introduction/credits-and-usage#what-happens-when-you-run-out-of-credits).
* **A credit limit was reached.** Click **Manage limits** on the card, or open [**Workspace settings → Usage limits & alerts**](https://lovable.dev/settings/alerts-limits) and raise or remove the limit. Then click **Wake up**.
* **Lovable paused the project for excessive Cloud usage.** This happens when a project's Cloud usage reaches an extreme level, far beyond what its plan covers. Adding credits does not resume it, and **Wake up** is not available. [Contact support](/introduction/support-policy#contact-support) with the project URL to have the project reviewed.

<Note>
  Storage usage continues while a project is paused because your data stays in place. To stop storage usage entirely, remove Lovable Cloud from the project instead.
</Note>

<Warning>
  If your app uses Edge Functions for AI features, payments, or sending emails, those stop working while paused, since Edge Functions are unavailable. Apps built before May 2026 are the most affected, since newer apps don't depend on Edge Functions.
</Warning>

## Remove Lovable Cloud

Use **Remove Lovable Cloud** when you no longer want a project to use the built-in database, storage, authentication, or Edge Functions.

<Warning>
  Removing Lovable Cloud permanently deletes your Cloud instance and cannot be undone. Export your database and download any storage files you need before continuing.
</Warning>

<Steps>
  <Step title="Open Advanced settings">
    In your project, go to **More → Cloud → Overview → Advanced settings**.
  </Step>

  <Step title="Open the removal flow">
    In **Remove Lovable Cloud**, click **Remove**.
  </Step>

  <Step title="Confirm the warnings">
    Check both boxes to confirm you understand Cloud features will stop working and that unexported data may be lost. The second box becomes available only after you check the first.
  </Step>

  <Step title="Type the project name">
    Enter the project's display name exactly to confirm.
  </Step>

  <Step title="Remove Lovable Cloud">
    Click **Remove** to permanently delete the Cloud instance for the project.
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="Why isn't my Cloud data loading?">
    Your data can fail to load for several reasons:

    * The instance is too small for the amount of data and traffic it handles.
    * A query has an error.
    * [Row level security policies](/features/database#row-level-security-rls-policies) block the query.
    * The backend is [paused](#pause-cloud), for example after your workspace runs out of credits or reaches a credit limit.

    Ask Lovable to inspect the error and run a [database health check](/features/database#database-health-check).

    If the health check shows the instance is under pressure, go to **More → Cloud → Overview → Advanced settings**, click **Manage** next to **Database size**, and choose a larger instance size. After the resize completes, try the failing action again. If the disk is full instead, [increase database storage](#increase-database-storage).

    A larger instance size can increase Cloud usage and use more credits. To review Cloud usage, go to [**Workspace settings → Plans & credit usage → Usage details**](https://lovable.dev/settings/billing) and select **Run credits**.
  </Accordion>

  <Accordion title="Does pausing my Cloud project stop all billing?">
    No. While a project is paused, its backend stops running, so it stops using credits for everything except storage. Storage usage continues because your data stays in place. To stop Cloud usage for the project entirely, remove Lovable Cloud instead.
  </Accordion>

  <Accordion title="Why didn't my paused Cloud project wake up on its own?">
    A paused Cloud project only resumes when you explicitly click **Wake up** on the paused project card in **More → Cloud → Overview**. Traffic to your published app does not resume a paused project, and neither does waiting.
  </Accordion>

  <Accordion title="Can I export my Cloud project to Supabase?">
    Lovable does not provide a one-click transfer from the built-in backend (Cloud) to Supabase. You can export your database from **More → Cloud → Overview → Advanced settings** and move your code with [Git sync](/integrations/git-sync-overview).

    Storage files are exported separately from **More → Cloud → Storage**. You must reconfigure authentication, secrets, environment variables, and any external services in the destination platform. For a step-by-step walkthrough, see [Host backend and data on a managed provider](/tips-tricks/external-deployment-hosting#host-backend-and-data-on-a-managed-provider-supabase-example).
  </Accordion>
</AccordionGroup>


## Related topics

- [Manage connectors in your workspace](/integrations/admin-controls.md)
- [Manage workspace members from the People tab](/features/people.md)
- [Lovable Cloud](/features/cloud.md)
- [Lovable changelog](/changelog.md)
- [Scan your projects for vulnerabilities with Wiz](/integrations/wiz.md)