Make Pricing Explained: Plans, Credits, and Usage Guide

Make prices its automation service primarily on credit consumption, file capacity, and execution parameters rather than per-seat licensing. With unlimited users supported across tiers and annual billing enabling a 12-month credit rollover, choosing the right plan requires matching your workflow frequency, execution time, and data payloads against tier-specific execution boundaries.

How Make Pricing and Credits Work

Unlike platforms that charge based on individual user seats, Make’s pricing model is anchored in usage. Teams can invite unlimited users to collaborate, build scenarios, and manage connections without incurring per-seat penalties. Cost and plan allocation instead revolve around monthly or annual credit consumption, scenario execution speeds, and administrative capabilities.

Every action taken inside an automation workflow consumes resources from your credit pool. How quickly your credits deplete depends directly on the complexity of your automations, the frequency of execution, and the specific modules in use. Because base subscription rates fluctuate based on the specific credit package selected, buyers should consult Make’s official subscription packages to evaluate current entry costs and custom credit increments.

Credit Allocation and Expiration

Make provides flexibility in how credits are purchased and maintained:

• Monthly billing: Standard monthly subscriptions allocate a fixed quota of credits that reset at the end of each billing cycle. Unused credits generally do not roll over.
• Yearly billing: Selecting an annual commitment allows organizations to prepay for a yearly allotment of credits. These prepaid credits remain valid for 12 months rather than expiring at the end of each month, offering substantial flexibility for teams with seasonal or uneven workflow volumes.
• Credits overage protection: To prevent business interruptions when critical workflows spike, Make includes overage protection settings that allow scenarios to continue running even after your allocated quota has been met.

Code Execution and Custom Logic Costs

Standard no-code modules interact directly with third-party APIs or internal data tools. However, when advanced logic is required, Make provides the Make Code App to execute custom JavaScript or Python scripts. Running custom code incurs a distinct consumption rate: 2 credits per 1 second of code execution time. Teams running compute-heavy or long-running scripts must account for this duration-based drain alongside standard step executions.

Data Transfer and Payload Allowances

Data volume is directly tied to your plan level and credit volume:

• Scalable data transfer: Data transfers scale proportionally at 5 GB of data transfer per 10,000 monthly credits on paid tiers, compared to an introductory cap of 512 MB on entry-level free access.
• File size handling: Plans enforce strict per-file size ceilings. Maximum file sizes start at 5 MB on the free tier and scale across tiers to 100 MB, 250 MB, 500 MB, up to 1,000 MB on top-tier enterprise deployments.

Plan Tiers and Execution Boundaries

While credit counts determine raw volume, tier upgrades unlock crucial performance parameters that dictate how quickly and reliably scenarios run.

Built-in AI and Developer Features

Make includes native artificial intelligence tooling across its platform tiers, enabling workflows that parse unstructured inputs and automate decision-making:

• Maia by Make: Natural conversation interfaces to build and draft automations and AI agents.
• AI ecosystem: Direct integration with over 350 AI applications, alongside a dedicated MCP server to connect external AI frameworks to your Make scenarios.
• Native AI utilities: An AI Content Extractor to pull structured text and metadata from files, an AI Web Search tool (beta) for live web extraction, and Make AI Agents (beta) powered either by Make’s built-in AI provider or your own direct LLM API keys.
• Developer tooling: Beyond custom functions and scenario templates, developers gain access to over 300 public Make API endpoints, custom app builders, and dynamic connections that configure credentials at runtime rather than design time.

Key Limitations to Consider

When planning your automation budget, several operational boundaries should guide your choice:

• Execution timeouts: Scenarios on the free plan are terminated after 5 minutes of run time, while paid plans extend this ceiling to 40 minutes. Long batch processes that exceed 40 minutes must be broken into smaller subscenarios.
• File size ceilings: If your workflows manipulate raw video, audio, or high-resolution graphics, the 100 MB or 250 MB limits on lower-tier plans may block processing, necessitating higher subscription tiers regardless of your overall credit usage.
• Code app compounding: Because running custom JavaScript or Python consumes 2 credits per second, inefficient code loops or network wait times inside scripts can rapidly exhaust monthly credit allowances.
• Log retention caps: Debugging historical errors is limited to 7 days on entry tiers and 30 days on standard paid plans, with 60 days reserved for enterprise tiers.

Who Each Option Suits Best

Freelancers and Solopreneurs

Freelancers handling straightforward, lightweight administrative tasks—such as forwarding lead forms to a CRM or syncing calendar bookings—can often start on the free tier if 2 active scenarios and a 15-minute polling interval suffice. However, anyone requiring near-real-time triggers (1-minute intervals) or running multiple client automations will need to upgrade to a standard paid tier with unlimited active scenarios.

Small Teams and Agencies

Small teams benefit significantly from Make’s non-seat-based pricing. An entire agency can use Private Spaces and role-based permissions without multiplying monthly seat costs. For businesses handling client documents, invoices, and webhooks, the 100 MB to 250 MB file limits and 40-minute execution windows provide sufficient headroom for multi-step automations.

Scale-ups and High-Volume Organizations

Organizations managing high-throughput data pipelines, internal microservices, or complex ERP connections (such as SAP via on-prem agents) require upper-tier allowances. These environments benefit from priority scenario execution to avoid queuing during peak usage, expanded API rate limits (up to 1,000 calls per minute), and dedicated 60-day audit and execution logs for compliance.

Next Steps

To choose the most cost-effective configuration for your organization:

• Audit your scenario frequency: Determine whether your workflows require 1-minute scheduling or if standard intervals are adequate.
• Calculate payload sizes: Identify the largest files passing through your webhooks to ensure you do not breach the 5 MB, 100 MB, or 250 MB payload ceilings.
• Estimate script runtimes: Check how many seconds your custom JavaScript or Python scripts run, factoring in the 2 credits per second consumption rate.
• Review official package rates: Check the current base pricing and credit volume tiers directly on Make’s pricing page, and consider annual billing if your workflow demand fluctuates across months.

Sources and further reading

Research checked 2026-09-21. Product details can change.

• Pricing & Subscription Packages