Quotas and limits
Defaults
| Limit | Default | Who can change it |
|---|---|---|
| Storage per project | 5 GB | Org Admins |
| Size per file | 50 MB | Org Admins |
| Signed URL lifetime | 1 hour (at most 7 days) | Set per link |
| Object path | 1,024 characters; 255 per segment | Fixed |
| Listing page | 1,000 entries per folder page by default | Per request (limit) |
Org Admins change the quota and per-file limit on the project's Storage page under Quota, or with PUT /api/projects/:name/storage/limits.
When a project is over quota, uploads fail with STORAGE_QUOTA_EXCEEDED and a fix: delete files or ask IT to raise the quota. Limits are checked against the declared size before the upload starts and again while streaming.
Concurrent uploads can overshoot the quota by at most the sizes in flight; usage is re-measured regularly and corrects any drift.
Allowed file types
The storage service checks a file's first bytes as well as its name and declared content type. For binary formats the bytes win: a PDF sent as image/png is stored as a PDF, and a file that claims to be an image or PDF without the matching signature is refused. Text files keep a declared text type, else text/plain.
| Allowed | Refused |
|---|---|
Images (PNG, JPEG, GIF, WebP, AVIF, HEIC), PDF, plain text, CSV, Markdown, JSON, Office documents (Word, Excel, PowerPoint, including legacy .doc/.xls), zip, gzip, MP3, MP4 | HTML, SVG, XML, scripts, executables, and anything else not on the allowlist |
Files are served from your app's own origin, so types a browser could execute are refused. Your installation's administrators can narrow the allowlist further.
Object paths
Paths are relative and /-separated. They may not start with /, contain empty segments (//), . or .. segments, backslashes, control characters, or encoded dots and slashes. A path that would need normalising is refused rather than rewritten, so a/../b can never reach another person's folder.
Usage and cost
Storage bytes are measured per project and appear:
- on the project's Storage page, as a usage bar with a monthly estimate,
- in Admin › Cost, as part of each project's cost,
- in Admin › Org, rolled up the org tree.
Usage is re-measured every 10 minutes, and uploads and deletes move the counters in between.
On the local stack the storage price is a synthetic rate chosen so demo files are visible in cost reports. On Azure, cost comes from Azure Cost Management for the project's tagged resources; that driver is coming soon.