Make.com Cost Calculator 2026: Estimate Credits, Plan & Monthly Cost
Your Make.com cost depends mainly on the credits your scenarios use, not on how many you own, although Free caps you at two active scenarios. Estimate monthly credits as trigger credits (or polling checks) + (runs × other operations) + (runs × bundles × actions per bundle) + (Make Code seconds × 2) + AI credits, add about 10% for retries, then pick the credit level and plan that fit.
At the 10,000-credit level, Core is $10.59/month on monthly billing ($9 billed annually), Pro is $18.82 ($16), and Teams is $34.12 ($29). Free includes 1,000 credits. This calculator does the math for up to three scenarios and shows the plan and price you need.
Make.com Cost Calculator
Pick a preset or enter your own workflow. Include up to three scenarios, choose whether each one uses an instant (webhook) trigger or scheduled polling, and the calculator returns credits, the credit level you need, the cheapest plan that fits, and what you would pay.
1. Your scenarios
Scenario 1
Scenario 2 (optional)
Scenario 3 (optional)
2. Plan needs and allowance
3. Your estimate
Estimated monthly credits5,500
Annual plans are paid up front. On annual billing, Core still allocates credits monthly, while Pro and Teams receive an annual credit package you can spend flexibly across the year. The monthly equivalent is for price comparison only.
| Plan | Monthly | Annual (per mo) | Has your features |
|---|
Simple workflow estimate, not a blueprint-level calculation: one bundle multiplier cannot model every fan-out, branch or multi-stage iterator, so check real usage in Make’s execution history. Polling uses a 30-day month. AI usage is based on the credits you enter and covers Make credits only, not separate token charges from an external AI provider. Always confirm the price on Make’s live pricing page.
How the Make.com Cost Calculator Works
Make bills in credits, and most standard operations use one credit each. The calculator models each scenario from the way Make actually meters work, then sums them:
The formula
Credits per scenario = trigger credits + (runs × other operations per run) + (runs × bundles × actions per bundle) + (runs × code seconds × 2) + (runs × AI credits). Then add your retry allowance.
| Input | What to enter | How it is counted |
|---|---|---|
| Trigger type | Instant (webhook) or scheduled polling | Instant: one credit per run. Polling: one credit per check, so 43,200 ÷ interval checks a month |
| Runs with data / month | Executions that actually process data | For polling, capped at the number of checks |
| Other operations per run | Once-per-run steps after the trigger: searches, aggregators, the iterator itself | Runs × this number |
| Bundles per run | Average items an iterator or search hands downstream | Multiplies the per-bundle actions |
| Actions per bundle | Credit-consuming modules that run once for every bundle | Runs × bundles × this number |
| Make Code seconds | Average execution time per run | 2 credits per second |
| AI credits | Credits your AI modules use per run | Dynamic, so you enter the figure from your execution history |
Routers and error-handler modules use no credits, so leave them out. The calculator then finds the smallest credit level that covers your total, picks the cheapest plan that has the features you ticked, and prices it on monthly and annual billing.
Make.com Credit Rules Used in This Calculator
| What happens in a scenario | Credit treatment |
|---|---|
| Read data from an app or webhook | 1 credit |
| Search, create, update or delete data in an app | 1 credit per operation for standard non-AI modules |
| Transform data with built-in tools, aggregate, iterate | Counted as credits |
| Trigger check | A trigger runs once per check, however many bundles it returns, so 1 operation per check; the steps after it run once per bundle |
| Router | No credits |
| Error handler modules (Rollback, Break, Resume, Commit, Ignore) | No credits |
| Make Code app (paid plans only) | 2 credits per second of execution time |
| Make’s AI Provider | Dynamic, based on tokens and operations |
| Your own AI provider connection | Operations-based credits; you pay your AI provider for tokens |
Credits expire at the end of the term. Extra credits are valid for your current billing cycle: until the end of the month on a monthly subscription, until the end of the billing year on annual Pro and Teams, and until each monthly reset on annual Core. Manual purchases are in units of 1,000 credits, auto-purchases are in units of 10,000 (capped at the credits in your subscription per cycle), and both carry a 25% premium over your plan’s per-credit rate. Make notifies you at 75% and 90% of your credits, and scenarios stop when you run out until credits are added.
Make.com Plan Prices Used
Free includes 1,000 credits a month. Core, Pro and Teams are priced by credit level, and Core stops at 300,000 credits. These are the figures the calculator uses, in USD, shown for monthly billing and for annual billing as a monthly equivalent.
| Credits / month | Core monthly | Core annual | Pro monthly | Pro annual | Teams monthly | Teams annual |
|---|---|---|---|---|---|---|
| 10,000 | $10.59 | $9.00 | $18.82 | $16.00 | $34.12 | $29.00 |
| 20,000 | $18.82 | $16.00 | $34.12 | $29.00 | $62.35 | $53.00 |
| 40,000 | $34.12 | $29.00 | $62.35 | $53.00 | $116.47 | $99.00 |
| 80,000 | $64.71 | $55.00 | $107.06 | $91.00 | $203.41 | $172.90 |
| 150,000 | $116.47 | $99.00 | $180.53 | $153.45 | $343.01 | $291.56 |
| 300,000 | $214.31 | $182.16 | $315.93 | $268.54 | $600.26 | $510.22 |
Above 300,000 credits only Pro and Teams are offered. The calculator contains prices for selected credit tiers and directs you to Make’s live pricing for the others, such as 750,000 or 1.5 million credits, rather than guessing.
Pricing note
Make’s displayed prices can differ across pricing-page versions and billing selections. Some views show $12, $21 and $38 at 10,000 credits, while price ladders recorded from the pricing page in September and October 2026 show $9, $16 and $29 annual and $10.59, $18.82 and $34.12 monthly. This calculator uses the recorded USD ladder for the stated credit tiers and keeps monthly billing separate from the monthly equivalent of annual prepayment. Before purchasing, select the same credit tier and billing frequency on Make’s live pricing page and verify the amount shown for your account. The credit estimate does not depend on price, so it stays reliable either way.
Worked Examples
Each example matches a preset in the calculator, so you can load it and change the numbers.
Example 1: lead capture with a webhook
1,000 runs a month. Each run uses 1 trigger credit, 2 other operations and 1 bundle with 2 actions, so 5 credits per run: 5,000 credits. Add 10% for retries and you need 5,500 credits. That fits the 10,000-credit level on Core at $10.59/month ($9 annual), using 55% of the level.
Example 2: CRM sync with 15-minute polling
A 15-minute schedule checks 2,880 times a month, and each check uses a credit. 1,500 of those checks find data and process 3 bundles with 2 actions each, plus 1 other operation: 2,880 + 1,500 + 9,000 = 13,380 credits. Add 10% and you need 14,718 credits, which is the 20,000-credit level on Core at $18.82/month ($16 annual). About 1,380 credits go to checks that found nothing. Switching to an instant trigger would cut that waste.
Example 3: an agency running three scenarios
A 2,000-run webhook lead flow (12,000 credits), a 5-minute polling sync (8,640 checks plus 3,000 runs with 2 bundles each, 23,640 credits) and a 500-run AI enrichment flow with 10 bundles and 5 AI credits a run (19,000 credits) total 54,640. With 10% allowance that is 60,104 credits, so the 80,000-credit level. On Core that is $64.71/month ($55 annual). If the team also needs roles and shared templates, Teams at the same level is $203.41/month ($172.90 annual). The 5-minute polling scenario alone burns about 5,640 credits on empty checks.
What Increases Your Make.com Bill
| 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 |
| Frequent polling | A check every minute is 43,200 credits a month before any work |
| Routers and error handlers | No credits |
| AI and token processing | Variable, dynamic credit usage |
| Long Make Code execution | 2 credits per second |
How to Lower Your Make.com Cost
- Use instant triggers instead of polling wherever the app supports webhooks. It removes the empty-check credits.
- Lengthen polling intervals when near-real-time is not needed. Going from 5 to 15 minutes cuts checks by two thirds.
- Filter before expensive modules so records that will be discarded never reach a credit-consuming step.
- Aggregate and batch writes. One bulk write for a group of records costs far less than one write per record.
- Reduce searches. Each search is an operation, so look data up once and reuse it.
- Keep bundles small. Trim the data an iterator passes on, and process only what you need.
- Watch retries. Failed runs that retry use credits again, so fix the cause instead of absorbing it.
- Check real usage in your execution history for the first weeks, then compare it to this estimate.
Make.com vs Zapier Cost
Make counts credits for module work, while Zapier counts tasks for successful action steps, and Zapier’s polling triggers do not use tasks. The meters differ, so compare them on a real workflow. Zapier Professional starts at $29.99/month on monthly billing ($19.99 annual) for 750 tasks.
Run your workflow through our Zapier vs Make pricing calculator for a side-by-side, or read the full Zapier vs Make.com comparison.
Ready to check your Make.com plan?
Estimate your credits, start on the smallest plan that fits, and move up only when credits or features require it.
Make.com Cost FAQ
How much does Make.com cost per month?
Free is $0 with 1,000 credits. At 10,000 credits, Core is $10.59/month on monthly billing ($9 annual), Pro is $18.82 ($16) and Teams is $34.12 ($29). Prices rise with the credit level you choose, so estimate your credits first.
How do I calculate how many Make.com credits I need?
Add the credits each scenario uses: trigger credits, once-per-run operations, and per-bundle actions multiplied by runs and bundles. Add about 10% for retries. The calculator above does this for up to three scenarios.
Does polling use Make.com credits?
Yes. A scheduled trigger uses an operation each time it checks, even when it finds nothing. A check every 15 minutes is 2,880 credits a month. An instant webhook trigger uses a credit only when the scenario runs.
Do routers and filters cost credits?
Routers and error-handler modules (Rollback, Break, Resume, Commit, Ignore) use no credits. Most other module actions use one credit each.
How much do extra Make.com credits cost?
Extra credits carry a 25% premium over your plan’s per-credit rate. You can buy them manually in units of 1,000 credits or turn on auto-purchase in units of 10,000. They are valid for the current billing cycle: the month on monthly plans, the year on annual Pro and Teams, and each monthly reset on annual Core. Make recommends moving up a level if you need them regularly, since higher tiers have lower per-credit costs.
Is annual Make.com billing cheaper?
Yes. Make advertises savings of 15% or more for annual billing, which is prepaid for the year. At 10,000 credits that is $9 versus $10.59 on Core, $16 versus $18.82 on Pro and $29 versus $34.12 on Teams.
Which Make.com plan do I need?
Free suits testing within 1,000 credits, 2 active scenarios and 15-minute scheduling, and it does not include the Make Code app. Core adds unlimited scenarios and one-minute scheduling. Pro adds priority execution, custom variables and log search. Teams adds roles and shared templates. Core is not offered above 300,000 credits.
How accurate is this Make.com cost calculator?
It is accurate for standard fixed-credit workflows when your inputs are. AI modules and Make Code can use more credits, so enter their usage if you rely on them, and confirm your real consumption in Make’s execution history. Prices should always be checked on Make’s live pricing page.
Related CreatorOpsMatrix guides
Sources and Methodology
Make pricing, credit behavior and plan limits can change. These are the primary references to check before buying.
Plans, credit levels, billing options, credit FAQ 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.
Professional pricing and the task model used in the comparison.
How we checked Make.com pricing
Credit rules and plan limits checked October 10, 2026 against Make’s pricing page and Help Center. Dollar prices come from price ladders recorded from the pricing page by independent trackers in September and October 2026, not from the Help Center. Prices shown are USD for the stated credit level and billing cadence. Make’s displayed prices varied between sources during our check, so verify the live pricing page before purchasing.