Usage Limits & Quotas
Every resource quota a plan sets, whether it's tracked per workspace, per site, or across your whole account, and what happens when you reach one.
Every plan sets quotas — numeric ceilings on how much you can create or use. Quotas aren't all tracked the same way: most are shared across a single workspace, some are scoped to an individual site, and a couple are pooled across every workspace the same owner has.
This page lists every quota and its real scope. For which plan includes which limit, the Compare Plans page is always the source of truth — and for your actual, live usage, see Checking Your Real Usage below.
Scope matters. A workspace-level quota like Workspace members is shared by everyone in that workspace. A site-level quota like Pages per site resets the count for every new site. And an account-level quota like Workspaces or AI credits / month is shared across every workspace the same owner has — see Plans & Billing Overview for why.
Quota Types
Account & Workspace Quotas
Tracked once per owner account, or shared across everyone in a single workspace.
| Quota | What it counts | Scope |
|---|---|---|
| Workspaces | How many workspaces the account owns. | Account-wide (every workspace the owner has). |
| Sites per workspace | Active, unlocked sites in the workspace. | Per workspace. |
| Workspace members | People who belong to the workspace. | Per workspace. |
| Asset storage (MB) | Total size of uploaded images and files across the workspace's sites. | Per workspace. |
| Bandwidth (GB/month) | Monthly data transfer served to visitors. Resets each billing cycle. | Per workspace. |
| Blog posts | Non-archived blog posts across every site in the workspace. | Per workspace (not per site). |
| CMS collections | Data collections across every site in the workspace. | Per workspace (not per site). |
| AI credits / month | Monthly AI credit allowance, plus any purchased top-ups. Resets each billing cycle. | Account-wide (pooled across every workspace the owner has). |
| Apps installed workspace-wide | Apps installed at the workspace level (not tied to one site). | Per workspace. |
| Version history (days) | How long published-version backups are retained. Not a count — a retention window enforced independently of quota checks. | Per workspace. |
Site Quotas
Tracked separately for each site (or, for form submissions, for each form).
| Quota | What it counts |
|---|---|
| Pages per site | Maximum pages on that site. |
| Forms per site | Forms built on that site. |
| Form submissions / month (per form) | Submissions each individual form on that site can receive per calendar month. Every form has its own allowance, so one busy form never uses up another form's submissions. |
| CMS items per collection | Records inside a single collection. |
| Custom domains per site | Primary custom domains connected to that site. |
| Custom scripts per site | Non-empty header + footer custom script entries on that site. |
| Dynamic API blocks per site | Dynamic, API-powered blocks on that site. |
| Apps installed per site | Apps installed directly on that site. |
Role Seat Quotas
Separate caps on how many people can hold each role, on top of the overall member/collaborator counts above.
| Quota | Scope |
|---|---|
| Workspace Admin users | Per workspace. |
| Workspace Member users | Per workspace. |
| Workspace Viewer users | Per workspace. |
| Site Manager users per site | Per site. Site Admins count toward this cap too. |
| Site Designer users per site | Per site. |
| Site Viewer users per site | Per site. |
Role seat quotas stack with the general Workspace members cap — inviting someone as a Site Manager counts against both that site's Site Manager seat limit and the workspace's overall member limit.
Example: How Limits Scale Across Tiers
The table below is an example only — it shows the general shape of how limits grow from lower to higher tiers. The actual plans, their names, and their exact numbers are configured by the platform and shown on the Compare Plans page.
| Quota | Free | Lower tier | Mid tier | Higher tier |
|---|---|---|---|---|
| Sites | 1 | 10 | 50 | Unlimited |
| Pages / site | 5 | 25 | 100 | Unlimited |
| Members | 1 | 5 | 25 | Unlimited |
| Asset storage | 100 MB | 2 GB | 20 GB | Custom |
| Bandwidth / mo | 5 GB | 50 GB | 500 GB | Custom |
| Submissions / mo | 100 | 2,000 | 20,000 | Custom |
| Dynamic API blocks / site | — | 5 | 25 | Unlimited |
These figures are illustrative placeholders, not your real limits. To see the actual numbers, open Compare Plans, check your current active plan, and click View detailed limits on its card (or Compare all limits & features for a full side-by-side table).
Checking Your Real Usage
The Plan Usage tab (on the Plans & Billing page, under Billing & Plan) is the real, live view of where you stand:
- At the top: your account-wide Workspaces count and AI credits (all workspaces) balance — including any purchased top-ups — against their limits.
- Per workspace: Sites usage plus every other workspace-level quota.
- Per site, nested under its workspace: Pages usage (with a Locked badge if the site is currently over its plan's site limit) plus that site's other quotas.
This is the most accurate place to check usage — it reflects live counts, not the illustrative numbers on the Compare Plans cards.
How Usage Is Counted
- Shared within its scope, not per member. A workspace-level quota is drawn from by every member of that workspace; one person creating a site reduces the remaining allowance for everyone else in it. Account-wide quotas (Workspaces, AI credits) are shared the same way across every workspace the same owner has.
- Time-based quotas reset monthly. Bandwidth and AI credits reset at the start of each billing cycle, and form submissions (counted per form) reset at the start of each calendar month.
- Cumulative quotas don't reset. Counts like sites, pages, stored assets, blog posts, and role seats reflect what currently exists — freeing items (deleting a site, removing an asset, archiving a blog post) returns capacity immediately.
- Version history is different from the rest. It isn't something you can "use up" — it's a retention window for how far back you can restore a page's version history, enforced independently of the quota checks above.
Reaching a Limit
Most quotas are enforced reactively: you attempt the action, and if it would exceed your plan's limit, the request is rejected and a "Limit reached" notice appears explaining which quota you hit, with an Upgrade plan link. The trigger button itself (e.g. + New Site, + New Form) usually isn't disabled ahead of time — you find out when you try.
Custom scripts are an exception: the Custom Scripts panel checks your quota proactively and pre-disables its Add script control (with a quota badge) once you're at the cap, rather than waiting for you to try and fail.
Either way, existing content is never removed for exceeding a limit — you simply can't create more in that category until you:
- Upgrade to a plan with a higher quota — capacity increases immediately (or at renewal, for a scheduled upgrade).
- Free up usage — delete or archive items you no longer need. This works for cumulative quotas like sites, pages, and storage.
Quotas are also enforced server-side before a create operation completes. If you script against the REST API, expect create requests to be rejected once a workspace is at its limit — handle that case in your integration.
Related
- Feature Access — On/off feature gating, separate from these numeric quotas.
- Subscription Management — Upgrade to raise your limits.
- Plans & Billing Overview — Why some quotas are shared across every workspace you own.
- Plans & Billing — Where to buy extra AI credits and see your usage history.