Make.com Free Plan Limits (2026): 1,000 Credits & 2 Scenarios
Can your Gmail PDF workflow stay on Make's Free plan? Check the limits that can stop it: monthly credits, active scenarios, scheduling and the size of each file. Start with the task you need, then decide whether a paid plan solves a real constraint.
$0, 1,000 monthly credits, 2 active scenarios, a 15-minute minimum scheduled interval and a 5 MB maximum file size.
Which limits matter for Gmail PDF workflows?
| Free-plan limit | Allowance | What to check |
|---|---|---|
| Monthly credits | 1,000 | Usage in scenario history, including checks and processing |
| Active scenarios | 2 | How many separate workflows must stay switched on |
| Scheduled interval | 15 minutes minimum | Whether a scheduled delay is acceptable |
| Maximum file size | 5 MB | The size of each attachment, not just the email count |
These are published plan limits, not limits we reached in a stress test. A successful test with a small PDF does not prove that a larger scan will fit.
What counts as a credit?
A module run can check for data or process data. Many standard operations consume one credit, but bundles, module type and AI features can change the total. A trigger can return several bundles in one check while downstream actions run separately for each bundle. Count actual usage, not the number of boxes in the scenario.
How much can 1,000 credits handle?
Do not treat the allowance as a guaranteed number of saved PDFs. First run representative examples, then inspect both operations and credits in scenario history. Include checks with no matching email, multiple attachments and any retries when estimating regular use.
Estimate scheduled checks and Gmail processing with our free Make credit calculator →
- Test a representative PDF and inspect each module's usage.
- Repeat with multiple attachments and an email your filter rejects.
- Observe scheduled checks as well as successful uploads.
- Estimate your month from that measured usage, then leave room for variation.
This is a suggested measurement procedure. We are not reporting a new monthly-volume test.
What you can test with the existing guides
- Gmail attachment archiving
- PDF-only filters
- Specific-sender invoice filters
- Date-based filenames and folder routing
Which limit matters for your workflow?
For larger scanned PDFs, check file size first. For several independent automations, check active scenarios. For time-sensitive archiving, check the scheduled delay. Credit usage is a separate constraint: a workflow can fit the file-size limit and still exhaust its allowance.
When a paid plan makes sense
Stay on Free while the workflow fits. If a limit blocks the task, compare that specific limit with the paid offer available to your account. Our Free vs Core decision guide explains the upgrade checks, and our pricing guide explains billing and credits.
Current paid starting point: Make's official pricing page displayed Core at $12 per month for 10,000 credits with monthly billing on September 9, 2026. Core adds unlimited active scenarios, 1-minute scheduling and a 100 MB maximum file size. Annual billing may show a lower monthly equivalent; confirm the billing period and checkout total before purchasing.
Test before you pay
If the Free plan covers your test workflow, start there. Upgrade only when a specific limit blocks the workflow.
Make link is an affiliate link.
Try Make with the Free plan
Build one real workflow first, then decide whether your usage justifies a paid plan.
Affiliate disclosure: the Make link is an affiliate link. We may earn a commission if you later become a paying customer, at no additional cost to you.
Related guides
- Make pricing explained
- Make credit calculator for Gmail automation
- Make Free vs Core: when to upgrade
- Make.com hands-on review
- Build a Gmail automation on Make
Sources and verification
- Make official pricing and Free-plan limits — checked September 9, 2026; monthly prices use the 10,000-credit selection.
- Make Help Center: operations and bundles
- Make Help Center: changing plans and billing cycles
Published specifications are not stress-test results. Our existing workflow examples remain the tests described in their individual guides.