Skip to content

How credits work

Netlify’s Credit-based pricing plans are optimized to simplify metered & usage-based billing and work smoothly with AI development workflows. By using credits to measure and bill for usage, Netlify users have fewer metrics to track and more flexibility on how to optimize their spending.

If you’d like a video summary of how credits work, check out this video.

Each Credit-based plan includes a monthly credit allotment that a web project will use for that month’s billing cycle. Some features are also only available on certain plans or have different limits across the Credit-based pricing plans.

FreePersonalPro
300 credits/month1,000 credits/month5,000 credits/month
Hard limitOption to purchase more creditsOption to purchase more credits

Once your monthly credit allotment is used up for all web projects on your team, all of your web projects (sites/apps) are paused and visitors to your web projects will find a Site not available page at each of your web project’s URLs.

Control your spend and keep your web projects active by enabling auto recharge. Auto recharge automatically reloads your credit balance when it runs out with small increments of credits only when your projects need it.

Auto recharge can only be enabled or disabled by a Team Owner for all web projects on a team and is turned off by default for all projects. If you are on a Pro plan, you can also add additional Team Owners to your team.

If you have a Personal or Pro plan, you can enable auto recharge to ensure you always have enough credits to keep your projects active and receiving web requests and form submissions.

If you have a Personal or Pro plan and you’ve enabled auto recharge, the credit card you have on your account will be charged at these rates when your credit balance runs out:

FreePersonalPro
N/A200 credits for $51000 credits for $20

Only Team Owners can enable or disable auto recharge for all web projects on a team. You cannot enable auto recharge for only a specific project on a team.

For guided steps on enabling auto recharge, check out Configure auto-recharge.

Here is how credit usage is calculated by Netlify’s metered billing at a high-level. For more detailed and technical explanations, check out the sections below.

FeatureCredit usageQuick high-level description
Production deploys15 credits eachDeploying your project to production, build minutes no longer calculated
Deploy Previews or branch deploys0 creditsFree deployments for previewing, experimenting, and creating versions of your site/app
Compute5 credits per GB-hourThe “processing power” your site/app needs to run things like serverless functions, scheduled functions, and background functions
Netlify Forms submissions1 credit eachNetlify’s highly customizable forms service with spam protection support available
Bandwidth10 credits per GBData sent out to the internet, such as assets hosted on Netlify or files downloaded from your site/app
Web requests3 credits per 10,000 requestsWeb traffic requests to your site or app, includes page views, API calls, redirects, requests to serverless functions, asset requests

Explore pricing estimates for various combinations of Netlify’s features and services with our Pricing estimation calculator.

Production deploys are a type of deploy that is optimized to work as the finalized version of your web project that shows up at your primary domain and is live on the web. Your primary domain can be a custom domain, such as mycompany.com, or your Netlify default URL, such as MY-PROJECT-NAME.netlify.app.

Netlify supports three types of deploys:

  • Production deploys for finalized and production-ready released versions of your web project
  • Deploy Previews for reviewing and experimenting with changes before they are released
  • Branch deploys for reviewing and experimenting with changes from specific branches or for maintaining different versions of your project

Deploy Previews and branch deploys are optimized to work as preview environments for reviewing and experimenting.

With Credit-based pricing plans, each successful production deploy consumes 15 credits during that month’s billing cycle and you have free deployments for previewing, experimenting, and creating versions of your site/app.

Failed deploys and rolling back a production deploy to a previous production deploy does not consume credits.

Learn more about Netlify’s deploy types.

Compute is the amount of resources used by your functions and represents the “processing power” your site/app needs. This is measured in GB-hours, which at a high-level represents the amount of data transfer in gigabytes needed in an hour.

Compute uses 5 credits per GB-hour. A GB-hour represents a combination of memory allocation and execution time, creating a more transparent way to understand and manage your resource usage.

This means we multiply the amount of time your functions run by the memory they use during the billing cycle. We use this metric on our credit plans, instead of the number of function invocations, because we intend to only charge for the compute time you use.

Features that use compute include:

  • Serverless Functions
  • Scheduled Functions - Functions triggered on a schedule
  • Background Functions - Long-running background tasks

Note that Edge functions don’t contribute to the compute usage metric. Edge functions are measured through web requests.

Netlify’s web forms service consumes 1 credit per form submission. When Netlify auto-detects spam in a form submission, then a credit is not consumed.

We recommend taking measures to help prevent abuse of your project. For example, you can reduce form submission spam by adding a reCAPTCHA 2 challenge and honeypot field.

Bandwidth is the amount of data traffic your site or app sends out to the internet.

Bandwidth uses 10 credits per GB.

Features that use bandwidth include:

  • Assets & web content served - All static assets hosted on Netlify, HTML, CSS, JavaScript files served to visitors
  • Image serving - Images served through Netlify’s CDN
  • File downloads - Any files downloaded from your site/web project
  • API responses - Data served through serverless functions
  • Large Media (Deprecated) - Git LFS files served through Netlify Large Media

Web requests are web traffic requests to your site/app, including requests to your site’s main (production) URL, as well as to any active branch deploys and Deploy Previews.

A web request is counted whenever a user or system accesses content hosted on your project. This includes requests for HTML pages, images, JavaScript, CSS files, and other static assets. Additionally, any invocation of Netlify Functions also counts as a web request.

Web requests use 3 credits per 10 thousand (10,000) requests.

Features that use web requests include:

  • Page views - Each visitor request to your site/app pages
  • API calls - Requests to your serverless functions
  • Asset requests hosted by Netlify - Requests for CSS, JavaScript, images, and other static files hosted by Netlify
  • Redirects
  • Edge functions

For help monitoring your web project’s credit usage, check out Monitor credit usage.

Use our Pricing calculator to calculate common usage patterns.

Get more of your questions answered, such as “What happens when credits are used up?” in our Billing FAQ for Credit-based plans.