How it works
Limits
Sizes, rates and storage, and what happens when you meet one.
Per document
- Without an account
- 5 MB, and it expires in thirty days unless claimed.
- Signed in
- 50 MB.
Per workspace
- Free
- 250 MB in total, counting every version of everything.
- Team
- 5 GB — the tier exists in the code and there is no way onto it yet, because there is nothing to pay for during the beta.
- Publishing rate
- Unlimited signed in. Ten an hour from one network without an account.
Every version counts towards storage, because every version is kept — that is the promise, and it is also what fills the disk. Your current usage is on the settings page.
Meeting a limit refuses the publish with a sentence saying what to do, rather than failing quietly. If you need more, ask.
What published documents may do
- External libraries load
- Scripts, stylesheets, fonts and images may come from another host, so a document can reach for a charting library or a web font. Inline styles, inline scripts and inline SVG all work too.
- Sandboxed, whatever it loads
- The document runs on an opaque origin from a cookie-free domain. It cannot read your account, call the API as you, or reach any other document — and neither can anything it loads, because those run in the same sandbox.
- No calls out
- fetch and XHR reach only the content origin, so a document cannot post what it holds to somewhere else. A script it loads can still read the page it is in, which is the trade for letting libraries work at all.