Limits

Every published plan limit for document size, artifacts, storage, versions, projects, project links, publish rate, and retention.

In short

All limits are published here rather than discovered at publish time. Hitting one returns an explicit error naming the limit and the plan it belongs to.

How limits behave

Limits are enforced at publish time. A document over the size cap returns a 413; a plan restriction such as private visibility or permanent retention on Builder returns a 403 naming the plan; exceeding the publish rate returns a rate limit error with retry headers.

Nothing is silently truncated. If a publish succeeds, the artifact holds exactly the document you sent.

Which limit bites first

For most people it is retention, not size. Builder's three-day window is the setting that surprises teams who expected a link to persist.

For data and QA teams it is usually document size, and embedded base64 images are almost always the cause. Compressing images or switching plots to vector output is the normal fix.

Every limit

BinHTML plan limits by plan
LimitBuilderPro
Publishing
HTML file size10 MB50 MB
Publish rate10 per minute60 per minute
Active artifacts2505,000
Versions per artifact25200
Active storage2 GB100 GB
Projects and sharing
Projects50500
Active project links10 active500 active
Artifacts per project link25250
Project publish batch25 MB200 MB
Retention and access
RetentionUp to 3 daysPermanent or custom expiry
VisibilityUnlistedUnlisted and private

Related