A Hugging Face inference pricing calculator estimates a monthly bill in one of three ways. Inference Providers bill per token at the provider rate with no markup. HF Inference bills compute seconds. Inference Endpoints bill an hourly instance rate. An AWS NVIDIA T4 endpoint at $0.50 an hour costs $365 for 730 hours.
Estimated monthly cost after credits
Calculations run in your browser. Inputs are not sent to our servers; anything you Save stays in this browser only.
Saved results (0)
How to Use the Hugging Face Inference API Pricing Calculator
- Pick the billing model: Inference Providers per token, HF Inference per compute second, or a dedicated Inference Endpoint per hour.
- Enter the prices and your usage. Token prices come from the provider row for your model. Endpoint rates fill in when you pick an instance, and every price stays editable.
- Choose your account type so the monthly credits are taken off, then read the cost and the endpoint comparison.
What each result tells you:
| Result | What it means |
|---|---|
| Estimated monthly cost after credits | Usage cost minus the monthly credits, never below zero. |
| Usage cost before credits | What the usage costs at the prices entered. |
| Credits applied | The part of your monthly credits used up by this usage. |
| Cost per request | Usage cost divided by requests per month. |
| Usage per month | Total tokens, compute hours or instance hours behind the bill. |
| Dedicated endpoint comparison | The request volume at which pay per use costs the same as the chosen instance left on for 730 hours. |
The subscription fee for a PRO, Team or Enterprise plan is a separate charge. It is not part of the result.
What Is Hugging Face Inference API Pricing?
Hugging Face inference pricing is the cost of running a model through Hugging Face, and today it comes from two products with different billing. Inference Providers is the serverless, pay-as-you-go service. Inference Endpoints is the dedicated service billed by the hour.
The name in this page's title is the older one. Hugging Face's billing guide says the HF Inference provider used to be called Inference API (serverless) before Inference Providers existed. HF Inference is now one provider among many inside Inference Providers.
| Product | How it is billed | Figures on 2026-10-02 |
|---|---|---|
| Inference Providers, partner providers | The provider's own rate, passed through with no markup from Hugging Face | Set per model and provider. See the supported models table. |
| Inference Providers, HF Inference | Compute time x the price of the hardware | Guide example: 10 seconds on a GPU at $0.00012 a second is $0.0012. |
| Inference Endpoints (dedicated) | Hourly instance rate, counted by the minute | From $0.033 an hour for the smallest AWS CPU instance. |
| Monthly credits | Applied before any pay-as-you-go charge | Free users $0.10, PRO users $2.00, Team or Enterprise $2.00 per seat. |
Hugging Face states that the free-user credit is subject to change. Free-user credits can be spent on Inference Providers. Credits that come with a PRO, Team or Enterprise plan are general compute credits, which also cover Inference Endpoints. The PRO plan is listed at $9 a month.
Hugging Face says that, as of July 2025, HF Inference focuses mostly on CPU tasks such as embeddings, text ranking and text classification. Large language models are mostly served by partner providers at per-token rates.
How Does the Hugging Face Pricing Calculator Work?
The calculator applies one of three formulas, then subtracts your monthly credits.
Per token = (input tokens x input price + output tokens x output price) / 1,000,000. Compute time = seconds per request x price per second x requests. Endpoint = hourly rate x ((hours x minimum replicas) + (scale-up hours x additional replicas)).- Per token: tokens per request x requests per month gives monthly tokens. Each total is priced per 1 million tokens.
- Compute time: seconds per request x the hardware price per second x requests per month.
- Endpoint: the hourly rate x the instance hours billed. This is the formula in the Hugging Face endpoint pricing guide.
- Monthly cost = usage cost - credits. The result stops at zero.
- Break-even requests = the instance rate x 730 hours / your cost per request.
Token counts are your own figures. A fast way to turn text length into tokens is the AI token calculator.
Hugging Face Pricing Example
A free-tier user sends 100,000 requests a month through Inference Providers. Each request has 1,000 input tokens and 300 output tokens. The provider row lists $0.20 input and $2.50 output per 1 million tokens. That row is one example read from the supported models table on 2026-10-02, not a typical rate.
| Step | Calculation | Result |
|---|---|---|
| Input tokens | 1,000 x 100,000 | 100,000,000 |
| Output tokens | 300 x 100,000 | 30,000,000 |
| Input cost | 100 x $0.20 | $20.00 |
| Output cost | 30 x $2.50 | $75.00 |
| Usage cost | $20.00 + $75.00 | $95.00 |
| After the $0.10 credit | $95.00 - $0.10 | $94.90 |
| Cost per request | $95.00 / 100,000 | $0.00095 |
Meaning: the bill is $94.90 for the month. A PRO user with $2.00 of credits would pay $93.00 plus the plan fee. A dedicated NVIDIA T4 endpoint left on all month costs $365.00, so pay per use stays cheaper until about 384,211 requests a month.
Factors That Change Your Hugging Face Bill
The Provider You Route To
The same model is priced differently by each provider. Hugging Face passes the provider rate through with no markup, so the row you pick in the supported models table sets your price.
Output Tokens
Output usually costs more than input. In the example, output is 30 million of 130 million tokens but $75.00 of the $95.00 bill.
Routing and Keys
Requests routed by Hugging Face are billed on your Hugging Face account, and monthly credits apply. With a custom provider key, the provider bills you directly and the credits do not apply.
Running Hours
A dedicated endpoint is billed for the time it runs, not for requests. An NVIDIA T4 instance on for 8 hours across 22 days costs $88.00 instead of $365.00.
Replicas and Autoscaling
Each replica is billed at the full rate. The pricing guide's example scales a T4 endpoint from 1 to 3 replicas for 15 minutes every hour. That adds 182.5 hours x 2 replicas and brings the month to $547.50.
Instance Size and Cloud
Rates differ by hardware and by cloud. One NVIDIA A100 is $2.50 an hour on AWS and $3.60 an hour on GCP in the official table.
Inference Providers vs Inference Endpoints: Cost Comparison
Inference Providers cost scales with requests, and an Inference Endpoint costs the same whether it serves one request or a million. The right choice depends on steady volume. The table shows official hourly rates and the cost of one replica left on for 730 hours.
| Instance | Hourly rate | 730 hours |
|---|---|---|
| AWS CPU Intel Sapphire Rapids x1 (1 vCPU, 2 GB) | $0.033 | $24.09 |
| AWS CPU Intel Sapphire Rapids x2 (2 vCPU, 4 GB) | $0.067 | $48.91 |
| AWS CPU Intel Sapphire Rapids x4 (4 vCPU, 8 GB) | $0.134 | $97.82 |
| AWS CPU Intel Sapphire Rapids x8 (8 vCPU, 16 GB) | $0.268 | $195.64 |
| AWS GPU NVIDIA T4 x1 (14 GB) | $0.50 | $365.00 |
| AWS GPU NVIDIA L4 x1 (24 GB) | $0.80 | $584.00 |
| AWS GPU NVIDIA A10G x1 (24 GB) | $1.00 | $730.00 |
| AWS GPU NVIDIA L40S x1 (48 GB) | $1.80 | $1,314.00 |
| AWS GPU NVIDIA A100 x1 (80 GB) | $2.50 | $1,825.00 |
| AWS GPU NVIDIA H200 x1 (141 GB) | $5.00 | $3,650.00 |
| GCP GPU NVIDIA T4 x1 (16 GB) | $0.50 | $365.00 |
| GCP GPU NVIDIA L4 x1 (24 GB) | $0.70 | $511.00 |
| GCP GPU NVIDIA A100 x1 (80 GB) | $3.60 | $2,628.00 |
| GCP GPU NVIDIA H100 x1 (80 GB) | $10.00 | $7,300.00 |
The break-even point is the endpoint's monthly cost divided by your pay-per-use cost per request. At $0.00095 a request, the $365.00 T4 endpoint matches pay per use at about 384,211 requests a month. The same sum for any fixed cost is covered by the break-even calculator.
What Does HF Inference Cost per Request?
HF Inference bills compute time. The billing guide's example is a request that runs for 10 seconds on a GPU machine costing $0.00012 a second, which is billed $0.0012. Fifty thousand such requests cost $60.00.
What Should You Budget?
Budget from measured usage. Run a short test, read the token counts or request times, and enter the averages. One instance has a limit on how many requests it can serve, so a busy service needs more replicas than the break-even sum suggests.
When to Use a Hugging Face Cost Estimate
Choosing Between Serverless and Dedicated
A team with steady traffic compares its pay-per-use bill with an always-on endpoint. The break-even result shows which side of the line it is on.
Comparing Providers for One Model
A developer enters two provider rows in turn. The difference in monthly cost shows what a faster provider costs. Response speed matters as well as price, and the token generation speed simulator shows how long a reply takes at a given speed.
Sizing a Side Project
A hobby user checks whether the monthly credits cover the project. A result of zero means no pay-as-you-go charge at that volume.
Planning Working-Hours Endpoints
A team that needs a private model only during the working day enters the real running hours. The saving against an always-on endpoint is the difference.
Common Hugging Face Pricing Mistakes
1. Expecting One Price per Model
There is no single Hugging Face price for a model. Each provider sets its own rate, and the rates change.
2. Treating the Free Credit as a Free Tier for Production
The free-user credit is $0.10 a month and is subject to change. It suits testing, not a live service.
3. Leaving an Endpoint Running
A dedicated endpoint bills for every hour it runs, with or without traffic. An idle T4 instance still costs $365.00 a month.
4. Forgetting Extra Replicas
Autoscaling adds replicas at the full hourly rate. Count the scale-up hours, not only the minimum replica.
5. Using a Custom Key and Expecting Credits
Credits apply only to requests billed by Hugging Face. A custom provider key moves the bill to the provider.
6. Reusing Old Price Tables
Hugging Face has renamed and restructured these products. Older per-model price lists for the serverless Inference API do not describe billing today.
Accuracy and Limitations
The arithmetic is exact for the prices and usage you enter. The estimate depends on those inputs, and provider rates change without notice.
What it calculates accurately
- Per-token cost at the provider rate you enter
- Compute-time cost for HF Inference requests
- Endpoint cost from the official hourly formula
- Credits taken off, and the break-even request volume
What it does not account for
- Price changes after 2026-10-02
- Per-image, per-video or per-minute provider pricing
- The PRO, Team or Enterprise subscription fee
- How many requests one instance can serve
- Per-minute rounding of endpoint time, storage and taxes
- Credits already spent on other Hugging Face services
How We Calculate the Hugging Face Cost
Frequently Asked Questions About Hugging Face Inference Pricing
Is the Hugging Face Inference API free?
Only up to the monthly credits. Free users get $0.10 of Inference Providers credits a month, subject to change. After that, usage is pay-as-you-go and needs purchased credits.
What is the Inference API called now?
The serverless service is now Inference Providers. Hugging Face says its own HF Inference provider used to be called Inference API (serverless). Dedicated deployments are a separate product named Inference Endpoints.
Does Hugging Face add a markup to provider prices?
No. Hugging Face states that it charges the same rates as the provider and passes the costs through with no extra fees.
How much does a Hugging Face Inference Endpoint cost per month?
It is the hourly rate x the hours it runs x the replicas. One AWS NVIDIA T4 instance at $0.50 an hour costs $365.00 for 730 hours, and the smallest listed AWS CPU instance at $0.033 an hour costs $24.09.
How much are the credits for a PRO account?
A PRO account includes $2.00 of compute credits each month, and the plan is listed at $9 a month. The credits can be spent on Inference Providers, Inference Endpoints and other Hugging Face compute services.
When is a dedicated endpoint cheaper than pay per use?
A dedicated endpoint is cheaper once your monthly pay-per-use bill is higher than the endpoint cost. At $0.00095 a request, that point is about 384,211 requests a month for a $365.00 endpoint.
Are endpoints billed by the hour or by the minute?
Prices are shown by the hour, and Hugging Face states that the actual cost is calculated by the minute. This tool works in hours, so enter part hours as decimals.
Do credits work with my own provider key?
No. With a custom provider key the provider bills you directly, and Hugging Face monthly credits do not apply to those requests.
Where do I find the token price for my model?
Hugging Face publishes a supported models table for Inference Providers. It lists the input and output price per 1 million tokens for each model and provider.
Who is this calculator not suited to?
It does not suit image, video or speech workloads priced per image or per minute by a provider. It also does not size the hardware a model needs.
Is my information saved?
No. The calculation runs in your browser and nothing is sent to our servers. Anything you Save stays in this browser only.
Sources
- Inference Providers: pricing and billing (Hugging Face documentation, checked 2026-10-02).
- Inference Endpoints: pricing (Hugging Face documentation, hourly instance rates and cost formula).
- Hugging Face pricing (Hugging Face, plans and hardware prices).
- Inference Providers: supported models (Hugging Face, per-model and per-provider token prices).
Related Calculators
Planning more AI costs?
Explore all AI calculatorsThis calculator gives educational cost estimates only. It is not a quote, an invoice or financial advice. Prices were read from Hugging Face's official pricing pages on 2026-10-02 and can change at any time. Check the official pages and your own billing page before you commit to a budget. MultiCalculators is not affiliated with or endorsed by Hugging Face. Hugging Face is a trademark of Hugging Face, Inc. Spotted an error? Let us know.
Author
Shakeel Muzaffar is the Founder and Editor-in-Chief of MultiCalculators.com, bringing over 15 years of experience in digital publishing, product strategy, and online tool development. He leads the platform's editorial vision, ensuring every calculator meets strict standards for accuracy, usability, and real-world value. Shakeel personally oversees content quality, formula verification workflows, and the platform's commitment to publishing tools that are genuinely useful for students, professionals, and everyday users worldwide.




