The short version
Make documents its limits in several places, and they work in two different ways. File size is a fixed number per plan. Data storage, incomplete-execution storage, data transfer and webhook queue size scale with the credits you license each month, so two people on the same plan can have different limits. [1] [2]
Three limits depend on your plan but are not given as numbers in Make's help center: the scenario run duration limit, the minimum scheduling interval and how many days run history is kept. The help pages for each one point to the pricing page. [5] [6] [7] Check those three on your own plan before you design a scenario that relies on long runs, fast polling or old logs.
File size by plan
This is the only limit in this guide that changes with the plan name rather than the credit count. It applies to any file a module handles, such as an email attachment, a downloaded PDF or an image passed to cloud storage. [1]
| Plan | Maximum file size |
|---|---|
| Free | 5 MB |
| Core | 100 MB |
| Pro | 250 MB |
| Teams | 500 MB |
| Enterprise | 1,000 MB |
Limits that scale with your credits
Make's pricing page lists a usage allowance per 10,000 licensed credits a month. [2] The Free plan is the exception for storage: it gets 1 MB and one data store. [2] [3]
| Allowance | Per 10,000 credits a month | Ceiling | Example at 40,000 credits |
|---|---|---|---|
| Data transfer | 5 GB | Not stated | 20 GB |
| Data storage (data stores) | 10 MB | Not stated | 40 MB |
| Incomplete executions storage | 10 MB | 2 GB | 40 MB |
| Webhook queue, per webhook | 667 items | 10,000 items | 2,668 items |
Fixed limits that apply on every plan
These numbers do not change with credits. They are the ones most likely to surprise you during a spike or a migration.
| Limit | Value | Source |
|---|---|---|
| Data stores per organization | Up to 1,000, regardless of plan | [3] |
| Minimum size of one data store | 1 MB | [3] |
| Maximum size of one data store record | 15 MB | [3] |
| Incoming webhook rate | 300 requests per 10 seconds; extra requests get HTTP 429 | [4] |
| Webhook log retention | 3 days; 30 days on Enterprise | [4] |
| Webhook not attached to any scenario | Deactivated after 5 days (120 hours); returns HTTP 410 | [4] |
| Sleep module delay | Up to 300 seconds | [8] |
| Default schedule for a new scenario | Every 15 minutes | [6] |
Symptom and cheapest workaround for each limit
Most limits fail quietly or with an error in another app, so it helps to know what each one looks like from the outside.
| Limit hit | What you see | Cheapest workaround |
|---|---|---|
| File too large | The module handles it according to the Enable data loss setting [1] | Pass a link to the file instead of the file itself, or compress or split it before Make touches it |
| Webhook queue full | The sender gets HTTP 400 with Queue is full, and that data never enters Make [4] | Run the webhook instantly instead of on a schedule, or raise Maximum number of results so each run clears more items |
| Webhook rate over 300 per 10 seconds | The sender gets HTTP 429 [4] | Ask the sender to retry with backoff, or batch events at the source |
| Incomplete executions storage full | Depending on the Enable data loss setting, Make either disables the scenario or discards the failed run data, which cannot be recovered [7] [10] | Resolve or delete old incomplete executions each week; more credits also raise the allowance |
| Data store storage used up | An out-of-space error when you create a new store [3] | Lower the Data storage size in MB of an existing store to free space, and delete records you no longer need |
| Run longer than the run duration limit | The run stops and no incomplete execution is saved [7] | Lower the Limit field on the trigger so each run processes fewer bundles, and let the schedule pick up the rest |
| Webhook logs expired | Nothing to inspect after 3 days [4] | Write the event ID, time and outcome to a data store or sheet in the scenario itself |
Worked example: a launch that overflows a scheduled webhook
Suppose you are on Core with 10,000 credits a month, and a form sends each sign-up to a Make webhook. To save credits you set the scenario to run every 15 minutes instead of immediately. Make holds scheduled webhook requests in the queue until the next run and then processes them according to Maximum number of results, which defaults to 2. [4]
Your queue allowance at 10,000 credits is 667 items. [2] [4] If a launch email sends 1,500 people to the form in an hour, about four scheduled runs clear only a handful of items while the queue fills. After 667 items, every further sign-up is rejected with Queue is full, and the form tool may or may not retry. [4]
The fix that costs nothing extra is to switch the webhook to run immediately. If you need to keep a schedule, raise Maximum number of results so each run drains the queue. Then check that each run finishes well inside the run duration limit for your plan. [4] [7]
What counts against credits while you work around limits
Workarounds can add modules, so check the credit cost. A trigger uses 1 credit each time it checks, even when it finds nothing new. Filters, routers and the error handlers Rollback, Break, Resume, Commit and Ignore use no credits. Most other modules use 1 credit per operation. [9]
A scheduled scenario that polls every 5 minutes makes 288 checks a day, and each check uses 1 credit, so the trigger alone uses 288 credits a day before any data is processed. [9] If you shorten an interval to get around a queue or rate problem, budget for that.
- Turn on Store incomplete executions before you need it, and keep the folder below its allowance. [10]
- Use bulk modules or aggregators to send several bundles in one request when an app rate-limits you. [8]
- Set Maximum runs to start per minute on instant scenarios to smooth spikes. [6]
- Keep your own log of important events, because webhook logs only last 3 days outside Enterprise. [4]
Watch demos / Official walkthroughs
See how the tools work.
Videos load from YouTube only when you press play. These are provider videos, not our own product tests.
Make / Official video
Make—Building Your First Automated Workflow from Scratch
What to look for: Follow how modules connect and how data moves through the first workflow.
Watch on YouTubeQuestions before you decide
What is the maximum file size in Make on each plan?
Make lists 5 MB on Free, 100 MB on Core, 250 MB on Pro, 500 MB on Teams and 1,000 MB on Enterprise. When a file is larger, Make follows the Enable data loss setting in Scenario settings.
How big can a Make webhook queue get?
Up to 667 items per webhook for every 10,000 credits licensed per month, with a hard cap of 10,000 items. Requests over the limit are rejected with HTTP 400 and the body Queue is full.
How much data store space do I get?
Divide your monthly credits by 1,000 to get megabytes: 10,000 credits gives 10 MB. The Free plan gets 1 MB, which is enough for one data store because each store needs at least 1 MB.
How long does Make keep webhook logs?
Make keeps webhook logs for 3 days, or 30 days on Enterprise. If you need a longer audit trail, write the key fields to a data store or a sheet yourself.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make Help: Working with files Accessed 30 Oct 2026
- Make pricing Accessed 30 Oct 2026
- Make Help: Data stores Accessed 30 Oct 2026
- Make Help: Webhooks Accessed 30 Oct 2026
- Make Help: Scenario history Accessed 30 Oct 2026
- Make Help: Schedule a scenario Accessed 30 Oct 2026
- Make Help: Errors that don't create incomplete executions Accessed 30 Oct 2026
- Make Help: Fix rate limit errors Accessed 30 Oct 2026
- Make Help: How features use credits Accessed 30 Oct 2026
- Make Help: Scenario settings Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.