Make.com pricing starts with an ongoing Free plan offering 1,000 credits per month. Monthly paid configurations shown by Make are Core at $12, Pro at $21 and Teams at $38, each starting with 10,000 credits per month; Enterprise uses custom pricing through sales. Make pricing is best compared by credit consumption, operating limits and required plan capabilities rather than price alone. These USD plan details were checked on September 23, 2026.
How Make.com pricing works
Make measures automation usage in credits. Each module action generally consumes credits, while some AI features may consume more. This distinction matters when comparing Make with platforms that use terms such as tasks, operations, runs or executions because those units are not automatically equivalent.
A scenario can consume several credits during one run. For example, a record might enter through one module, pass through a transformation and then create records or notifications in other systems. The actions that execute determine consumption. Longer scenarios, conditional routes and high processing volume can therefore use capacity faster than a simple two-step transfer.
The listed Core, Pro and Teams prices use monthly billing at the displayed 10,000-credit starting configuration. Make also describes annual billing as cheaper, but the exact annual rates are not included here. The displayed currency is USD, and regional applicability was not specified. Unused credits expire at the end of the applicable monthly or annual term rather than rolling over indefinitely.
Subscription capacity is only one part of the budget. A connected app or external API may charge separately for its own account, requests or premium functionality.
Make.com free plan limits
The Make.com free plan provides 1,000 credits per month with no time limit. Readers looking for a Make.com free plan operations-per-month figure should use that credit allowance rather than treating credits and operations as interchangeable terms.
- Monthly allowance 1,000 credits
- Active scenarios Up to 2
- Scheduled-run interval A minimum interval of 15 minutes
- Execution time Up to 5 minutes
- File size Up to 5 MB
- Detailed logs 7 days
These Make.com free plan limits suit learning, prototypes and a small number of low-volume automations. The free tier becomes restrictive when you need more than two active scenarios, process files above 5 MB, require a scheduled scenario to run more frequently than every 15 minutes, or approach 1,000 credits before the end of the month.
The 5-minute execution limit also deserves attention when a scenario processes many records or waits on several connected services. Seven days of detailed logs may be sufficient for experiments but provides a short investigation window when an intermittent problem is noticed late.
Make.com pricing plans compared
The following Make.com pricing plans cover the documented monthly configurations. Core, Pro and Teams all show 10,000 credits at their starting configuration, so credit quantity alone does not explain the price difference. Plan-specific API rate limits and access to some advanced options vary, making required capabilities an important part of the decision.
| Plan | Price and billing | Included usage and material limits |
|---|---|---|
| Free | $0 per month | 1,000 credits monthly, 2 active scenarios, 15-minute minimum scheduled interval, 5-minute execution time, 5 MB files and 7 days of detailed logs |
| Core | $12 per month with monthly billing | 10,000 credits per month at the displayed starting configuration |
| Pro | $21 per month with monthly billing | 10,000 credits per month at the displayed starting configuration |
| Teams | $38 per month with monthly billing | 10,000 credits per month at the displayed starting configuration |
| Enterprise | Custom pricing through sales | Enterprise features and support |
Core is the lowest-priced documented paid starting point and provides ten times the Free plan’s monthly credit allowance. Pro and Teams begin with the same displayed 10,000-credit allowance at higher monthly prices, so they should not be selected merely to obtain more starting credits. Choose one only when its plan-specific capabilities match an operational requirement.
Enterprise is the sales-led option for organizations that need enterprise features and support. Its configuration should be evaluated against requirements such as governance, deployment access, support and expected usage rather than compared with the fixed monthly starting prices alone.
Choosing a Make plan for your automation workload
Start by estimating consumption for each scenario. Count the module actions that normally execute for one item, multiply by expected items or runs per month, and then allow for branches or features that consume additional credits.
Illustrative estimate Suppose a scenario handles 40 records per day and normally executes five module actions for each record. Over a 30-day month, the baseline estimate is:
40 records × 5 module actions × 30 days = approximately 6,000 credits
This example assumes each listed module action consumes one credit. Actual consumption can differ when routes execute differently or a feature uses more credits, so inspect representative scenario usage before relying on the estimate. A 6,000-credit baseline would exceed the Free plan’s 1,000-credit allowance but fit within the displayed 10,000-credit starting allowance of Core, Pro or Teams.
- Choose Free when your total is comfortably below 1,000 credits and two active scenarios, 15-minute scheduling, 5 MB files and short log retention are acceptable.
- Start with Core when you need the documented 10,000-credit paid configuration but have no identified requirement for a higher plan’s capabilities.
- Consider Pro or Teams when a required plan entitlement, access option or API rate limit justifies the higher subscription price, rather than assuming the plan name alone matches your organization.
- Discuss Enterprise when enterprise support or features are a defined requirement and a custom commercial arrangement is appropriate.
Build a representative scenario with realistic test data, confirm that its output is correct, and inspect how many credits the executed path consumes. Multiply that observed pattern by expected monthly volume, then leave practical headroom for growth and scenario changes. This produces a more reliable plan choice than estimating from the number of scenarios alone.
Explore more technology guides on Techistuff.
Frequently Asked Questions About Make.com pricing plans
Does Make have a permanently free plan?
Yes. Make’s ongoing Free plan has no time limit and includes 1,000 credits per month. It permits up to two active scenarios and has tighter scheduling, execution-time, file-size and log-retention limits than a growing automation workload may require.
What counts as an operation in Make?
Make describes current usage in credits rather than treating operations as a universal billing unit. Each module action generally consumes credits, while some AI features can use more. The number of credits needed therefore depends on which modules and routes actually execute.
How can I estimate monthly Make credits?
Multiply the expected number of workflow runs by the module actions that usually execute in each run. Then account for conditional branches, testing and features that may consume additional credits. Compare the result with actual usage after launching a representative test scenario.
Is annual Make billing cheaper?
Make describes annual billing as cheaper than monthly billing. Exact annual rates were not included with the monthly figures used in this guide, so compare the applicable annual total and commitment before selecting that billing option.
Does Make pricing include charges from connected services?
A Make subscription pays for the applicable Make plan and credit capacity. Connected apps, data providers or APIs may impose their own subscription or usage charges. Include those external costs separately when budgeting an automation.
