Disclosure: some links on this site may be affiliate links. If you buy through one, we may earn a commission at no extra cost to you. It never changes what we write or how we rank things. Details.

Make plans compared: Free vs Core vs Pro vs Teams, and what each upgrade adds (checked November 2026)

Updated November 14, 2026 · Facts come only from the vendors' official pages listed under Sources. We have not run paid accounts on these products for this page.

Make's paid plans differ in two ways. The credit tier you pick on the slider sets how much work your scenarios can do each month. The plan (Core, Pro or Teams) sets everything else: how many scenarios can be active, how often they can run, how long a run may take, how big a file can be, how long logs are kept, and which features you get. Our Make credits explained page covers the first part. This page covers the second: every row of Make's plan comparison table, what each upgrade costs at the 10,000-credit tier, and the lowest plan for a given need.

The short answer

• Free is for trying Make. 1,000 credits a month, 2 active scenarios, scheduled runs at most every 15 minutes, runs of up to 5 minutes, 5 MB files and 7 days of logs. No Make Code app and no Make API.
• Core ($9 a month) lifts almost all of that. Unlimited active scenarios, scheduling down to the minute, 40-minute runs, 100 MB files, 30 days of logs, the Make Code app and the Make API at 60 calls a minute. For one person automating their own work, Core is the plan most of the comparison table points to.
• Pro ($16, $7 a month more) adds four things: custom variables, full-text search of execution logs, "High" priority execution and, on annual billing, a year's credits you can use in any month (on Core they reset every month even when billed annually). Files go up to 250 MB and the API to 120 calls a minute.
• Teams ($29, $13 a month more than Pro) is about structure, not people. It adds more than one team with roles, 3 event subscriptions, 500 MB files and 240 API calls a minute. Every plan, Free included, has unlimited users, so you do not need Teams just to invite colleagues.
• Enterprise (custom price) adds single sign-on, audit logs, custom roles, 60 days of logs, overage protection and enterprise apps.
• Credits cost more on each higher plan: $0.90 per 1,000 on Core, $1.60 on Pro and $2.90 on Teams at the 10,000-credit tier. Upgrade for a feature you need, not for the credits.

Prices at the 10,000-credit tier

• Monthly billing: the page marks annual billing "Save 15%", but the monthly prices only appear after switching the toggle in a browser, so we do not list them.
• Other tiers: the slider sets the credit tier and the price follows it. Only the 10,000-credit tier is in the page text.
• Extra credits cost 25% more than your plan's own credits, bought by hand in units of 1,000 or automatically in units of 10,000, and only on paid plans. The column above is our arithmetic from that rule; Make's own example gives the Core figure, $1.125.
• Annual credits: with annual billing, Pro and Teams give you the whole year's credits at once, to use whenever you like over the year. Make's Help Center gives the example of 10,000 a month on Pro becoming 120,000 a year. Core keeps a monthly allocation even on annual billing.

Every limit and feature that differs by plan

These two tables are Make's comparison table, row for row, for the rows where the plans differ. "Yes" and "No" stand for Make's "Included" and "Not included".

Limits

Data transfer grows with your credit tier: Make allows 5 GB per 10,000 monthly credits, so the 5GB above is the 10,000-credit tier and Free's 512MB goes with its 1,000 credits. The API limits match Make's developer documentation (60, 120, 240 and 1,000 calls a minute); going over returns an error 429.

Features

Two rows don't fit a table:

• Make Code App (JavaScript or Python inside a scenario): not on Free. On Core, Pro and Teams the table says "2 credits per 1 sec of code execution time"; on Enterprise the same, plus "Extended resources".
• Customer support: Free gets "90-day expert access to get started"; Core and Pro "Technical support from our expert team"; Teams "High-priority guidance from dedicated consultants"; Enterprise "24/7 top-priority assistance from senior specialists".

Only on Enterprise

These rows are "Not included" on Free, Core, Pro and Teams:

• Custom scenario properties
• Custom functions
• Access to enterprise apps
• On-prem agent
• Dynamic connections
• Custom Roles
• Analytics Dashboard
• Audit logs
• Credits overage protection
• Access to the Value Engineering Team
• Information security compliance support
• Two-factor authentication enforcement
• Company single sign-on (SSO)
• Domain claim

On every plan, Free included

• Maia by Make
• AI applications
• MCP server
• AI Content Extractor
• AI Web Search (marked beta)
• Make AI Agents (marked beta)
• Make AI Toolkit
• No-code workflow builder
• System variables
• Scenario inputs
• Scenario Outputs
• 3,500+ standard apps
• Custom apps
• Parallel scenario execution
• Subscenarios
• Real-time execution monitoring
• Unlimited users
• Private Spaces
• Two-factor authentication

All plans are hosted on AWS (EU/North America), per the table's last row.

Free to Core: the upgrade most people need

Free is a trial in practice, and the limits that end it are mostly not about credits:

• 2 active scenarios. A third workflow means switching one off.
• 15 minutes between scheduled runs. Core allows every minute, but the credits do not stretch that far: a scenario that checks for new data every minute uses 43,200 credits a month on checks alone (30 days, by our arithmetic), more than four times the 10,000-credit tier. Checking every 5 minutes uses 8,640, which leaves 1,360 of the 10,000 for the actions. Our credits page has the full table.
• Free's 1,000 credits run out early on a schedule. Checking every 15 minutes is 96 checks a day, so 1,000 credits last about 10 days with no actions at all.
• 5-minute runs and 5 MB files. Anything that processes a long list or handles attachments, PDFs or images can hit these first. Core allows 40 minutes and 100 MB.
• 7 days of logs. When something fails, Core keeps 30 days of execution history to look back through.
• No Make Code app and no Make API. Code steps (2 credits per second of run time) and managing Make from your own scripts both start at Core.

