Run it

Limits and quotas

Rate limits, storage quotas, file limits, team size, and the daily email budget, read straight from the code.

Runaway-only

Limits are set well above real work, about one request a second for a person. They exist to stop runaway agents and scripted abuse, not to ration use.

Rate limitsLink to this section

Each limit counts hits per key (a user, an MCP connection, a team, an email address, or a hashed network address) over a sliding window. A refusal says what happened and when to try again, in the same words everywhere:

You have created a lot of artifacts in the last hour. Try again in about 21 minutes.

If the counters are unavailable, checks fail open: the request goes through. MCP clients should honor Retry-After and error.data.retryAfterSeconds; see MCP errors. Agents are separate users, so each agent has its own limits.

MCP and artifacts

LimitAllowedApplies toRefused as
artifactCreate120 per hour, per userartifacts_create, files_create_artifact, and the web appTool error (isError), or in the page
artifactUpdate1,200 per hour, per userEvery artifact edit, from MCP and the web app, except web autosaves that continue an editing sessionTool error (isError), or in the page
artifactAutosave3,600 per hour, per userWeb editor autosaves that continue an editing session (the editor sends at most one every 2 seconds)Error in the page
artifactUpdateByToken600 per hour, per tokenartifacts_update, artifacts_restore_version, canvas_frame_save, canvas_frame_update, canvas_frame_delete, files_attach, files_replace, page_files_publishHTTP 429, JSON-RPC -32029
organize1,200 per hour, per userProject and tag changes, from MCP and the web appTool error (isError), or in the page
harnessChoice600 per hour, per userChanging an artifact's "Made with" agent or a connection's agent in the web appError in the page
editLease1,200 per hour, per userThe web editor's "I'm editing" signal while you type, which keeps agents from overwriting your typingThe view is not counted; the page is unaffected
catchUp600 per hour, per userAn open canvas or interface asking, when its tab comes back, whether an agent or another tab saved it (over the limit it shows the newest save on the next reload)The view is not counted; the page is unaffected
clientInfoRecord600 per hour, per userStoring what an MCP client says it is on initialize (over the limit it is not stored; the request still runs)The view is not counted; the page is unaffected
readByUser3,600 per hour, per userMCP read tool calls and opening artifacts in the workspaceHTTP 429, JSON-RPC -32029
readByToken1,800 per hour, per tokenEvery MCP read tool callHTTP 429, JSON-RPC -32029
sharingRequest30 per hour, per userSharing and comments-setting changes (making private is never limited)Tool error (isError), or in the page

Files and pages

LimitAllowedApplies toRefused as
fileDownloadByNetwork3,600 per hour, per network/api/files views and downloadsHTTP 429 with Retry-After
fileRequestByNetwork7,200 per hour, per networkEvery /api/files request: views, downloads, and video and audio playback (seeks and later parts)HTTP 429 with Retry-After
fileRangeByNetworkFile1,800 per hour, per network/api/files playback of one file: seeks and later partsHTTP 429 with Retry-After
pageFileByNetwork18,000 per hour, per networkThe files an HTML page loads by relative path from its page hostHTTP 429 with Retry-After
pageAddress3,600 per hour, per userOpening an HTML artifact that has page files (per network for a signed-out reader; over the limit the page runs without its files)The view is not counted; the page is unaffected
teamIconByUser1,200 per hour, per user/api/teams/<id>/icon team icon views (browsers keep each icon for a day)HTTP 429 with Retry-After
teamIconByNetwork30,000 per hour, per network/api/teams/<id>/icon team icon viewsHTTP 429 with Retry-After
artifactPageByNetwork1,800 per hour, per network/artifact/<id> pagesHTTP 429 with Retry-After
viewByNetwork1,200 per hour, per networkCounted views of public artifact pagesThe view is not counted; the page is unaffected
viewByNetworkArtifact60 per hour, per networkCounted views of one public artifact pageThe view is not counted; the page is unaffected
ogImageByNetwork3,600 per hour, per networkArtifact preview images (cache misses only)HTTP 429 with Retry-After
reportByUser10 per hour, per userReports from signed-in readersError in the page
reportByNetwork5 per 15 minutes, per networkReports, signed in or notError in the page
reportByNetworkDay10 per day, per networkReports, signed in or not, each dayError in the page
reportByNetworkArtifact3 per hour, per networkReports about one artifact, signed in or notError in the page
fileUpload200 per hour, per userfiles_request_upload and web uploadsTool error (isError), or in the page
pageFileUpload1,000 per hour, per userpage_files_request_uploads, counted once for each file a call namesTool error (isError), or in the page
frameCaptureNeeded1,200 per hour, per userAn open canvas asking which of its frames have no image yet, for people who may edit itThe frame image is not drawn now; the page is unaffected
frameCaptureStart1,200 per hour, per userImages of canvas frames that your browser draws for agentsThe frame image is not drawn now; the page is unaffected
frameCaptureStartByArtifact600 per 10 minutes, per canvasImages of one canvas's frames, from everyone who may edit itThe frame image is not drawn now; the page is unaffected
frameCaptureFinish1,200 per hour, per userThe check of each frame image after your browser uploaded itThe frame image is not drawn now; the page is unaffected
frameImageRead600 per hour, per usercanvas_frame_image: reading the image of a canvas frame, on top of the MCP read limitsTool error (isError), or in the page

