Get Started
Capacity and Limits
ZeroPress builds a static site from Preview Data and a theme. Plan the build machine, search and hosting together: search indexes, archive pages and media can add substantial work and files beyond the number of posts.
Choose A Configuration
For a site similar to the reference profile below, use these planning examples:
| Your site | Suggested configuration |
|---|---|
| A small site, around 100 posts | Start with the standard theme and your chosen search setup. Native search is an option while its index remains small. |
| Around 1,000–5,000 posts | Pagefind is a useful starting point for static search. As your site grows, plan for a build environment with 8 GB of RAM. |
| Approaching 7,500 posts, with Pagefind | Check final file counts before relying on Cloudflare Workers Free. Leave space for new content, or plan a hosting upgrade or external search integration. |
| Around 12,000 posts, without Pagefind | For the reference profile, site generation fits the Free file allowance. Use an external search integration, or disable search when it is not needed. |
| Larger sites | Use the builder results below to plan resources, then choose hosting with enough file capacity. Check your own theme, archives and media before migration. |
About 12,000 posts without a local search index, or about 7,500 with Pagefind, are useful Cloudflare Free planning examples for this profile. They are not built-in post limits or universal capacity guarantees. The remaining file budget is small; see Hosting Limits for exact counts and growth room.
Use 2 vCPU and 8 GB of RAM as a reference configuration for sites with several thousand posts. Smaller sites can need less. The measured peaks below are observations, not minimum-memory requirements; do not size a build machine exactly to a recorded peak. Node.js 22.22.0 or later is required by the builder. Use your project’s pinned supported version for reproducibility.
Builder Capacity
These measurements start with prepared chunked Preview Data and invoke the actual zeropress-build CLI. Reading and validating the input, rendering the site, and writing its files are included. There is no WordPress runtime, WXR conversion, importer or starter build coordinator in the measured command. Both tables include five additional pages and use externally hosted images.
Each configuration was measured three times with a fresh output directory, process and constrained Linux ARM64 container: 2 vCPU, 8 GB RAM, no swap, and a 20-minute combined wall-time limit. Time is the median of the three attempts; memory is the largest cgroup peak across them, including charged file cache, kernel usage and the measurement supervisor. This is different from process RSS or JS heap size.
Site Generation Without A Local Search Index
Every row uses --skip-search-index. Pagefind is not run. The normal site files, including posts, pages, archives, feeds, theme assets and the sitemap, are still built. This measures site generation without the cost of a usable local search index. The option alone does not install external search or hide the search UI.
| Posts | Build time | Peak build memory | Generated files | Largest file |
|---|---|---|---|---|
| 100 | 0.59 s | 0.25 GB | 193 | 0.05 MiB |
| 1,000 | 3.64 s | 0.47 GB | 1,623 | 0.18 MiB |
| 2,500 | 10.09 s | 0.98 GB | 4,023 | 0.44 MiB |
| 5,000 | 21.66 s | 1.45 GB | 8,023 | 0.87 MiB |
| 7,500 | 37.26 s | 2.09 GB | 12,023 | 1.31 MiB |
| 12,000 | 60.01 s | 2.93 GB | 19,223 | 2.10 MiB |
| 62,500 | 13 min 17 s | 6.73 GB | 100,023 | 10.91 MiB |
The 62,500-post case also passed all three attempts with the same content and taxonomy growth rules. It produced 100,023 files before Pagefind. The upload-candidate count is 100,022, which exceeds Cloudflare Paid’s 100,000-file allowance. This is a larger builder-only example, not a complete importer/search/deployment workflow or a hosting capacity claim.
Site Generation With Pagefind
These are separate builds from the same prepared inputs. The CLI still uses --skip-search-index, then exits before the Pagefind postprocessor runs in a separate process. The timed work includes indexing, switching the search adapter and removing the unused native index. Final files include the working Pagefind index. Search was checked in a browser at all five sizes.
| Posts | Build time | Peak build memory | Generated files | Largest file |
|---|---|---|---|---|
| 100 | 0.77 s | 0.29 GB | 323 | 0.17 MiB |
| 1,000 | 5.00 s | 0.62 GB | 2,752 | 0.18 MiB |
| 2,500 | 13.42 s | 1.35 GB | 6,658 | 0.44 MiB |
| 5,000 | 27.86 s | 2.57 GB | 13,170 | 0.87 MiB |
| 7,500 | 43.90 s | 3.78 GB | 19,686 | 1.31 MiB |
All five conditions passed three times. A starter that keeps its build process alive during indexing can have different memory use; these are measurements of the sequential CLI-plus-Pagefind workflow. Input conversion and external search services would add their own work and are excluded from both tables.
Reference Profile And Measurement Scope
The measurements were completed on November 9, 2026, with Node.js 24.21.0 and Pagefind 1.5.2, with Node’s default heap configuration. The same reference theme, taken from WXR Starter, is used throughout. The theme is applied to Preview Data directly; using it does not require WordPress.
- Every row has five additional pages, one author and one menu.
- English post bodies follow an 8 / 16 / 16 / 24 KiB HTML pattern, approximately 16 KiB per post on average.
- There are ten categories, three tag assignments per post and a tag catalog that grows with site size. Listing pages contain ten posts.
- Each post references two externally hosted images. Image binaries are not included in the output. Comments and newsletters are off; feeds and archives are enabled.
- All counts, including 62,500, use this profile. Repeated successful runs produced byte-identical output.
GB means 1,000,000,000 bytes; KiB and MiB mean 1,024 and 1,048,576 bytes. Input generation, dependency installation, cloning, copying, verification and upload are outside timing. Filesystem caches are not forcibly flushed. These results do not measure visitor traffic or a complete deployment job.
Build Environment
Keep enough writable disk space for Preview Data, temporary build data and final output. Output replacement stages a new site before replacing an existing one, so allow room for both generations when rebuilding in the same directory. Before deployment, check your hosting provider’s file limits as well.
Why This Build Budget
The 2 vCPU / 8 GB RAM / 20-minute budget represents a common entry-level build environment. It follows Cloudflare Workers Builds Free’s published limits and uses the same CPU and memory budget as GitHub’s standard private-repository Ubuntu runners. It is a reference test budget, not a minimum requirement for all ZeroPress sites.
The following published specifications were checked on November 9, 2026. GitHub rows refer to standard Ubuntu x64 runners such as ubuntu-latest, using the runner specifications and hosted-job time limit. Cloudflare rows use the Workers Builds limits.
| Build environment | CPU | Memory (RAM) | Disk | Time limit |
|---|---|---|---|---|
| GitHub Actions, public repository | 4 vCPU | 16 GB | 14 GB SSD | 6 hours per job |
| GitHub Actions, private repository | 2 vCPU | 8 GB | 14 GB SSD | 6 hours per job |
| Cloudflare Workers Builds, Free | 2 vCPU | 8 GB | 20 GB | 20 minutes |
| Cloudflare Workers Builds, Paid | 4 vCPU | 8 GB | 20 GB | 20 minutes |
| Local constrained measurement | 2 vCPU | 8 GB | No disk quota imposed | 20 minutes |
GitHub workflows can set a shorter timeout. Include dependency installation, other tests and upload when choosing the workflow timeout; the six-hour service limit does not override a shorter job setting. Cloudflare’s Paid build environment has more CPU but the same memory allowance as Free; a memory bottleneck may therefore remain.
These resources apply where the build command runs. Building in GitHub Actions and uploading with Wrangler uses the GitHub runner for site generation. Cloudflare Workers Builds is the separate Git-connected build service. These build-machine specifications are also separate from the deployed Worker’s request-processing limits.
Differences From The Local Measurement
The local test applies CPU and memory limits to the build processes. It does not reproduce every property of a hosted runner:
- Architecture and software: the test uses Debian-based Linux ARM64 in Docker, while the GitHub runners above use Ubuntu x64. Cloudflare documents Ubuntu 24.04 and x86_64. CPU performance, runtime versions, and native Pagefind binaries can differ. A two-vCPU quota does not establish identical execution speed.
- Available memory: the local 8,000,000,000-byte limit covers the build process group and charged file cache. It does not model all of a provider’s operating-system and runner overhead. Equal advertised RAM does not guarantee identical memory available to the build.
- Elapsed time: the timed work covers site generation, optionally followed by Pagefind. Input conversion, cloning, installation and upload are excluded, so the measured duration is not a complete CI or deployment duration.
- Disk: the test records output sizes but imposes neither a 14 GB nor a 20 GB quota. Repository history, dependencies, intermediate data, temporary files, and final output all need space in a real build environment.
The results therefore demonstrate local builds within a relevant CPU, memory, and time budget. They do not certify equivalent performance, available disk space, or successful deployment on either provider.
Content And Input Limits
Body-size policies belong to the product processing the content. They are measured in UTF-8 bytes, including markup, whitespace and inline data; linked media files do not count toward the body size.
| Product | Default body policy |
|---|---|
| Build CLI / Build Core | Warn from 256 KiB; no fixed input-body maximum. An optional maximum can be configured. |
| Build Pages / Markdown | Warn from 256 KiB of converted content; optional --max-body-bytes maximum, with no fixed default ceiling. |
| WXR importer | Warn from 256 KiB; no fixed body maximum. An optional maximum checks both the source body and converted content. |
| ZeroPress Static | Warn from 256 KiB; refuse export/publication above 4 MiB (4,194,304 bytes). Exactly 4 MiB is allowed. |
| ZeroPress Studio | Keep the 1 MiB write maximum and its separate storage and recovery checks. |
The importer and builder accept --max-body-bytes <bytes>. For example, --max-body-bytes 1048576 allows exactly 1 MiB and rejects larger bodies. Omitting the option imposes no product-level body ceiling. JavaScript callers use maxBodyBytes; omission or null has the same default behavior. See the CLI guide for usage.
The builder checks Preview Data posts/pages.content before rendering, for single-file input, chunk input and object APIs. It does not reapply a body maximum to rendered HTML or the final themed page. Markdown rendering, code highlighting and theme output can increase the generated file size.
No fixed body maximum does not mean unlimited capacity. Parsing, memory, temporary storage, execution time, format validation and hosting limits still apply. Integrations accepting untrusted content should configure a body maximum that fits their resource budget. A body is never silently truncated to fit. Base64 body images are a separate opt-in policy: Build CLI and Build Pages accept --allow-data-uri-images for validated PNG, JPEG, GIF and WebP images. A larger body allowance alone does not enable them. Encoded images count toward input size and can enlarge generated HTML; hosting file limits still apply. WXR and Studio product defaults continue to remove Data URI images during body rendering. See Data URI body images.
For large datasets, use a compatible tool’s chunked Preview Data output to avoid assembling the entire site in one JSON string. The builder supports both legacy single-file input and a chunk manifest. Keep the manifest and referenced parts together; keep these private inputs outside the public output directory. Chunk input reduces full-body memory retention but metadata and route catalogs still grow with site size, and temporary disk space is required.
Chunk transport checks a 16 MiB manifest limit and a 32 MiB per-chunk limit, alongside hashes, counts and safe paths. These are validation bounds, not a combined site-size allowance. See the build CLI guide and Theme Package Limits for their separate contracts.
Search Limits
Choose search according to your content and operating requirements. ZeroPress site generation can be used with native search, Pagefind, or an external search service. The builder does not require Pagefind. Choose the search integration that fits the site you are building.
| Search method | How it works | What to plan for |
|---|---|---|
| Native search | The builder writes a JSON index that is searched in the browser. | A small index within the safety limits below; no separate search service. |
| Pagefind | A local indexing step reads the generated HTML and writes static search files. | Build memory, indexing time, browser search behavior, and additional hosted files. |
| External search | A separate service maintains the index and serves search results. | Search UI integration, crawling or content synchronization, and the provider’s limits and pricing. |
Pagefind provides static search without a separate search server. It can be a convenient choice for a personal blog or other site whose index fits the build and hosting budgets. The table above gives concrete examples of its additional build and hosting cost. Consider content size, update frequency, available resources, and required search features when choosing. See Pagefind’s documentation for its indexing workflow.
External services such as Algolia or Google Programmable Search Engine are additional options. Their integration and capacity were not benchmarked here. Replacing Pagefind requires adapting the theme’s search UI and arranging the provider’s crawl or index updates. Configure the build to omit Pagefind if you no longer use it; omitting local indexing alone does not provide external search.
Native Search Limits
The following limits protect the native index. They are not site-wide post limits and do not require switching specifically to Pagefind. The builder applies them to the uncompressed UTF-8 JSON index:
| Condition | Result |
|---|---|
| Less than 2 MiB, with at most 5,000 searchable records | Normal native index |
| At least 2 MiB but less than 5 MiB, with at most 5,000 records | Normal native index with a recommendation to use external search |
| At least 5 MiB, or more than 5,000 records | Native indexing is omitted with a warning; the build continues |
Searchable records include eligible posts and pages. Exactly 5,000 records are allowed if the size limit is not reached. The --skip-search-index option also omits native indexing explicitly. Omission writes one non-searchable placeholder and keeps the adapters; native queries return no results until a replacement search integration is configured. The option controls native indexing only: it neither disables a separate Pagefind step nor installs or configures Pagefind or an external search service.
If Preview Data or the theme disables search, no search artifacts are generated, even with --skip-search-index. An enabled search with no eligible content keeps a genuinely empty index. See Static Search for the exact output rules and Pagefind setup.
Hosting Limits
A post count differs from the final file count. Posts, pages, archives, theme assets, search indexes and local media all consume hosted files.
Cloudflare Workers Static Assets
Cloudflare currently documents the following per-version limits:
| Plan | Static files | Maximum size of one file |
|---|---|---|
| Free | 20,000 | 25 MiB |
| Paid | 100,000 | 25 MiB |
See Cloudflare Workers limits. These are Workers Static Assets limits, not a ZeroPress post limit. Provider specifications on this page were checked on November 9, 2026.
| Planning example | Actual upload candidates | Room within 20,000 files |
|---|---|---|
| 12,000 posts, site generation only | 19,222 | 778 files |
| 7,500 posts, including Pagefind | 19,685 | 315 files |
Both examples include five additional pages, external images and the reference theme. Their largest files are below 25 MiB. The build tables count every physical file; this table excludes only root _redirects, which is deployment configuration. These are locally audited upload candidates, not completed Cloudflare deployments.
Allow room for growth. These examples sit close to the Free file allowance. Local images, additional pages, languages, archives or index changes can consume the remaining slots. As an operational planning rule, start reviewing the next hosting or search configuration around 18,000 final upload files; that is suggested headroom, not another provider limit or a measured post-count ceiling.
Keep Pagefind if it meets your needs and choose hosting with more file capacity, or integrate an external search service and omit local indexing. Count the finished output after every configured postprocessing step. Disabling native indexing alone does not remove Pagefind’s files or provide external search.
Additional Publishing Workflows
WordPress, Studio, Markdown and other tools can prepare data for the shared builder. Their preparation, storage, authentication and upload limits are additional to the builder limits on this page.
Markdown Sites
zeropress-build-pages handles Markdown preparation before the shared builder. It captures documents, resolves routes, converts them one at a time, and uses chunked Preview Data for the build. The compatible single JSON export remains available, but the normal build and Markdown Starter’s Pagefind handoff do not load that entire document. No extra option is needed to use this path.
A separate Markdown/docs2 check used 16 KiB source files with front matter, English/Korean text and internal links, with no local images. Each condition ran once at 2 vCPU / 8 GB RAM / 20 minutes on Linux ARM64 with Node 24.21.0, --skip-search-index, source copying disabled and link checking enabled. Pagefind 1.5.2 and browser search checks were included in the second workflow. These observations include Markdown preparation and are separate from the three-run builder-only measurements above.
| Markdown documents | Build time without Pagefind | Files without Pagefind | Build + Pagefind time | Files with Pagefind | Peak memory with Pagefind |
|---|---|---|---|---|---|
| 100 | 0.87 s | 108 | 0.91 s | 226 | 0.15 GB |
| 7,500 | 34.68 s | 7,508 | 42.24 s | 15,036 | 3.02 GB |
| 12,000 | 54.49 s | 12,008 | 68.42 s | 24,038 | 4.62 GB |
Memory is the whole-job cgroup peak, including charged file cache. The two workflows were measured separately. This pages-only theme generates fewer archive files than the blog profile above, but Pagefind still adds substantial files and memory use. 12,000 Markdown documents with Pagefind exceed the Free 20,000-file allowance in this example. Count your complete output; neither table establishes a universal document limit.
Staged preparation trades disk space and I/O time for lower body retention in memory. Allow room for private snapshots, compatible JSON, chunk generations and both output generations. One document and its front matter are still read in full, and routing/configuration metadata still grows with the site. A record or header beyond chunk transport bounds uses a validated legacy fallback with a warning; that path retains aggregate-memory and string limits. For format, cleanup and postprocessor details, see Build Pages output.
WordPress Sites
For WordPress → ZeroPress Static → importer → WXR Starter, see WordPress Workflow Capacity for publication requirements, WXR conversion and starter build capacity.
When A Limit Stops Your Build
| Symptom | Next step |
|---|---|
| A post or page exceeds a body limit | Check which product or configured maximum rejected it. Shorten or split the content, or review an explicitly configured importer/build maximum against available resources. Studio and Static retain their own fixed limits. |
| A large single JSON input cannot be loaded | Use compatible chunked Preview Data output. Do not split JSON manually or mix generations. |
| The builder runs out of memory or disk | Check the failing stage, temporary storage and build budget. Chunk input helps with body retention; large metadata and route catalogs still consume resources. |
| Pagefind runs out of memory or time | Increase build resources, review the indexing workload, or integrate external search. Verify the entire configured workflow before deploying. |
| Native search returns no results after an omission warning | Complete a Pagefind or external search integration, or disable search if it is not needed. |
| Hosting rejects file count or size | Inspect final output including search and media. Reduce generated files, move media to separate storage, or choose a suitable hosting plan. |
After fixing a failed build, rerun and verify the complete configured workflow. Deploy only when site generation and every configured postprocessing step succeed, including search indexing when enabled.
Validate Your Site Before Migration
Use a clean installation of released packages on your intended build host. Build with your actual theme, representative content and chosen search setup. Check the complete job time, including installation and upload, as well as peak memory, disk usage, final file count, largest file and search results. Local ARM64 measurements cannot substitute for checking your project’s Ubuntu x64 or other hosting environment.
Try the chosen deployment workflow before switching the site address. Allow for future content as well as the first successful build.
For a reproducible builder problem, include package versions, content counts, build resources, command options and the error message when requesting support. Remove tokens, private content and other sensitive information from reports.