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.

When any card shows pressure in the last 24 hours, an Instance upgrade recommended notice appears below the cards with an Ask Lovable button. Click it to send a chat message that asks Lovable to inspect your database and suggest query or code changes that reduce the load, so you may not need a larger instance. This message is treated as standard chat usage and consumes credits.

Lovable also alerts you when your instance reaches a resource limit. A Cloud instance needs attention notice appears in More → Cloud → Overview and in the chat, and both open Advanced settings so you can review the cards and resize. The project owner also receives a Database limit reached in-app notification that opens the project.

Before you upgrade, check whether slow queries are the real cause. See Find and fix database performance problems.

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.

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.

Ask Lovable to resize your instance

On Pro plans and higher, you can also ask Lovable in chat to resize the instance instead of opening Advanced settings yourself. When you describe database slowness, Lovable can offer a resize approval card with a size picker (Tiny through X-Large). The resize only applies after you pick a size and approve it.

For example:

My database feels slow under load. Resize my Cloud instance to a larger size.

Lovable first checks that the instance size, rather than storage or a slow query, is the cause, then offers the size picker. 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.

Export Lovable Cloud data

Use Export project data when you need a copy of your database, for example before moving your backend to another provider.

The export contains your full database, both structure and data. It does not include files in storage, Edge Function code, or your project’s secrets, so plan to move those separately. The export does not include user passwords in a usable form either, so plan a password reset flow for migrated users.

1. Open Advanced settings

   In your project, go to More → Cloud → Overview → Advanced settings.

2. Open the export dialog

   In Export project data, click Export data.

3. Start the database export

   In the Database card, click Export. In the confirmation dialog that appears, click Start export.

4. 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.

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.

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.

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, open it in the editor and click Wake up in the chat notice or on the paused project card in More → Cloud → Overview. A project can also pause with the message “This project is paused due to a low balance” when your workspace runs out of credits or reaches a credit limit. In that case, add credits or adjust the limit first. See Credits and usage.

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.

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.

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.

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

1. Open Advanced settings

   In your project, go to More → Cloud → Overview → Advanced settings.

2. Open the removal flow

   In Remove Lovable Cloud, click Remove.

3. 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.

4. Type the project name

   Enter the project’s display name exactly to confirm.

5. Remove Lovable Cloud

   Click Remove to permanently delete the Cloud instance for the project.

FAQ

Why isn't my Cloud data loading?

Your data can fail to load when the project’s instance is too small for the amount of data and traffic it handles.

To fix it, go to More → Cloud → Overview → Advanced settings, click Manage next to Database size, and choose a larger instance size. After you switch to a larger instance, wait a few minutes for it to update. Your data should then load, and your Cloud project should work again.

A larger instance size can increase Cloud usage and use more credits. To review Cloud usage, go to Settings → Plans & credit usage → Usage details and select Run credits.

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.

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.

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.

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.