Make.com Pricing 2026: Plans, Credits, Costs & Calculator
Make.com has a Free plan with up to 1,000 credits/month. At the 10,000-credit level, Core is $16/month on monthly billing ($12/month billed annually), Pro is $28 ($21 annual), and Teams is $51 ($38 annual). Enterprise pricing is custom.
But the plan price is only half the calculation. Make prices usage through credits, and your real cost depends on how many credits your scenarios actually consume.
How your Make.com bill is built
The plan price is the last step. Use the credit calculator below to work out the earlier ones.
Make.com Pricing Plans at a Glance
These are the current prices at Make’s 10,000-credit comparison point. Make’s public pricing page uses a credit selector, so a higher credit requirement produces a higher subscription price.
| Plan | Credits | Monthly billing | Annual billing (monthly equivalent) | Best for |
|---|---|---|---|---|
| Free | Up to 1,000/mo | $0 | $0 | Testing and light automation |
| Core | 10,000+ | $16* | $12* | Individual builders |
| Pro | 10,000+ | $28* | $21* | Advanced automation |
| Teams | 10,000+ | $51* | $38* | Collaborative teams |
| Enterprise | Custom | Custom | Custom | Governance and large deployments |
*Read this before comparing prices
Paid-plan figures are the 10,000-credit reference point, not universal prices. Make’s pricing page defaults to the annual view, so the lower number you see first is the annual-billing monthly equivalent, which is paid in advance for the year. Month-to-month billing costs more.
What Makes Make.com Pricing Different?
Make does not price you by how many automations you have. It prices usage through credits, and the number of credits you consume depends on what your scenarios actually execute.
That is the single most important thing to understand before choosing a plan. A scenario that runs 1,000 times can consume 1,000 credits, 5,000 credits or more than 10,000, depending on what happens inside those runs. Workflow runs and credits are not the same number.
The pricing question to ask
Not “how many automations do I have?” but “how much module work will my scenarios perform each month?”
How Make.com Credits Work
Credits are Make’s billing unit. They replaced operations as the term for billing, while operations still describe the module activity itself. Most standard non-AI operations use one credit, but some features use different or dynamic credit rates, so do not treat one visible module as exactly one credit in every case.
Example 1: a simple workflow
3 standard operations × 1,000 runs
Three standard operations across 1,000 runs is roughly 3,000 credits.
Example 2: a longer workflow
Several operations per execution × monthly runs
Credit usage grows with the actual work performed. Routers and error-handler modules do not use credits, so routing logic is cheaper than it looks on the canvas.
Example 3: bundles and loops
If one execution processes 20 records, a downstream action can run once for each bundle. What looks like one workflow run can become many credit-consuming operations. This is the most common reason a Make bill is higher than a first estimate.
The cost rule
For a simple fixed-credit workflow, credit usage can be approximated from scenario runs, credit-consuming operations and the number of bundles those operations process. It does not depend on how many scenarios you own.
Make.com Credit Calculator: How Many Credits Will Your Workflow Use?
Use this calculator to approximate monthly credit usage for a standard fixed-credit workflow. It separates operations that happen once per run (a trigger, a search, an aggregator) from operations that repeat for every bundle, because that split is where most estimates go wrong.
1. Your workflow
2. Your estimate
Estimated monthly creditsYour estimated usage is within the 10,000-credit level, but with little headroom. A growing workflow may need the next level.
Formula: (runs × per-run operations) + (runs × bundles × per-bundle actions), then plus your allowance. Operations that run once per run include the trigger, searches and aggregators. Routers and error-handler modules use no credits, so leave them out. Estimate only: AI and other dynamic-credit features can use credits based on tokens, file size, pages, processing time or other usage factors. Plan suggestions assume Free limits (2 active scenarios, 15-minute scheduling) are not enough for production use.
What Increases Your Make.com Bill?
After you know the plan prices, these are the behaviors that actually move your credit count.
| Workflow behavior | Effect on credits |
|---|---|
| More scenario runs | Increases credits in proportion |
| More credit-consuming modules | Increases credits on every run |
| More bundles | Multiplies the actions that run per bundle |
| Iterators | Can increase usage sharply, since every item flows downstream |
| Repeated searches | Each search operation uses credits |
| Scheduled polling with no new data | Can consume credits on empty checks |
| Routers | No credits |
| Error-handler modules | No credits |
| AI and token processing | Variable, dynamic credit usage |
| Long Make Code execution | 2 credits per second of execution time |
Make.com Free Plan
The Free plan has no time limit, but it is built for learning and light use.
- 1,000 credits per month
- 2 active scenarios
- 15-minute minimum scheduling interval
- 5-minute maximum scenario execution time
- 5 MB maximum file size
- 7-day execution log storage
Who should choose Free?
Choose Free when you are learning Make, testing a workflow, or running very light automation where 1,000 monthly credits and the 15-minute scheduling limit are enough. For production workflows, the 2-scenario limit and 15-minute scheduling interval can become the reason to move to Core even before you exhaust the 1,000-credit allowance.
Make.com Core: Who Is It Actually For?
Core is the logical starting point once you have moved beyond experimentation. Over Free, it adds unlimited active scenarios, one-minute scheduling and access to the Make API.
| Core makes sense when | Core is unnecessary when |
|---|---|
| You need more than 2 active scenarios | You are still testing |
| You need 1-minute scheduling | 15-minute scheduling is enough |
| You need Make API access | You do not use the API |
| Your usage fits the credit allocation | You need advanced collaboration features |
Make.com Pro: What Are You Actually Paying More For?
You are not primarily buying more automation. At the same credit level, Pro adds higher-level execution and operational features: priority scenario execution, custom variables and full-text execution-log search.
These matter to you
Execution priority matters, you need searchable execution history, or custom variables solve real workflow complexity.
You are only short on credits
Your workflows already run reliably, you do not need those features, or you are upgrading purely because you need more credits. Credits are bought by volume, not by plan name.
Make.com Teams: When Is It Worth Paying More?
Teams adds teams and team roles plus the ability to create and share scenario templates. It is primarily a collaboration and governance decision, not a volume decision.
Do not upgrade on client count alone
Having more clients does not by itself justify Teams. Upgrade when you need role-based access, team-owned resources or shared templates across several builders.
If you run client work, read our guide to Make.com for marketing agencies for how teams, ownership and billing fit together.
Make.com Enterprise
Enterprise is for organizations that need capabilities such as custom functions, enterprise app integrations, 24/7 support, overage protection and advanced security features.
Enterprise pricing is custom. Request a quote from Make for current commercial terms.
Monthly vs Annual Make.com Pricing
Annual billing is cheaper, but the lower monthly-equivalent price represents a prepaid annual commitment rather than a month-to-month subscription. Make advertises savings of 15% or more for annual billing. At the 10,000-credit level shown here, annual billing is about 25% cheaper than monthly billing for Core, Pro and Teams.
| 10,000 credits | Monthly billing | Annual billing (monthly equivalent) | Annual total |
|---|---|---|---|
| Core | $16 | $12 | $144 |
| Pro | $28 | $21 | $252 |
| Teams | $51 | $38 | $456 |
Annual billing changes credit behavior differently by plan. Core still uses monthly credit allocations even when you pay annually. Pro and Teams use annual credit packages that you can spend flexibly across the year, which suits uneven usage. Credits expire at the end of the term, and extra credits expire with it: after one month on a monthly subscription, or at the end of the year on an annual Pro or Teams subscription. If you are not sure the workflow will still exist in a year, start monthly.
What Happens When You Run Out of Make Credits?
75% and 90%
Make notifies you as usage approaches 75% and again at 90% of your purchased credits.
Scenarios stop
Scenarios stop running until credits are added. Incoming webhooks queue up to your queue limit and process when scenarios resume.
Upgrade or top up
Upgrade your subscription, buy extra credits, or enable automatic extra-credit purchases on eligible plans.
Extra credits currently carry a 25% premium over the credits included in your plan. A 10,000-credit plan does not mean you can safely plan around exactly 10,000: a production workflow that regularly exceeds its allocation becomes more expensive through extra credits, so recurring overage is a signal to move up a credit level rather than keep topping up.
Polling can use credits on empty checks
Scheduled polling can consume credits even when no new data is returned. If an app supports instant webhooks, using a webhook can avoid unnecessary polling activity.
How AI Changes Make.com Credit Costs
Standard workflows mostly use fixed credit rates. AI workflows can be dynamic. Make’s documentation says dynamic credit usage can depend on tokens, file size, page count, processing time and other usage factors.
Standard app modules
Usually one credit per operation, regardless of input or data size. Uploading a file always costs the same credit amount.
Make’s built-in AI provider
Credits are based on tokens and operations, and vary with the model you select and the amount of text processed.
Your own AI connection
Custom AI provider connections work on every paid plan, Core included. You pay Make for operations and your AI provider directly for tokens.
Make Code
The Make Code app uses 2 credits per second of execution time, so long-running code adds up quickly.
A scenario that looks identical to a basic sync can cost far more once an AI step or a long code block is added, so test with realistic payloads before trusting an estimate.
What Does Make.com Actually Cost for a Real Workflow?
Lead qualification workflow
Assume 2,000 runs per month and 5 standard operations per run: 2,000 × 5 = 10,000 credits, assuming each of the five operations executes once per scenario run and produces one bundle. That lands right at the 10,000-credit level before any retries, loops, extra bundles or dynamic AI processing, so a real month could easily run past it.
Do not treat that result as exact billing when bundle behavior is unknown. The same 2,000 runs can cost very different amounts depending on the workflow shape:
| Workflow shape | Approximate credit usage | Why |
|---|---|---|
| Simple 3-module workflow | Low | Few operations per run |
| 6-module linear workflow | Medium | One credit per standard operation |
| Search + multiple bundles | Higher | Downstream actions run per bundle |
| Iterator + downstream actions | Potentially much higher | Every item triggers the actions after it |
| AI or file-processing workflow | Variable | Dynamic credit usage |
Which Make.com Plan Should You Choose?
| Your situation | Recommended starting point |
|---|---|
| Learning or testing workflows | Free |
| Solo production automation | Core |
| Need priority execution, log search or custom variables | Pro |
| Multiple people or reusable team templates | Teams |
| Enterprise governance and security | Enterprise |
The decision rule
Do not choose a plan from client count alone. Choose it from credit consumption + required features + collaboration model.
Make.com vs Zapier Pricing
The two platforms meter different things, so a price-for-price comparison misleads. Make counts credits for module work. Zapier counts tasks for successful action steps, and its polling triggers do not use tasks.
| Pricing question | Make.com | Zapier |
|---|---|---|
| Primary usage meter | Credits for module execution | Tasks for successful action steps |
| Main billing question | How much module work happens? | How many billable actions happen? |
| Entry paid price | Core $16/mo monthly, $12 annual (10k credits) | Professional $29.99/mo monthly, $19.99 annual (750 tasks) |
| Collaboration | Teams and roles on the Teams plan | Team plan features |
| Best way to compare | Model your real workflow | Model your real workflow |
For a full side-by-side, read the Zapier vs Make.com comparison or run your own numbers in the Zapier vs Make pricing calculator.
See Make pricing in real workflows
Ready to pick your Make.com plan?
Estimate your credits, start on the smallest plan that fits your workflow, and move up only when credits or features actually require it.
Make.com Pricing FAQ
How much does Make.com cost in 2026?
At the 10,000-credit level, Core is $16/month on monthly billing ($12 annual), Pro is $28 ($21 annual) and Teams is $51 ($38 annual). Free is $0 with up to 1,000 credits, and Enterprise is custom. Prices rise with the credit allocation you choose.
Is Make.com free?
Yes. The Free plan has no time limit and includes up to 1,000 credits per month, 2 active scenarios and a 15-minute minimum scheduling interval.
How many credits does Make.com include?
Free includes up to 1,000 credits per month. Paid plans start at 10,000 credits per month, and the pricing page lets you select higher allocations.
What is the difference between Make Core, Pro and Teams?
Core adds unlimited active scenarios, one-minute scheduling and API access over Free. Pro adds priority execution, custom variables and full-text execution-log search. Teams adds teams, team roles and scenario-template sharing.
Is Make.com cheaper if I pay annually?
Yes. Make advertises savings of 15% or more, and at the 10,000-credit level shown here annual billing is about 25% cheaper than monthly billing for Core, Pro and Teams. The lower price is a prepaid annual commitment.
What happens if I run out of Make credits?
Your scenarios stop until credits are added. Make warns you at 75% and 90% usage, and you can upgrade, buy extra credits at a 25% premium, or enable automatic purchasing on eligible plans.
How are Make.com credits calculated?
Most standard non-AI operations use one credit, but some features use different or dynamic rates. Credits scale with runs, operations and bundles processed. Router and error-handler modules do not use credits.
Do Make AI features use additional credits?
They can. Make’s built-in AI provider calculates credits from tokens and operations, while a custom AI connection on a paid plan uses credits for operations and you pay your provider for tokens. The Make Code app uses 2 credits per second of execution.
Which Make.com plan should I choose?
Choose from your estimated credit usage, the features you need and how many people collaborate. Free suits testing, Core suits solo production work, Pro adds execution features, and Teams adds collaboration and governance.
Is Make.com cheaper than Zapier?
Often for multi-step, higher-volume workflows, but the two meter different units. Model your real workflow in both before deciding. Our pricing calculator does this for standard workflows.
Official Make.com Sources
Make pricing, credit behavior and plan limits can change. These are the primary references to check before buying.
Current plans, credit selector, monthly and annual billing, and plan limits.
Fixed vs dynamic credit usage and AI credit rules.
How operations are counted for trigger checks, bundles and iterators.
Buying extra credits and automatic purchasing.
How credit allocation differs between monthly and annual billing by plan.
How AI agent features consume credits.
Extra-credit premium and pricing-policy changes.
Current Professional and Team pricing and task model.
How we checked Make.com pricing
Pricing checked October 2026. We compared Make’s public pricing page with its Help Center documentation for credits, extra credits and plan limits. Prices shown are for the stated credit allocation and billing cadence. Make can change pricing, features and credit rules, so verify the live pricing page before purchasing.