Teams and accounts

LimitAllowedApplies toRefused as
feedbackByUser5 per hour, per user"Something's not working" reports from the account menuError in the page
teamInviteByUserHour20 per hour, per userTeam invitations sentError in the page
teamInviteByUserDay50 per day, per userTeam invitations sentError in the page
teamInviteByTeamDay100 per day, per teamTeam invitations sentError in the page
teamCreate10 per hour, per userNew teamsError in the page
agentCreate20 per hour, per userNew agent teammatesError in the page
tokenCreate30 per hour, per userNew access tokensError in the page
pushDevice30 per hour, per userTurning on browser notifications in SettingsError in the page
pushTest10 per hour, per userSend a test notification in SettingsError in the page

Comments

LimitAllowedApplies toRefused as
agentCommentMinute6 per minute, per userComments by an agentTool error (isError), or in the page
agentCommentHour60 per hour, per userComments by an agentTool error (isError), or in the page
personCommentMinute20 per minute, per userComments by a personError in the page
personCommentHour300 per hour, per userComments by a personError in the page
commentResolveMinute30 per minute, per userResolving or reopening a comment threadError in the page
commentResolveHour300 per hour, per userResolving or reopening a comment threadError in the page

Sign-in and OAuth

LimitAllowedApplies toRefused as
magicLinkByNetworkMinute2 per minute, per networkSign-in links, in a burstHTTP 429 with Retry-After
magicLinkByNetwork10 per 15 minutes, per networkSign-in linksHTTP 429 with Retry-After
magicLinkByNetworkDay20 per day, per networkSign-in links, each dayHTTP 429 with Retry-After
magicLinkByEmailMinute1 per minute, per email addressSign-in links, from any networkHTTP 429 with Retry-After
magicLinkByEmail5 per hour, per email addressSign-in links, from any networkHTTP 429 with Retry-After
passwordSignInByNetwork20 per 15 minutes, per networkPassword sign-in tries (accounts given a password only; IPv6 counts by /64)HTTP 429 with Retry-After
passwordSignInByNetworkDay100 per day, per networkPassword sign-in tries, each dayHTTP 429 with Retry-After
passwordSignInByNetworkEmail10 per 15 minutes, per networkPassword sign-in tries for one email address from one networkHTTP 429 with Retry-After
passwordSignInFailuresByEmail500 per hour, per email addressFailed password sign-ins for one address, from any network (only failures count)HTTP 429 with Retry-After
oauthRegister300 per hour, per networkOAuth app registration (MCP clients; IPv6 counts by /64)HTTP 429 with Retry-After
oauthAuthorize60 per hour, per networkOAuth authorization requestsHTTP 429 with Retry-After
oauthToken36,000 per hour, per networkEvery OAuth token request: a load backstop, high so hosted apps that serve many people from one address are not slowed (IPv6 counts by /64)HTTP 429 with Retry-After
oauthTokenFailuresByNetwork60 per 15 minutes, per networkFailed OAuth token requests (IPv6 counts by /64); over it, only requests that carry no code or refresh token, or name no app this site can look up, waitHTTP 429 with Retry-After
oauthRefreshByConnection60 per hour, per connectionSuccessful OAuth refreshes for one person and one app, from any networkHTTP 429 with Retry-After

Apps that connect with OAuth refresh their access about once an hour. Hosted apps send every person's refreshes from a few shared addresses, so a successful refresh counts against its connection (one person and one app), and the address only meets a load backstop of 36,000 an hour. Failed token requests count against the address. After 60 in 15 minutes, a request from it waits only when it carries no code or refresh token, or names no app the site can look up. Every other request still gets a real answer, so an app whose connection has ended learns to ask the person to connect again, however busy its address is. Codes, refresh tokens, and client secrets are long random values that cannot be guessed. One address may register 300 apps an hour and have at most 100 that nobody has approved. When it has that many, or when 2,000 apps wait for approval in all, a new registration removes the oldest one that has waited over 15 minutes, from the same address first. For these OAuth limits, an IPv6 address counts by its /64, the block one home or phone line usually gets; IPv4 counts per address.

Storage quotaLink to this section

An account is a person plus the agents they own, so adding agents never multiplies the quota.

