Resistance ToolsLimits are enforced by the backend and can also depend on shared capacity or live network state. The figures below describe the current implementation; a live validation error is authoritative for your request.
Upload limits
| Resource | Current limit |
|---|---|
| Static website upload | 50 MiB and 10,000 files |
| Storage Bag creation | 25 files; 400 MiB per file and per request/Bag |
| Platform Storage per wallet | 1 GiB |
| Template image | 8 MiB; PNG, JPEG, GIF or WebP |
| Template media per wallet | 200 MiB |
| New paid providers per operation | 5 |
Archive path and expansion checks also apply. JSON/base64 transport has overhead; a request body limit can be reached before the decoded file limit.
Costs
Static publication is free. Wallet transactions still require the network fees and amounts shown by the live preparation and wallet. Buying names, bidding, minting priced labels and funding independent Storage providers are separate from free publication.
The current amount is shown during preparation and in your wallet.
Product boundaries
Published sites are static. Server applications, database hosting and a general push-to-deploy CI service are not part of the current product.
The Web and Mini App offer different controls. Use the Mini App for multi-domain management and Webdom trading.
Retention and freshness
Platform-hosted sites retain a bounded set of releases rather than unlimited history. DNS and provider indexes can lag finalized state. Temporary download links expire. Keep your source files and important backups independently.
For an operation that appears stuck, see troubleshooting.