Fair use
Usage limits
Figures in force on November 13, 2026
Free is meant to last: neither the number of files nor the use of MCP is limited. The only limits are on what really costs: renders, which run a browser on our servers, and image storage. They are published here rather than in the terms of use so they can follow real usage; a change that concerns you is announced by e-mail.
During the beta, nothing is limited. These figures will apply when Pro launches, in January 2027.
The figures
| Limit | Free | Pro |
|---|---|---|
| Renders per month | 300 per workspace; slowed down beyond, stopped at 900 (3× the quota) until the next month | 2,000 per editor, pooled in the workspace; never stopped or charged extra |
| Renders per hour | At most 100 per workspace | At most 100 per workspace |
| Images | 1 GB per workspace | 50 GB per workspace |
| Editors | 2 per workspace | Unlimited |
| Version history | The last 7 days shown; older versions are kept | The whole history |
| Team features | Company domain, new teams, audit log and “can edit” share links are Pro | Included |
| Pro trial | 14 days, no card, once per workspace and per account | – |
| Workspaces owned | 1 Free workspace per account | Unlimited: Pro workspaces don’t count |
| Inactivity | Workspace deleted after 12 months without activity, with a notice e-mail 30 days before | No deletion while the plan runs |
What counts as a render
Any MCP tool that runs a browser to look at a screen: get_screenshot,
compare_to_reference, inspect_reference and
check_layout. The other tools (creating or editing a screen, reading its
HTML, listing files, answering a comment…) are not counted.
Beyond a limit
- Free’s monthly quota: renders go on, behind those of paying workspaces. Past three times the quota, they are refused until the next month; your agent gets a clear message (“monthly quota reached, upgrade to Pro or try again later”) and passes it on to you.
- Pro’s monthly quota: renders are never stopped, nor charged extra past the quota; Settings › Billing shows the running count.
- Hourly cap: it stops scripts asking for renders in a loop, on every plan. Renders resume the next hour.
- Storage: once the limit is reached, new images are refused; those already there stay.
- Editors: on Free, beyond two editors, other people reach your files to view or comment, as guests or through a share link. A guest you allow to edit a file or a project counts as an editor.
What is never limited
- Viewers, commenters and agents, on every plan;
- Files, projects, prototypes, and share links to view or comment;
- MCP calls that are not renders.
Abnormal use (getting around the limits, creating workspaces in series, excessive automated requests) can lead us to slow down or suspend a Free workspace, as the terms of use provide. That decision is always made by a person, never automatically, and we write to you.
Plans and prices are on the pricing page.