At $9 a month for 10,000 credits, Core also has the lowest price per credit of the paid plans at that tier.

Core to Pro: $7 a month for four things

Pro costs $7 a month ($84 a year) more than Core at the 10,000-credit tier. For that you get:

• Custom variables. Values defined for the whole organization or a team and shared by many scenarios: a setting such as TestMode = true/false, a limit you want to change without editing each scenario, or a value kept between runs. A scenario can change a value; the new value applies from the next run. Make warns that they are stored in plain text and visible to other members, so they are not for passwords or keys.
• Full-text execution log search. Search for any term in module outputs across your scenario history, for example a customer's name in a run that seemed to succeed. After an upgrade it only finds runs made after the upgrade.
• Priority execution, "High". Make describes priority as running your scenarios during peak usage times to minimize queuing time. It does not say how long the queue is on Core, so we can't put a number on the gain.
• A yearly pool of credits on annual billing (120,000 at the 10,000-credit tier), instead of 10,000 that reset each month.

Pro also raises the file limit to 250 MB and the API to 120 calls a minute.

Is Pro worth it just for the yearly credits?

Only if your usage is very uneven. On Core billed annually, a busy month that needs more than 10,000 credits is covered with extra credits at $1.125 per 1,000. Pro's $84 a year buys about 74,667 of those, by our arithmetic. So the yearly pool pays for itself only when your busy months need more than about 75,000 extra credits a year in total.

Our arithmetic at the 10,000-credit tier: Core's extra credits cost $9 ÷ 10,000 × 1.25 per credit, and all three years fit inside Pro's 120,000. A bigger Core tier for the busy months could also work, but its price is not in the page text.

Pro to Teams: $13 a month for team structure

Teams costs $13 a month ($156 a year) more than Pro, and $20 a month ($240 a year) more than Core, at the 10,000-credit tier. What it adds:

• Teams and team roles. Below the Teams plan, an organization has one team and you can't manage roles inside it, per Make's Help Center. With Teams you can split scenarios, connections and data into separate teams and give each person a role in each.
• Event subscriptions. Make sends events about your scenarios and organization to an HTTPS endpoint you control. Teams includes 3 per organization; deactivated subscriptions still count.
• Scenario templates. The comparison table lists "Create and share scenario templates" from Teams up. Make's Help Center page on scenario templates says templates are available on all plans and anyone can create and share them. We could not tell which is current, so ask Make before buying Teams for templates alone.
• Priority, support and limits. Priority execution is "Priority" (Pro's is "High"; Make doesn't define the difference), support is "High-priority guidance from dedicated consultants", files go to 500 MB and the API to 240 calls a minute.

What Teams does not add is seats: every plan has unlimited users, and every person gets a private space to build in.

Which plan do you need?

The lowest plan that has each item, read from the comparison table:

Then pick the credit tier for the work: our automation cost calculator estimates a month's credits from runs and steps, and Make credits explained covers what counts.

Downgrading and cancelling

• Downgrading: per Make's FAQ, active scenarios that use a feature of the higher plan are stopped, and Make tells you before you confirm. Our reading: moving from Pro to Core would stop a scenario that uses custom variables. Make charges the new plan straight away and the billing cycle starts again from that day; unused credits move to the new plan for its first month (or year).
• Upgrading: unused credits become a discount on the new plan, at your current plan's price per credit.
• Cancelling: the paid plan runs to the end of its month or year, then the organization moves to Free. The exception, per the FAQ: if the user who holds the subscription already has another Free organization, the subscription is removed instead and no credits run until a plan is added.

Check the current numbers

• Make pricing (the comparison table is below the plan cards)
• What uses a credit, and what extra credits cost: Make credits explained
• Make against n8n by runs and steps per run: n8n vs Make
• Make against Zapier by runs and steps per run: Make vs Zapier
• All three side by side: n8n vs Make vs Zapier pricing and the automation cost calculator

Sources

1. Make pricing page (plan cards, comparison table, FAQ) — https://www.make.com/pricing, checked November 14, 2026
2. Make Help Center: Monthly and annual subscriptions — https://help.make.com/monthly-and-annual-subscriptions, checked November 14, 2026
3. Make Help Center: Change your subscription — https://help.make.com/change-your-subscription, checked November 14, 2026
4. Make Help Center: Extra credits — https://help.make.com/extra-credits, checked November 14, 2026
5. Make Help Center: Custom variables — https://help.make.com/custom-variables, checked November 14, 2026
6. Make Help Center: Scenario history (full-text execution log search) — https://help.make.com/scenario-history, checked November 14, 2026
7. Make Help Center: Teams — https://help.make.com/teams, checked November 14, 2026
8. Make Help Center: Scenario templates — https://help.make.com/scenario-templates, checked November 14, 2026
9. Make Help Center: Event subscriptions — https://help.make.com/event-subscriptions, checked November 14, 2026
10. Make Developer Hub: Rate limiting — https://developers.make.com/api-documentation/getting-started/rate-limiting, checked November 14, 2026