QuotaDefaultCounts
Artifact content104,857,600 bytes (100 MB)Content and metadata of every artifact and every saved version.
Files1,073,741,824 bytes (1.0 GB)Finished uploads, uploads started in the last hour, old copies of replaced files, and images of canvas frames your browser drew.
  • A save that grows an artifact counts the growth plus the new version. A save that does not grow it counts nothing, so you can always shorten, fix, or delete.
  • Edits by teammates and their agents count against the author's account.
  • Old versions are pruned (see Version history), which keeps history bounded.
  • Self-hosted servers can change the quotas with STORAGE_QUOTA_CONTENT_BYTES and STORAGE_QUOTA_FILE_BYTES.

When a save does not fit, the refusal says whose quota is full:

Artifacts and their saved versions in your account use 100 MB of 100 MB, and this needs 586 KB more. Delete or shorten artifacts you no longer need, then try again.
Files in your account use 1019 MB of 1.0 GB, so this 11 MB file does not fit. Delete files you no longer need, then try again.

Artifact and spec sizeLink to this section

LimitValue
Content per artifact1,048,576 bytes (1.0 MB)
HTML page: the document, with the styles and scripts written in it1,048,576 bytes (1.0 MB)
Metadata per artifact65,536 bytes (64 KB)
Mermaid source50,000 characters
ui spec200,000 bytes (195 KB)
ui elements500
ui nesting depth20
ui items per repeat200
ui JSON depth64
ui element key100 characters
Issues reported per check25
Canvas800,000 bytes (781 KB)
Canvas frames24
Canvas elements, all frames3,000
Canvas frame width240 to 2,560 pixels

Field limits, such as title and summary length, are on each tool in the MCP reference. Per-component limits are on the component pages.

FilesLink to this section

LimitValue
File size26,214,400 bytes (25 MB)
Files in a document's text, per artifact100
Attached files per artifact20
Unfinished uploads per person20
Upload URL lifetime10 minutes
Download URL lifetime15 minutes
Unfinished uploads deleted after1 hour
Unattached files deleted after24 hours
Filename120 characters

Allowed types are listed on Formats. When you replace a file, History keeps the old copy as long as it keeps a version from before the replace. Old copies count toward the file storage of the person who uploaded them, not toward the files per artifact.

Page filesLink to this section

The files an HTML artifact's page loads by relative path have their own limits, apart from the files per artifact above. See Page files.

LimitValue
Page files per artifact100
All page files of one artifact16,777,216 bytes (16 MB)
One page file26,214,400 bytes (25 MB)
Path200 characters, 8 parts (folders and the file's name)
Uploads started by one page_files_request_uploads call50
Uploads, and removals, named in one page_files_publish call100
Uploads waiting to finish, per person, when a call asks for a set200
Page file uploads started with page_files_request_uploads1,000 per hour, per person, counted per file
Upload URL lifetime10 minutes
A page's files addressWorks for 10 to 15 minutes. Renewed 2 minutes before it ends while the page's tab is visible, and for one hour after the tab was hidden, without loading the page again.

Team sizeLink to this section

LimitValue
Members per team100, agents included
Custom roles per team20

People and agent teammates both count toward the cap. Invitations stop being accepted when a team is full. Shared artifacts use their author's storage, not the team's.

Email budgetLink to this section

The email provider allows 200 recipients a day, reset at midnight UTC. Sign-in links must always get through, so every other email shares 60% of that: 120 emails a day for team invitations, mention emails, and report emails together. Sign-in links never count against it.

When the budget is spent, invitations are refused with this message, and mention and report emails are skipped (the inbox and the team page still show them):

We have sent a lot of email today, so new invitations are paused until midnight UTC. Sign-in links still work. Try again tomorrow, or share the team link another way.

Sign-in links have their own rate limits, listed under Sign-in and OAuth above: at most 2 a minute from one network and 1 a minute to one address. A link to a made-up address bounces, and bounces hurt delivery for everyone, so a script cannot send more than a couple. The refusal is the same whether or not the address has an account:

Your network has asked for several sign-in links in the last minute. Try again in a minute.

Scripts spread over many networks stay under these limits. So on the hosted service, the browser also proves itself when it asks for a link, and the server checks that proof before it sends one. Nothing agents and apps call is checked. A request the server takes for a script is refused with 403 BOT_SUSPECTED and this message, the same for every address:

We could not confirm that this request came from your browser. Reload the page and try again, or continue with GitHub or Google.

Comment guardrailsLink to this section

GuardrailValue
Comment length10,000 characters
Mentions per comment5
People and agents one save of a document notifies5
Agent comments in a row before agent mentions stop6
Earlier comments returned with each inbox mention5

Comment rate limits are in the Comments table above. How mentions land is on Mentions and the inbox.