Make pricing 2026: plans, credits and what you'll pay
2026-11-03 · 9 min read
Rather not build it yourself? We build the automation on your tools and keep it running. Get it built for me→
It's Tuesday morning and a scenario that has run fine for three months has stopped. Your web form leads aren't reaching the spreadsheet, and the new-lead text to your phone didn't go out overnight. You log in to Make and see the reason in the corner: you're out of credits for the month, on the 19th. You didn't add a single workflow. You did change one schedule from every 15 minutes to every minute, because a customer said the confirmation email felt slow.
Make pricing is cheap at the start and easy to misjudge, because the bill follows credits, and credits follow how your scenarios are built. This post covers what each plan costs, how Make counts usage, what happens when credits run out, and how to estimate what a small business will actually pay. Everything below comes from Make's own pages, which I checked on November 3, 2026, and each one is linked where I use it.
Make pricing at a glance
One caveat first. Make's pricing page builds its plan cards in the browser, and when I checked, the cards didn't come through in a plain page fetch. The FAQ on that page did. The plan prices below come from Make's other pages, and those pages don't all show the same numbers.
| Plan | Price at 10,000 credits a month | Where Make says it | What the plan adds |
|---|---|---|---|
| Free | $0, 1,000 credits a month | Pricing FAQ, Make blog, August 4, 2026 | No credit card, no time limit, 1 MB of data storage and 1 data store |
| Core | $12 a month | Make blog, June 18, 2026 and August 4, 2026 | The entry paid plan; tiers up to 300,000 credits a month |
| Pro | $21 a month | Same two posts | Priority execution; tiers up to 8 million credits a month |
| Teams | $38 a month | Same two posts | Shared development for more than one builder |
| Enterprise | Custom pricing | All of the pages above | Single sign-on, audit logs, 24/7 priority support with a 2-hour response target, 99.5% uptime commitment |
Make's own Make vs Zapier page shows lower figures for the same 10,000-credit tier: Core $9, Pro $16 and Team $29 a month, "as of November 2025." That page doesn't say whether those are monthly or annual-billing prices. The pricing FAQ does say "prices are cheaper with the annual payment in advance compared to monthly payments," and when I checked Make's pricing page for Zapier vs Make on September 25, it showed Core at $12 billed monthly. My read is that $9, $16 and $29 are annual-billing prices, but I couldn't confirm it on Make's site. Toggle the switch on the pricing page yourself before you budget.
Two things I couldn't find on any page I could read: the yearly price for each plan, and the per-plan limits (active scenarios, shortest schedule, longest run time, file size, log retention). Those live on the plan cards. Check them there if one of them matters to you.
How Make counts credits
Make bills in credits. The pricing FAQ says "most actions consume 1 credit," and Make's help page on credits says that for regular apps, "1 operation equals 1 credit." What counts as an operation, then?
According to Make's help page on operations, "an operation is a single module run to process data or check for new data." Three rules follow from that, and they explain most of the surprise bills I've seen:
- The trigger counts, even when it finds nothing. A scenario that checks a form for new entries spends a credit on every check, including quiet nights and weekends.
- Every item counts separately. A module runs once for each item passing through it. Make's own example is a trigger that returns 10 items with three modules after it: 31 operations for one run.
- Some modules are free. The pricing FAQ says routers and the error-handling modules (Rollback, Break, Resume, Commit, Ignore) don't use credits.
The FAQ also says some advanced features built on Make's own model provider can use more than one credit per action. If you add those to a scenario, watch the usage report in the first week.
What a small business actually pays
Here's the arithmetic for workflows I see all the time, using Make's counting rules above. These are estimates. Your own usage report is the real number.
| Workflow | Credits per month | Plan that covers it |
|---|---|---|
| Web form lead: trigger, add a sheet row, create a CRM contact, text the owner, email the lead. 200 leads a month on an instant trigger | About 1,000 | Free, barely, or Core with plenty of room |
| Same workflow, but the trigger checks every 15 minutes instead of firing instantly | About 1,000 plus about 2,900 checks | Core |
| Same workflow, checking every minute | About 1,000 plus about 43,200 checks | Well past Core's 10,000-credit tier |
| Nightly job that copies 50 new invoices into a spreadsheet, five steps per invoice | About 7,500 | Core at 10,000 |
The third row is the one from the opening scene. A 30-day month has 43,200 minutes, so a trigger that checks every minute spends 43,200 credits before it moves a single lead. Fixing it is free: use an instant trigger (a webhook that fires when the form is submitted) wherever the app offers one, and set scheduled checks only as often as the work needs.
Make doesn't publish a full price table for higher credit tiers on the pages I could read. Its help article on changing your subscription gives one example: "The Core plan costs $113.85 for 150,000 credits per month." Its November 2025 plan update gives another: a customer paying $338.13 a month for 500,000 credits on Core keeps that price when moved to Pro. Most small businesses never come close to either.
What happens when you run out
Make's pricing FAQ is direct about this: "Your scenarios won't continue to run, until credits are added again." Webhooks that arrive in the meantime wait in a queue, and polling scenarios pick up records from their last successful run once they restart. The queue has a limit, though. The FAQ sizes it at 667 webhooks per 10,000 credits, up to 10,000, so a long outage on a small plan can still lose work.
To get running again, you have three options:
- Upgrade to a bigger credit tier or a higher plan. Make turns your unused credits into a dollar discount on the upgrade, per the subscription help article.
- Buy extra credits in bundles of 1,000 or 10,000. Since November 6, 2025, extra credits cost 25% more than the credits in your plan, whether you buy them by hand or automatically, according to Make's announcement.
- Turn on auto-purchase, which buys 10,000 credits before you run out. The FAQ says that's available on Core, Pro and Teams.
Credits don't roll over. The FAQ says plan credits "expire at the end of the term," and extra credits expire after one month on a monthly subscription. The subscription article adds a detail for annual Core plans: credits reset every month, and extra credits expire with that reset. Buying a big credit pack in a slow month doesn't bank anything for a busy one.
The rest of the fine print
- Your data allowance scales with credits. Per 10,000 credits a month, the FAQ lists 5 GB of data transfer, 10 MB of data storage and 10 MB for incomplete executions. If you move large files or images through Make, check that this is enough.
- Downgrades can switch scenarios off. Per the FAQ, "any active scenarios using features of higher plans will be stopped" when you move down a plan.
- Canceling takes effect at the end of the term. A paid plan runs to the end of its billing cycle or annual term, then drops to Free.
- Core, Pro and Teams take major cards, ACH direct debit and Google Pay. Nonprofits are asked to contact sales about discounts.
Make vs the other tools on price
At low volume Make tends to be the cheapest hosted option, since its entry tier includes a lot of credits. The trade-off is that a credit and a Zapier task don't measure the same thing: Zapier doesn't charge for triggers, and Make does. I priced one workflow on both in Zapier vs Make, and the full Zapier tiers are in Zapier pricing. If you're comfortable running your own server, n8n pricing covers the self-hosted route.
What stays with a person
A Make plan moves the data. Somebody still has to decide what the scenarios should do: which leads get a call back first, what a confirmation email says, when a follow-up should stop. Somebody has to read the failure alert and decide whether it matters, and that's the step I see skipped most. A scenario stops at 2am and nobody knows until a customer calls asking why they never heard back. Before you build anything, name the person who gets the alert and checks the usage report once a month.
When a plan isn't the answer
Make is a good tool for moving data between apps. It gets awkward when the process carries real business rules, like quotes that change with the form answers or leads routed by job type and town. That's when owners end up with a canvas only one person understands. I wrote about where that line falls in Zapier vs custom automation, and the business automation page shows what I build for Illinois businesses. For a freight forwarder, I set up intake so quote, import, export and general inquiries each arrive sorted instead of piling into one inbox. Builds start at $500 one-time, then a flat monthly from $99 after an included run-in period, cancellable. Plenty of the time, a $12 Make plan and an afternoon of setup is the better choice, and I'll say so.
If you're pricing Make, or your credits keep running out before the month does, book the free 20 minute process audit. We'll look at your scenarios and your week, and work out whether the fix is a schedule change, a bigger tier, or something else.