WordPress staging · user-entered costs and setup checks

Compare staging and production site costs

Compare annual staging and production hosting, database, domain, email, and other costs, then check environment parity and staging safety assumptions.

Compare one production WordPress site with its staging copy over 12 months. Enter costs in the same currency and billing period. Monthly inputs are multiplied by 12; annual inputs are included once. Use the amounts that apply to your plan and account, including separate resources where they are billed.

Production hosting per month Staging hosting per month Production database or storage add-ons per month Staging database or storage add-ons per month Production domain and DNS charges per year Staging domain and DNS charges per year Production email or mail-service costs per month Staging email or mail-service costs per month Other production add-ons per month Other staging add-ons per month

Enter all ten amounts. Use 0 for a category that does not apply.

The annual estimate is production monthly charges × 12 plus annual domain/DNS costs, compared with the equivalent staging sum. “Other” can include a separate staging plan, backup, or paid tool when applicable. It does not estimate labor, taxes, variable usage, renewal changes, or costs you did not enter.

Staging parity and safety checklist

A staging copy may share production code and data. Record where your test environment matches and where it deliberately differs; a test result only applies to the conditions you actually exercised. WordPress Hosting guidance describes potential real email, scheduled task, external-service, and search-indexing side effects when a copy is not configured appropriately.

Record what is being compared

WordPress core, theme, plugin, and custom-code versions are recorded for both environments.
PHP/runtime version, extensions, memory and upload limits, and relevant server configuration are compared.
Database engine/version, character set, schema, and a representative data snapshot are checked.
Uploads and other needed files are present; storage or media differences are written down.
Site URL, environment variables, secrets handling, API endpoints, and feature flags are reviewed without copying production credentials into an unsafe environment.
Host plan limits and separately charged staging resources are verified from current account terms and bills.

Prevent staging side effects

Access is restricted with authentication or another access control; a search-engine discouragement setting alone is not treated as access control.
Outgoing email is captured or disabled so tests cannot message real customers or subscribers.
Scheduled events and external schedulers are reviewed; payment, subscription, webhook, and API integrations use safe test behavior.
WordPress environment type is set to staging on the copy, and will not be pushed back to production.
Backups cover both WordPress files and database before copying data or pushing changes.
The push/copy direction, overwrite scope, rollback owner, and production verification steps are understood.

0 checklist items checked.

Sources and scope

Source pages checked November 3, 2026. These references explain WordPress behavior; they do not define what a particular hosting plan includes.

Make WordPress Hosting: Staging Environments — environment type, restricting access, stopping or capturing outgoing email, scheduled jobs, external services, and search indexing.
WordPress developer handbook: WP_ENVIRONMENT_TYPE — environment-type configuration and values.
WordPress backup guidance — a typical full-site restore needs both files and database.

This worksheet does not inspect your host, copy a site, verify security, or prove production parity. Confirm current provider pricing, resource limits, staging terms, and backup scope in your account. For transition work, see the host move checklist and cost worksheet.

How it works

Enter monthly and annual costs for the production site and its staging copy using the same currency. The calculator annualizes monthly amounts and compares totals. Use the printable checklist to record environment differences and verify access, email, scheduled jobs, backups, and other side effects.

Good to know

Does this assume my host includes staging at no extra cost?

No. Check your plan and account terms, and enter any staging charge that applies. A staging feature can still use hosting resources or require separate services; this calculator does not infer what a plan includes.

What does parity mean in this checklist?

It prompts you to record which production settings and services the test copy shares or differs on, including runtime, database, files, environment configuration, and integrations. A copy can be similar enough for a useful test while still needing safety differences such as restricted access and captured outgoing mail.

Does the checklist configure or secure a staging site?

No. It runs in your browser and records checked items only. Follow your host and application instructions, then verify the settings on the actual staging copy.

Impact — TODO: apply/approval and configure referral URL — referral link not configured.

CJ Affiliate — TODO: apply/approval and configure referral URL — referral link not configured.

PartnerStack — TODO: apply/approval and configure referral URL — referral link not configured.