Page Capacity¶
SecondPage has one user-facing object: a Page.
Some Pages are simple single-file artifacts. Others include many files, nested routes, fonts, images, scripts, and shared assets. You do not need to choose a separate product or Page type. Create or update the Page, and SecondPage chooses the right upload path.
What Changes For Bigger Pages¶
For ordinary Pages, the agent can send the files inline while creating or updating the Page.
For Pages with more files or more bytes, SecondPage may return an upload continuation. The agent uploads only the files SecondPage asks for, then finishes the same Page create or update. Reused assets do not need to upload again when their file hash has not changed.
The result is still a normal Page:
- same Pages library
- same sharing and visibility controls
- same comments and review flow
- same Page activity and version history
- same public URL behavior
Included Capacity¶
Per-publish limits (files, routes, total size, and max file size) are hard limits by plan, checked on every publish.
| Plan | Files per publish | Routes per publish | Total publish size | Max file size | Versions retained per Page |
|---|---|---|---|---|---|
| Starter | 250 | 25 | 50 MB | 10 MB | 50 |
| Pro | 2,000 | 500 | 1 GB | 100 MB | 100 |
| Custom | 5,000 | 1,000 | 2 GB | 250 MB | Unlimited |
If a Page crosses a plan limit, the publish stops with a plain-language upgrade message such as: "This Page is over the Starter size limit. Upgrade to Pro for larger Pages."
Storage¶
Storage works differently by plan and is not a simple included allowance:
- Starter has a combined 1 GB storage target across published Page bundles and uploaded media, plus 30-day Page availability. A background cleanup sweep trims the organization's oldest, past-availability content back toward that target if storage drifts above it. There is a hard upload ceiling well above the target as an abuse guard; hitting it is not expected in normal use.
- Pro and Custom are pay-as-you-go. Storage is metered from the first byte against your usage credits, with no included allowance to run out of. Your monthly usage budget, not a storage cap, is the practical stop. A high abuse-ceiling guard exists in the background but should not bind for normal usage.
See Plans And Billing for usage budgets and billing actions.
Warnings That Can Still Publish¶
Some Pages are valid but may be inefficient. SecondPage can publish them while returning a warning, such as:
- many separate files
- many assets needed by one route
- an organization on Starter getting close to its storage target, or a Pro or Custom organization approaching its monthly usage budget
When you see one of these warnings, the Page is live, but it may be worth combining assets, removing unused files, or upgrading capacity before it becomes a recurring pattern.
Good Habits¶
- Keep file paths relative and stable.
- Include every file the Page references.
- Reuse the same Page when revising existing work.
- Avoid thousands of tiny generated files when a smaller asset shape would load the same way.
- Use the media upload flow for original video files or large media that should be managed separately from the Page bundle.