Make pricing explained: every plan and what a credit buys

Our verdict: price the credits, then the plan

Make sells credits, and the plan you need follows from how many credits your scenarios burn in a month. [1] The most useful thing you can do before choosing a tier is count credits for each scenario you plan to run, including the trigger. Picking a plan by feature list first usually leads to either an idle allowance or a mid-month stop.

Who this fits: anyone about to move from Free to a paid Make plan, or anyone comparing Make's bill with another tool. Who can skip it: a person whose scenarios already fit comfortably in Free's 1,000 monthly credits and who does not need paid-only features such as extra credits or a custom AI provider connection. [1] [4]

What each plan includes, per the official pages

The table lists only what Make's pricing page and help center stated in text we could read on 2026-10-29. The pricing grid with dollar amounts, credit tiers and per-plan limits did not appear in that text, so those cells say so rather than repeat figures from third-party sites. Open the pricing page in a browser for the live grid in your currency.

What a credit buys

Make's help center splits credit use into two kinds. Fixed usage means a module costs a set number of credits per operation; Google Drive Upload a File always uses 1 credit, for example, and most non-AI apps are 1 operation to 1 credit. [2] Dynamic usage varies per run, usually because of AI tokens, and sometimes because of file size, page count or processing time. [2]

The pricing page lists reading data from an app or webhook, searching, creating, updating and deleting data, plus transforming, aggregating and iterating rows, as actions that consume credits. The Router module and the error handler modules (Rollback, Break, Resume, Commit, Ignore) do not. [1]

Credits also set your usage allowances. For every 10,000 credits licensed per month, Make lists 5 GB of data transfer, 10 MB of data storage, 10 MB of incomplete-execution storage (2 GB maximum) and a webhook queue of 667 (10,000 maximum). [1] A tier with more credits therefore also gives more transfer and storage room.

Worked monthly totals for three sample workloads

All three workloads are hypothetical. Each counts one credit per non-AI module operation and assumes one record per run. Confirm the real count in your scenario history before buying.

Workload A, form to CRM: a webhook trigger receives a form entry, then three action modules create a contact, add a tag and post a team message. That is 4 credits per run. At 400 entries a month it is 1,600 credits, which is 600 more than Free's 1,000. [1]

Workload B, hourly inventory check: a scheduled trigger runs every hour. Make's own tutorial counts an hourly trigger at 24 credits a day, or 720 a month, before any records are processed. [5] If 50 changed items a month each pass through three more modules, add 150 credits for about 870 in total. That fits Free, with little headroom.

Workload C, AI-assisted ticket triage: a webhook trigger, one AI module using Make's AI Provider on the Large tier, and two action modules. Make lists the Large tier at 3,616 input or 452 output tokens per credit. [2] A ticket that sends 1,500 input tokens and gets 200 output tokens back adds about 0.86 token credits, assuming input and output are charged separately and added. With 4 operation credits, that is about 4.9 credits per ticket, or about 4,900 credits for 1,000 tickets.

Turning credits into a dollar figure

Once you know your monthly credits, pick the smallest tier on the live price grid that covers them with a margin for retries. If you expect to go over occasionally, Make prices extra credits at the plan's per-credit rate plus 25 percent, where per-credit rate means plan price divided by included credits. [4] Manual top-ups move in steps of 1,000 credits; automatic purchases are always 10,000 credits and are capped at your subscription's credit amount, so an 80,000-credit plan allows up to 8 auto-purchases per cycle. [4]

Formula, with P as the tier's monthly price and C as its included credits: monthly cost = P + (extra credits bought x P / C x 1.25). If you regularly buy more than about a fifth of your allowance in extras, compare the next tier up, because the extras carry the 25 percent premium.

Annual billing details that change the math

• Core on annual billing still allocates credits monthly. Unused Core credits do not pile up for a busy month. [3]
• Pro and Teams on annual billing allocate the whole year of credits up front, which suits seasonal workloads. [3]
• Credits expire at the end of the term, and extra credits bought on a monthly plan are valid until the end of the current billing cycle. [1] [4]
• Downgrading stops active scenarios that use higher-plan features and charges the card immediately; cancelling keeps the paid plan until the cycle ends, then moves you to Free. [1]

Checklist before you pay

• List every active scenario with its trigger type and schedule.
• Count credits per run, including the trigger, and multiply by last month's runs.
• Add polling checks separately for scheduled triggers. [5]
• Add token credits for any step on Make's AI Provider. [2]
• Choose the tier that covers the total plus 20 percent, then read the price in the live grid.
• Decide between monthly and annual billing using the allocation rules above.

Sources & verification

Product details and prices can change. Check the linked provider before buying.

1. Make pricing Accessed 29 Oct 2026
2. Make Help Center: Credits Accessed 29 Oct 2026
3. Make Help Center: Monthly and annual subscriptions Accessed 29 Oct 2026
4. Make Help Center: Extra credits Accessed 29 Oct 2026
5. Make Help Center: Schedule your scenario (tutorial step 10) Accessed 29 Oct 2026