Make.com pricing starts at $0 for 1,000 credits a month. At 10,000 credits, Core is $9 a month, Pro is $16 and Teams is $29, billed annually. Billed monthly, the same plans are $10.59, $18.82 and $34.12. Enterprise is custom. Those are the US dollar prices on Make's pricing page, checked on 30 October 2026. The price rises with the credits you choose, and one action is usually one credit, so the rest of this guide lists the tiers and shows how to count.
Every Make plan and credit tier
Each price is per month in US dollars. Annual prices are paid in advance, and Make labels them as saving 15%.
| Credits a month | Core, annual | Core, monthly | Pro, annual | Pro, monthly | Teams, annual | Teams, monthly |
|---|---|---|---|---|---|---|
| 10,000 | $9 | $10.59 | $16 | $18.82 | $29 | $34.12 |
| 20,000 | $16 | Not read | $29 | Not read | $53 | Not read |
| 40,000 | $29 | $34.12 | $53 | $62.35 | $99 | $116.47 |
| 80,000 | $55 | Not read | $91 | Not read | $172.90 | Not read |
| 150,000 | $99 | $116.47 | $153.45 | $180.53 | $291.56 | $343.01 |
| 300,000 | $182.16 | $214.31 | $268.54 | $315.93 | $510.22 | $600.26 |
| 500,000 | Not available | Not available | $410.27 | Not read | $779.50 | Not read |
| 1,000,000 | Not available | Not available | $748.73 | $880.86 | $1,400.67 | $1,647.85 |
| 3,000,000 | Not available | Not available | $1,983.85 | Not read | $3,446.97 | Not read |
The slider has more steps than this table, up to 8 million credits, and Make points you to Enterprise above that. Core is not available above 300,000 credits. "Not read" means we did not record that price on this check, so see Make's page for it.
What each plan adds
- Free has 1,000 credits a month, the visual builder, 3,500+ apps, routers and filters, and a 15-minute minimum interval between runs.
- Core adds unlimited active scenarios, scheduling down to the minute, higher data transfer limits and access to the Make API.
- Pro adds priority scenario execution, custom variables and full-text search of execution logs.
- Teams adds teams and team roles, and shared scenario templates.
- Enterprise adds custom functions, enterprise app integrations, 24/7 enterprise support, access to Make's Value Engineering team, overage protection and advanced security features.
Make also advertises a Start-up Plan: 50% off Business for companies with under 20 employees. Business did not appear as a card on the page we read, so check the offer with Make. Non-profits are asked to contact Make for a discount.
How Make credits work
Credits are Make's billing unit. Make's credit guide says most apps use a fixed one credit per operation, whatever the data size. Reading, searching, creating, updating or deleting data all count, and so do transforming data with built-in tools, aggregating and iterating. A single run can use two credits or thousands.
Two kinds of module cost nothing: routers, and the error handlers Rollback, Break, Resume, Commit and Ignore.
AI costs more than one credit in some setups
If you connect your own account at OpenAI, Anthropic or Google, each operation is one credit and you pay that provider for tokens. If you use Make's AI Provider, credits are based on tokens and vary by model. Make's examples include Claude Haiku 4.5 at 904 input tokens or 181 output tokens per credit. Some AI Content Extractor modules use a fixed 2 or 10 credits. Test an AI scenario on real data before you estimate its monthly credits.
Usage limits that scale with credits
For every 10,000 credits a month you get 5 GB of data transfer, 10 MB of data storage, 10 MB of incomplete execution storage (2 GB maximum) and a webhook queue of 667 (10,000 maximum). A high-data scenario can hit these before it runs out of credits.
What happens when you run out
Scenarios stop until credits are added. Incoming webhooks queue up to your limit, and polling scenarios pick up from their last successful run. You can upgrade, buy extra credits in bundles of 1,000 or 10,000 at your plan's fixed price, or turn on auto-purchase of 10,000 credits on Core, Pro and Teams.
Credits expire at the end of the term, so they do not build up forever. Extra credits expire after a month on monthly plans, or at the end of the year on annual Pro and Teams.
If a scenario matters, turn on auto-purchase, because it stops when the credits run out.
Worked examples: Make against Zapier
These are examples we chose. The conversion into credits and tasks and the choice of tier are our arithmetic, using prices billed annually. Make counts the trigger as a credit and Zapier does not, so a five-step workflow is five Make credits and four Zapier tasks.
| Example workload | Make credits | Make Core | Zapier tasks | Zapier Professional |
|---|---|---|---|---|
| 5,000 runs of a five-step workflow | 25,000 | $29 (40,000 tier) | 20,000 | $189 |
| 50,000 runs of the same workflow | 250,000 | $182.16 (300,000 tier) | 200,000 | $769 |
| 2,000 orders, 20 line items each, two actions per item, plus three steps per order | 86,000 | $99 (150,000 tier) | 84,000 | $489 |
Make costs less at these volumes. The price leaves out what you may value more: Zapier's app catalogue and how quickly non-technical people can use it. If your scenarios need heavy looping or code, price n8n too, because it bills per workflow run. n8n vs Zapier vs Make compares the three on more than price.
How to pick a tier
- Take your busiest scenario and count the modules that run, including the trigger. Add iterations: a module inside an iterator counts once per item.
- Multiply by runs per month, then repeat for your other scenarios.
- Add a margin for retries and busy months. Choose the tier above that total.
- Choose annual billing only when your usage is steady, because unused credits expire.
When to get help
Most Make accounts do not need an outside engineer. Get help when a scenario touches money, stock or customers and failures go unnoticed, or when nobody left at the company understands how it works. Our Zapier and Make page covers audits, rebuilds and moves to other tools. One critical automation rebuilt with error handling and alerts is an AI Quick Win Sprint at $8,000 fixed over 3 weeks. A wider migration is staffed as an embedded team at $3,000–$7,500 per engineer per month. Before you spend on either, the AI ROI calculator shows what the workflow's hours are worth.
