Skip to content
Netlify Docs
For the complete Netlify documentation index, see llms.txt. Markdown versions of this page are available by appending .md to the URL.

Unlimited seats on Netlify Pro for $20/month → Learn more 👥

Functions usage and billing

For the complete documentation index, see llms.txt

How functions are billed, and what options you have for monitoring detailed usage, depend on whether you’re on a Credit-based plan or a Legacy plan.

If you’re unsure which plan you’re on, here’s how to check.

Credit-based plans

Section titled “Credit-based plans”

With a Credit-based plan, functions are billed through the compute metric in GB-Hour units.

The default memory allocation for Netlify Functions is 1024 MB (1 GB). For example, if the total runtime of all function invocations across your team is two hours, you will be billed for two GB-Hour units.

If you have a Credit-based Pro or Enterprise plan, you can increase the memory allocation of a function up to 4096 MB (4 GB), which also provides a proportionally higher vCPU allocation. For non-default memory allocations, GB-Hour units are calculated as the total duration of function invocations multiplied by the configured memory allocation in GB.

For example, assume a function is configured to use 2,560 MB (2.5 GB) and runs for a total of 37 minutes in a given month:

  • Its usage in GB-Hour units is (37/60) x 2.5 = 1.54 GB-Hour units.
  • Each GB-Hour unit consumes 10 credits, so usage of this function consumes 15.4 credits in that month.

View team-level credit usage

Section titled “View team-level credit usage”

To check the aggregated credit consumption for functions:

  1. Go to Usage & billing General.
  2. On that page, scroll down to the Credit usage breakdown card and expand the Compute entry to view the exact credit consumption for functions in GB-Hour units.

For a view of usage over time, aggregated across all projects in your team, go to Usage & billing Account usage insights Compute. This view lets you quickly pinpoint trends and spikes over time.

View project-level observability

Section titled “View project-level observability”

For detailed visibility into function invocations in a specific project, down to individual requests, go to Logs & Metrics Observability.

Observability provides built-in quick actions to help you easily determine which functions are invoked the most, which are the slowest to run, and which client types make the most requests which invoke functions.

Legacy plans

Section titled “Legacy plans”

With a Legacy plan:

  • Functions are billed by request count, regardless of runtime. Limits per plan are available here.
  • Memory/vCPU allocation cannot be increased.
  • Background Functions are not available for Legacy plans, except for Enterprise.
  • Observability is not available, except for Enterprise. Use Function Metrics for a per-function view.

For paid plans, pricing scales with usage. When usage reaches a level limit, the site automatically upgrades to the next level or package. Free tier accounts are also metered based on usage and have a fixed limit.

View usage

Section titled “View usage”

At the team level, you can find function usage under Billing Account usage insights. Learn more about usage and insights for legacy-based plans.

At the project level:

  1. For an aggregated count of requests in the current billing period, go to Project configuration Functions Overview Usage.
  2. For more detailed data per function, use Function Metrics.

More usage and billing resources

Section titled “More usage and billing resources”