Skip to content
Early bird + Black Friday · 73% off

Get ZeroDirs for $179 $49

Claim $49 deal

Cost and limits

Static files run out first: 20,000 per version on the free plan, 100,000 on Workers Paid. budget.plan in site.config.ts picks the ceiling the build enforces.

Each listing costs:

1 HTML page
1 Pagefind search fragment
1 OG image (seo.ogImages: 'generated' and seo.ogScope.listings, the defaults)
1 optimised logo (webp, every listing)

Plus about 3,000 files of overhead. The build warns above 80% and fails above 90%:

Setup Files per listing At $0 a month On Workers Paid
The defaults 4 ~3,750 ~21,750
seo.ogImages: 'static' 3 ~5,000 ~29,000

pnpm check:config counts 4 files per listing, over the approved rows in the local database. Other free allowances have to hold too:

Resource Free allowance At $0
Static files 20,000 per version see above
D1 rows written 100,000 a day ~40,000 clicks a day, at ~2 writes each
Worker requests 100,000 a day ~100,000 dynamic requests, crawlers included
Workers Builds 3,000 minutes a month, 20 a build ~7 builds a day at ~4 minutes uses ~28%
Email (Resend free) 3,000 a month and 100 a day a launch spike stops at 100
Cron triggers 5 per account 1, the hourly trigger in wrangler.jsonc

Workers Paid, $5 a month: 100,000 files per version, 30 s CPU per request by default, 10 million requests a month included, 6,000 build minutes.

site.config.ts
budget: { plan: 'paid' },
Where You should see
The estimate pnpm check:config, or --listings 5000 for a what-if budget: … (free plan, P%) — ok and headroom: up to ~N listings …; past 90% it exits 1 with budget exceeded:
The real count pnpm build [zerodirs:budget] budget: N files / 20000 (P%) — free plan, ok; above 80% a budget warning: line follows
The quotas Workers & Pages → your Worker → Metrics and Builds; D1 → your database → Metrics requests, CPU, build minutes, rows read and written
  • budget.plan: 'paid' moves the ceiling the build enforces, not the billing; upgrade in the Cloudflare dashboard.
  • The estimate budgets pSEO up to pseo.maxPages; the build counts what is on disk, so the two differ.
  • seo.ogScope.pseo: true adds a PNG per generated page, the first switch to check near the ceiling.
  • One build at a time per account, not per Worker: two sites from one account build serially.
  • Pagefind gets uncomfortable at roughly 10,000–20,000 pages, before the file limit does. See Search.
  • providers.email: 'cloudflare' needs Workers Paid. On the free plan send with Resend, or notify a verified destination address with providers.adminNotify: 'cloudflare-verified'.
Quota spent What happens
Any Worker quota Static pages stay up.
D1 writes, on a click The visitor still arrives; the count is lost. The Worker log says clicks: recording a click for listing <id> failed.
D1 writes, on a submission The form answers “Submissions are temporarily unavailable. Please try again later.” and writes nothing.
Resend, past 100 a day Resend answers 429; the outbox row stays pending, retried hourly up to 5 attempts, then failed.
Build minutes, file budget, or the orphan check The build fails, the last good version stays live, and budget exceeded: ends with Cut files (seo.ogScope, fewer pSEO templates, fewer listings) or raise budget.plan to 'paid' (100000 files).

budget.plan, seo.ogImages, the three seo.ogScope switches, limits.submissionsPerEmailPerDay and limits.unpaidTtlDays — budget, limits, seo, pseo.

  • Directorysrc/
    • lib/budget.ts PLAN_FILE_LIMITS, OVERHEAD_FILES, the thresholds, maxListings()
    • config/defaults.ts DEFAULT_BUDGET, DEFAULT_LIMITS
  • integrations/budget.ts the count after the build
  • scripts/check-config.ts the estimate and the headroom line
  • wrangler.jsonc the one cron trigger
  • tests/unit/budget.test.ts the arithmetic