Get Started
WordPress Workflow Capacity
This page covers the WordPress → ZeroPress Static → WXR importer → WXR Starter workflow. For the shared builder’s current planning guidance and independent CLI measurements, see Capacity and Limits.
WordPress Preparation And Publication
The plugin requires WordPress 6.8+, PHP 8.2+, and a single-site installation. Preparation, first publication, unchanged republication and one-post updates were verified with a PHP memory limit of 128 MiB using isolated WordPress and a local GitHub test server. Separate checks covered interruptions, downloads and temporary storage. These checks assess plugin processing and recovery; they do not establish real GitHub network performance or a maximum site size.
WordPress and the builder run separately. Increasing PHP memory does not increase Node.js build memory. WordPress also needs private writable temporary storage for export and publication work; plugins and larger metadata can add memory and disk requirements.
Complete Workflow Builds
These measurements start with WXR and run the WXR Starter’s importer and site builder. They include converting the export, writing and reading chunked Preview Data, rendering the theme, and writing the site. The Pagefind series also includes search indexing. WordPress preparation and GitHub publication are separate.
Each configuration was measured three times in a fresh Linux ARM64 container with 2 vCPU, 8 GB of RAM, no swap, and a 20-minute combined time limit. Time is the median of three attempts; memory is the largest kernel-recorded build-environment peak across them, including charged file cache, kernel usage and the measurement supervisor. It is not just the JavaScript heap or a minimum RAM requirement. Both series use --skip-search-index.
See Why This Build Budget for the GitHub Actions and Cloudflare Workers Builds comparison and the differences from our local environment.
Site Generation Without Pagefind
These independent runs stop after WXR conversion and site generation. Pagefind is not started. Native indexing is skipped, so the output has no usable local search index. Use an external search integration or disable search when it is not needed; --skip-search-index alone does neither.
| Posts | Import + build time | Peak build memory | Generated files | Largest file |
|---|---|---|---|---|
| 100 | 0.86 s | 0.17 GB | 193 | 0.05 MiB |
| 1,000 | 5.00 s | 0.51 GB | 1,623 | 0.18 MiB |
| 2,500 | 13.07 s | 1.03 GB | 4,023 | 0.44 MiB |
| 5,000 | 27.69 s | 1.55 GB | 8,023 | 0.87 MiB |
| 7,500 | 44.08 s | 2.22 GB | 12,023 | 1.31 MiB |
| 12,000 | 81.00 s | 3.18 GB | 19,223 | 2.10 MiB |
At 12,000 posts, the output has 19,223 generated files and 19,222 upload candidates. That leaves 778 files within the reference Free allowance of 20,000, before adding more content or local media.
Full Build With Pagefind
These are separate complete WXR imports and starter builds using the same inputs. After rendering, the starter indexes the HTML with Pagefind, replaces the search adapter, and removes the unused native index. Time and memory include all of these steps. Search was checked in a browser at every size.
| Posts | Import + build time | Peak build memory | Generated files | Largest file |
|---|---|---|---|---|
| 100 | 1.00 s | 0.48 GB | 323 | 0.17 MiB |
| 1,000 | 6.56 s | 0.96 GB | 2,752 | 0.18 MiB |
| 2,500 | 17.16 s | 2.07 GB | 6,658 | 0.44 MiB |
| 5,000 | 41.19 s | 3.49 GB | 13,170 | 0.87 MiB |
| 7,500 | 64.20 s | 5.11 GB | 19,686 | 1.31 MiB |
| 12,000 | 111.12 s | 6.91 GB | 31,396 | 2.10 MiB |
At 7,500 posts, the output has 19,686 generated files and 19,685 upload candidates, leaving only 315 files of growth room. At 12,000 posts, the full build also succeeds, but its 31,395 upload candidates exceed the Free file allowance. A successful build does not by itself establish that a site fits its hosting plan.
Reference Profile And Measurement Scope
Measurements were completed on November 13, 2026, using Node.js 24.21.0 and Pagefind 1.5.2. All 36 builds passed, and the three repeats for each configuration produced byte-identical output. Pagefind changes only the search files.
- Every row includes five additional pages.
- 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.
- All cases use the same default WXR Starter theme, one author and one menu. Each post references two external images; image binaries are not included in the output. Comments and newsletters are off.
The inputs are local XML files reconstructed from retained WordPress exports, preserving the body content and the same taxonomy growth rules. Preparing those inputs, dependency installation, repository cloning, verification and uploads are outside timing. The larger local XML files can exceed GitHub’s single-file limit; normal plugin publication supports split WXR bundles. This measurement does not include PHP export or compare single and split WXR performance. No filesystem cache flush or disk quota was applied.
Generated files counts every physical output. For this fixture, upload candidates exclude only root _redirects, which is deployment configuration. All generated files are below 25 MiB. GB means 1,000,000,000 bytes; KiB and MiB mean 1,024 and 1,048,576 bytes.
The starter keeps its coordinator process alive during Pagefind. The direct CLI measurements in Builder Capacity exclude WXR conversion and exit the builder process before indexing, so their time and memory figures are not interchangeable with these tables.
Use around 12,000 posts without Pagefind or around 7,500 with Pagefind as planning examples for this profile, with little remaining file capacity. These are not built-in post limits. Longer bodies, other languages, more archive pages, local media and custom themes can change resource needs and file counts. Check the completed output against hosting limits and leave room for growth before choosing a deployment plan.
Export And Publication Limits
Post And Page Bodies
ZeroPress Static warns from 256 KiB (262,144 UTF-8 bytes) per eligible post or page and refuses export/publication above 4 MiB (4,194,304 bytes). Exactly 4 MiB is allowed. Both the stored body and its media-rewritten form are checked; markup and whitespace count, while linked media files do not. The plugin leaves the original WordPress content intact and never truncates it.
Preparation, completed downloads and publication were verified at the 4 MiB boundary in the WordPress environment described above. The limit applies to each body; it does not guarantee enough memory, temporary storage or build resources for a site with every body at that size.
The importer and builder have no fixed body maximum by default; callers can set an optional maximum. The starter inherits those defaults, so manually managed WXR exports are not subject to the plugin’s 4 MiB policy. All format, memory and output checks still apply. Base64 image support is a separate concern. See Content And Input Limits.
GitHub And Export Files
GitHub blocks regular repository files larger than 100 MiB. See GitHub file-size limits. A single large WXR can reach that boundary before the generated site reaches its hosting limits.
ZeroPress Static supports split WXR bundles. A bundle allows up to 256 XML parts, each at most 8 MiB, with a manifest of at most 1 MiB and a bound settings file of at most 8 MiB. The plugin also limits encoded upload requests to 8 MiB, so JSON escaping can make an individual upload too large before its raw file reaches 8 MiB. These are safety bounds, not a promise that every export up to their combined size will fit memory or time budgets.
Use a compatible WXR Starter and keep each manifest together with all files it references. Do not manually split the XML or remove part files. Chunked Preview Data similarly avoids one large JSON string during import and build; it does not make memory usage independent of site size.
Recovering From A Publication Problem
| Symptom | Next step |
|---|---|
| A body exceeds the plugin’s 4 MiB maximum | Shorten or split the indicated post, then prepare again. Increasing PHP memory does not bypass this body policy. |
| WordPress reports insufficient memory or temporary storage | Check the reported item, PHP memory, free disk and private-directory permissions with the host. |
| Publication pauses or a request times out | Check publication status and use the offered resume action. If approval expired, prepare again. Repeated preparation failures may need a longer host request timeout. |
| Publication result is uncertain | Use the plugin’s status check before another publication; do not assume the branch update failed. |
Keep source data and existing publications intact while diagnosing a failure. See Publish From WordPress for the workflow and Capacity and Limits for shared builder, search and hosting guidance. The measurements used local Linux ARM64 builds and a local GitHub test server. Verify the complete workflow on your intended build host and deployment service before migrating a site.