Make Pricing 2026: Annual vs Monthly Billing and Credit Limits
Compare Make's annual and monthly billing, Free-plan limits and credit rules. Estimate billable work before choosing an automation plan.
By ToolVerdict Editorial · Data verified October 8, 2026
Affiliate disclosure: We may earn a commission if you sign up through our Make referral link, at no extra cost to you. The prices below come from Make’s own published price list; the referral link does not change your price.
Make prices by credits, not by seats. Before paying for Make, estimate the billable work in your busiest scenario and check its scheduling and file limits. A credit allowance is not a promise of a fixed number of finished workflows; code, AI steps and repeated runs can change usage. This guide separates annual and monthly billing and the limits that may rule out Free.
Everything below was read from Make’s pricing page on October 8, 2026, including the underlying price list the page loads. This is a documented price check, not a measured performance test.
Plans at 10,000 credits/mo
The headline prices on Make’s page default to annual billing. Monthly rates are higher.
| Plan | Annual (per month) | Monthly billing | Best for |
|---|---|---|---|
| Free | $0 | $0 | Trying the builder |
| Core | $9/mo | $10.59/mo | Solo automation, first real workflows |
| Pro | $16/mo | $18.82/mo | Priority execution, custom variables |
| Teams | $29/mo | $34.12/mo | Shared templates and team roles |
| Enterprise | Custom | Custom | Security, SSO, overage protection |
Make advertises “Save 15% or more” on annual billing. Annual credits are prepaid for the year and, on Pro and Teams, expire at the end of that year rather than monthly.
The full credit ladder
Credits per month are selectable in steps. Core stops at 300,000; Pro and Teams continue to 8M.
Core
| Credits/mo | Monthly | Annual (per month) |
|---|---|---|
| 10,000 | $10.59 | $9.00 |
| 20,000 | $18.82 | $16.00 |
| 40,000 | $34.12 | $29.00 |
| 80,000 | $64.71 | $55.00 |
| 150,000 | $116.47 | $99.00 |
| 300,000 | $214.31 | $182.16 |
Pro
| Credits/mo | Monthly | Annual (per month) |
|---|---|---|
| 10,000 | $18.82 | $16.00 |
| 20,000 | $34.12 | $29.00 |
| 40,000 | $62.35 | $53.00 |
| 80,000 | $107.06 | $91.00 |
| 150,000 | $180.53 | $153.45 |
| 300,000 | $315.93 | $268.54 |
| 500,000 | $482.67 | $410.27 |
| 1,000,000 | $880.86 | $748.73 |
| 8,000,000 | $5,660.47 | $4,811.40 |
Teams
| Credits/mo | Monthly | Annual (per month) |
|---|---|---|
| 10,000 | $34.12 | $29.00 |
| 20,000 | $62.35 | $53.00 |
| 40,000 | $116.47 | $99.00 |
| 80,000 | $203.41 | $172.90 |
| 150,000 | $343.01 | $291.56 |
| 300,000 | $600.26 | $510.22 |
| 1,000,000 | $1,647.85 | $1,400.67 |
| 8,000,000 | $9,683.59 | $8,231.05 |
Tier prices are the same dollar amount shifted along the ladder — Pro at 10k costs what Core costs at 20k. Buying a higher tier is buying features, not a cheaper credit.
How credits are actually counted
Make’s own FAQ defines the rule:
- Each module action consumes credits — reading data, creating or updating a record, writing a row, posting a message, transforming or aggregating data.
- Routers and error handlers (Rollback, Break, Resume, Commit, Ignore) consume zero credits.
- Custom code runs at 2 credits per second of execution time.
- A scenario can cost anywhere from two credits to thousands per run, depending on modules.
When credits run out, scenarios stop until more are added. Make notifies at 75% and 90% of purchased credits, incoming webhooks queue up to the queue limit, and polling scenarios resume searching from their last successful run.
Extra credit bundles are sold in 1,000 or 10,000 packs at your subscription price. Auto-purchasing 10,000 credits before you run dry is available on Core, Pro and Teams.
Free plan: what you actually get
| Limit | Free | Core and above |
|---|---|---|
| Credits | 1,000/mo | From 10,000/mo |
| Active scenarios | 2 | Unlimited |
| Minimum schedule interval | 15 minutes | 1 minute |
| Max scenario run time | 5 minutes | 40 minutes |
| Max file size | 5 MB | 100 MB (scales to 1 GB) |
| Data transfer | 512 MB | 5 GB per 10,000 credits |
| Execution log history | 7 days | 30 days (60 on Enterprise) |
| Apps | 3,000+ | 3,000+ |
| Make API | — | Core and above |
| Priority execution | — | Pro and above |
There is no time limit on the Free plan. The binding constraints are the 15-minute interval, two active scenarios and the 5-minute run ceiling — enough to build and run real workflows, not enough for anything schedule-sensitive.
What the plans change beyond credits
- Core lifts the scenario count, adds minute-level scheduling, the Make API and larger files.
- Pro adds priority execution (less queueing at peak), custom variables and full-text execution log search.
- Teams adds team roles and shareable scenario templates.
- Enterprise adds custom roles, SSO, audit logs, overage protection, 24/7 support and value engineering onboarding.
Every tier includes the visual no-code builder, 3,000+ standard apps, routers and filters, Make Code (JavaScript/Python), AI agents and the Make MCP Server.
What a month of Make actually costs
These are hypothetical arithmetic examples from Make’s published credit rules, not bills from a running account.
Daily lead routing. One scenario run per day, three module actions per run (read a form, create a record, send an email) = 3 credits × 30 days = 90 credits/month. Comfortably inside Free’s 1,000.
Hourly digest, 8 hours a day. 8 runs/day × 4 actions = 32 credits/day = 960 credits/month. Still under Free, but only because Free’s minimum interval is 15 minutes — an every-5-minute schedule would not be possible on Free at all.
Four busy workflows at 15-minute intervals. 4 scenarios × 96 runs/day × 5 actions = 1,920 credits/day ≈ 57,600 credits/month. That lands on Core’s 80,000-credit annual tier at $55/mo, or Pro at $91/mo if you need priority execution.
The lesson: count module actions, not scenarios. A five-module scenario at 15-minute intervals burns roughly 14,400 credits a month by itself.
FAQ
Are credits the same as operations? Yes in substance. Make renamed operations to credits as the billing unit on August 27, 2026; the price list still labels the field operations.
Do unused credits roll over? Credits expire at the end of the term. On annual Pro and Teams, prepaid credits last 12 months instead of one month.
What happens if I exceed my credits? Scenarios pause. You can upgrade, buy bundles, or enable auto-purchase on Core, Pro and Teams. Enterprise adds overage protection.
Which payment methods work? Core, Pro and Teams accept major cards, ACH direct debit and Google Pay; Enterprise adds wire transfer after invoice.
Is annual billing cheaper? Yes — Make advertises 15% or more off, prepaid.
Are these prices still valid? They were read from Make’s own price list on October 8, 2026. Re-check before switching to annual billing.
The bottom line
Free is a genuine working tier for under a thousand credits a month; Core at $9/mo annual is where unlimited scenarios and minute-level scheduling start. The real question is always the same: count the module actions in your busiest workflow, multiply by runs per month, and buy the credit bucket that fits — not the tier logo that looks right.
Evaluate your workflow on Make Free, then compare the plan limits before upgrading.
Start Make free · Zapier versus Make · n8n versus Make · Make alternatives