Make.com Core vs Pro: $16 Buys 20,000 or 10,000 Credits

Short answer: if you are buying Make for more credits, buy Core. If you are buying it for one of three tools, buy Pro. On Make's pricing page (11 October 2026), $16 a month buys 20,000 credits on Core or 10,000 on Pro, billed yearly, and $29 buys 40,000 on Core or 20,000 on Pro. Pro's extra money pays for custom variables shared across scenarios, full-text search of your run logs, a faster queue at peak times, and a yearly credit pool. A coach or consultant running booking confirmations needs none of those: our own 4-step booking flow used 4 credits a booking, so Core's 10,000 credits cover 2,500 bookings a month. An agency running the same scenarios for many clients is who Pro is priced for.

This page is a source roundup of Make's own pages, plus credits we measured ourselves. The prices, plan rows and rules below come from make.com/pricing and Make's help centre, captured on 11 October 2026 in a fresh browser with no login. The credits per booking come from our own Make account, which we have run on the Free plan since 18 September 2026. We have not paid for Core or Pro, so we have not used any Pro-only feature ourselves, and this page has no rating. How we draw that line: how we test.

What we measured and what we only read

For what the Free plan does before you need either paid plan, see our Make.com free plan test, where we ran an account down to zero credits.

Same money, twice the credits on Core

This is the table to read before anything else. Make sells both plans in credit tiers, and up to 40,000 credits a month the pattern is exact: Pro at any tier costs what Core costs at double the credits.

Prices are per month, read on make.com/pricing on 11 October 2026 with the credit slider set to each tier. Teams starts at $29 a month yearly for 10,000 credits.

So the first question is not "Core or Pro". It is "do I need more credits, or do I need a Pro feature?" If you keep running out, Core's next tier gives you twice the credits Pro would for the same bill. Make says it itself on its extra-credits page: "Higher-tier plans have lower per-credit costs."

How many credits you need depends on how many modules each run touches. Our Make credits calculator does the sum for your own flow; for ours, a booking that reads a sheet, sends a Gmail, adds a calendar event and updates the sheet costs 4 credits.

What Pro adds over Core

Make's plan card lists three things under "Everything in Core, plus". The comparison table further down the page shows three more differences. Everything else in the two columns is the same.

Make labels Pro "Recommended" on the pricing page. That is Make's choice of which card to highlight, not a measure of what your scenarios need.

Custom variables: one switch for every scenario

A custom variable is a value stored once at the team or organization level that any scenario can read. Make's help page gives the examples: a TestMode = true/false switch that makes scenarios route differently, a limit such as myLimit = 20 set in a module's field, or a value that has to survive between runs. Change it once and every scenario using it changes, without editing each scenario.

That is the feature an agency or consultant feels. If you run the same lead or booking scenario for ten clients, a shared variable is how you change a setting across all ten. A solo business with two or three scenarios can type the value into each one. Make also warns that variables are stored in plain text, so they are not a place for passwords or API keys.

Full-text log search: find one failed run

Both plans keep detailed run logs for 30 days. Pro adds a search box over them: Make describes it as a way to "quickly search for, identify, and troubleshoot items in your scenario execution history". In practice that is the difference between typing a client's email address to find the booking that failed on Tuesday and opening runs one by one.

With one booking scenario and a handful of runs a day, scrolling the history is quick. With many scenarios and thousands of runs, it is not.

Priority execution: a shorter queue at busy times

Make says priority execution lets scenarios run "during peak usage times to minimize queuing time". Core has none, Pro has "High", Teams and Enterprise have "Priority". Make does not publish how long the queue is on Core, and we have not measured it, so we cannot put a number on the gain. If a few seconds of delay on a confirmation email does not matter to your business, this row should not decide your plan.

The yearly credit pool: real, but rarely worth $84

This is the least advertised difference and the one that changes the bill. On yearly billing, Pro hands you the whole year's credits up front: Make's example is 10,000 a month becoming 120,000 a year, usable in any month. Core keeps a monthly allowance even when you pay yearly, and its help page says extra credits bought on Core yearly also expire at each monthly reset.

That helps a business with lumpy months, such as a coach whose bookings arrive in one launch month. But price it before paying for it. Billed yearly, Pro costs $7 a month more than Core at 10,000 credits: $84 a year. On Core, Make sells extra credits at a 25% premium: its own example puts 10,000 extra credits on the $9 plan at $11.25. Seven of those packs cost $78.75 and add 70,000 credits.

So, by our arithmetic, Pro's pool only beats Core plus extras on price when your busy months overflow the plan by more than about 70,000 credits in a year. At 4 credits a booking, that is more than 17,500 extra bookings.

What our booking flow actually needed

We built the same booking automation on Make and Zapier in September (the full test is in our Make vs Zapier comparison). The Make version reads a new booking from a Google Sheet, sends a confirmation from Gmail, creates the Google Calendar event and marks the row done. It cost 4 credits per booking. A webhook version that only sent the email cost 2.

What it never touched: a shared variable, a log search, a file upload or the Make API. Every module it used is on the Free plan. On Free, the limits that stopped us were the 1,000 credits, 2 active scenarios and the 15-minute minimum between scheduled checks, and all three are lifted by Core, not by Pro.

The per-booking cost is our arithmetic: the yearly-billed monthly price divided by 2,500 bookings.

Where Core stops and Pro starts

Core is the right plan until one of these becomes true, in roughly this order for small service businesses:

1. You manage scenarios for several clients and want one place to change a setting (custom variables) or to find one client's failed run fast (log search).
2. Your files pass 100 MB, such as video or large exports. Pro raises the limit to 250 MB.
3. Your usage is seasonal and large, past the roughly 70,000-credit overflow above, and you pay yearly.
4. You call the Make API from your own tools more than 60 times a minute.

If none of those is true, the extra money buys nothing you will use. If you run out of credits instead, move up a Core tier.

Who should pick Pro, and who should skip it

Pick Pro if you are an agency, a virtual assistant or a consultant running the same automations for many clients. Shared variables and searchable logs are tools for running a fleet of scenarios, and that is the reader Make prices Pro for. Pay yearly if your usage is lumpy, so the 120,000-credit pool works for you.

Skip Pro if you are a coach, clinic, salon or consultant automating your own bookings, intake forms and follow-ups. On our measurements a booking costs 4 credits, so the decision is how many credits you need, and Core gives twice the credits for Pro's price. Skip it too if you only want speed: Make publishes no queue times, so the priority row is a label we cannot turn into seconds.

Not sure? Start on Core. Make's change-your-subscription page says that when you upgrade, your unused credits, including extras you bought, are turned into a dollar discount on the new plan, so moving from Core to Pro later does not throw away what you paid for. Make has a no-cash-refund policy, so the safe order is up, not down.

Core vs Pro at a glance

Both plans run unlimited active scenarios on a schedule as tight as every minute, and both sit above the $0 Free plan. If you are still choosing between Make and another tool, start with Make vs n8n or, for agencies, GoHighLevel vs Make.com. For the full plan ladder from Free to Teams, see our Make.com pricing guide; for AI agents, which bill by tokens on every plan, see Make.com AI agents pricing.