Skip to main content
Some of these limits reject and some truncate. A rejection surfaces at publish; a truncation is silent at render.

Bundle

Enforced twice, once while reading the archive and again on the extracted set. All of these reject the publish and name the file.
Per-plan bundle sizes appear in some pricing material. They are not enforced. Every plan gets the same 50 MiB ceiling today.

Path rules

A path must be non-empty and at most 300 characters, must not be absolute, contain a backslash, contain // or end in /, must have no segment that is empty, ., .. or starts with ~, and must be printable ASCII or spaces only. Anything under a dot-directory is dropped before the rules are applied, so .git, .github and .gitignore never reach a bundle.

Per store

Hitting the plan cap returns a payment-required error naming the plan:

Sections and blocks

The 200-blocks-per-type ceiling applies when the schema declares no max, and it truncates without a message. A merchant who adds 250 blocks sees 200 render and no error. Declare an explicit max.

Render

These come from Slurp and apply to every render. See Limits for detail. A section that exceeds its budget fails the whole page rather than disappearing from it. A page silently missing one section is diagnosed as a content problem.

Publish

Exceeding the parse budget produces:

Propagation

Store configuration is cached, so a published theme becomes visible to buyers within about 60 seconds. The builder preview is uncached and updates immediately. For the first minute after a publish, the preview reflecting a change the live store does not is expected.