# Manage Logs Ingest usage

Logs pricing is being rolled out. Quotas and rates on this page are confirmed but billing enforcement is not yet live. This page will be updated when the rollout is complete.

## What you are charged for

You are charged for the total volume of log data that Supabase ingests across all your project's services (Postgres, API gateway, Auth, Storage, Realtime, Edge Functions, etc.) during the billing cycle, measured in GB.

## How charges are calculated

Logs Ingest is charged per GB of log data ingested during the billing cycle.

### Usage on your invoice

Usage is shown as "Logs Ingest" on your invoice.

## Pricing

per GB. You are only charged for usage exceeding your subscription plan's
quota.

| Plan       | Quota  | Over-Usage per GB      |
| ---------- | ------ | ---------------------- |
| Free       | 5 GB   | -                      |
| Pro        | 5 GB   |  |
| Team       | 5 GB   |  |
| Enterprise | Custom | Custom                 |

## Billing examples

### Within quota

The organization's Logs Ingest usage is within the quota, so no charges for Logs Ingest apply.

| Line Item           | Units     | Costs                    |
| ------------------- | --------- | ------------------------ |
| Pro Plan            | 1         |      |
| Compute Hours Micro | 744 hours |      |
| Logs Ingest         | 2 GB      |       |
| **Subtotal**        |           | **** |
| Compute Credits     |           | -    |
| **Total**           |           | **** |

### Exceeding quota

The organization's Logs Ingest usage exceeds the quota by 7 GB, incurring charges for this additional usage.

| Line Item           | Units     | Costs                      |
| ------------------- | --------- | -------------------------- |
| Pro Plan            | 1         |        |
| Compute Hours Micro | 744 hours |        |
| Logs Ingest         | 12 GB     |       |
| **Subtotal**        |           | **** |
| Compute Credits     |           | -      |
| **Total**           |           | **** |

## View usage

You can view Logs Ingest usage on the [organization's usage page](/dashboard/org/_/usage) of the Dashboard. The page shows the usage of all projects by default. To view the usage for a specific project, select it from the dropdown. You can also select a different time period.

## Optimize usage

Every service in your Supabase project automatically generates Logs — you don't write them directly. Log volume scales with your application's traffic and behavior. To reduce ingest volume:

- **Reduce log-level verbosity** in your Edge Functions and server-side code (for example, `info` → `warn` in production).
- **Audit verbose logging in your application code.** Application-level logs forwarded to Supabase services count toward ingest.
- **Cap log payload size.** Large structured payloads inflate GB-billed volume quickly.
- **Investigate spikes.** Use the [**Logs Explorer**](/dashboard/project/_/logs-explorer) section of the Dashboard to find services or endpoints producing unusually high volume.

## Exceeding Quotas

If you are on a paid plan and have [Spend Cap](/docs/guides/platform/cost-control#spend-cap) disabled or your organization is on Team Plan or above, you will pay for any overages.

When you are exceeding your quotas while being on a Free Plan or having [Spend Cap](/docs/guides/platform/cost-control#spend-cap) enabled, you will get a notification to your billing email address and put under a grace period. For more details, refer to our [Fair Use Policy](/docs/guides/platform/billing-faq#fair-use-policy).