A small shop can lose more from an old backup than from a high bill for its website. A host runs your site on a server, a computer that stores its files and sends pages to visitors. A restore puts saved data back on the site. If orders arrive after that copy was made, a full restore can remove them. Start with the work you need to save, then check which plans fit. The small Kinsta plan below is a baseline example for a content site, not a shop recommendation.
Kinsta and WP Engine both offer backups and ways to test a copy of your site [3], [4]. The bill can look fair while the restore rules leave you with work to do. The plan pages were checked on October 20, 2026. Kinsta's backup guide was saved on October 18. They do not show which host is faster.
Choose the billing unit before you compare the price
GB stands for gigabyte, a unit of data sent or stored. Kinsta's Single 20GB plan lists one WordPress install, meaning one WordPress site, 20GB of server traffic per month and 10GB of storage [1]. Kinsta does not recommend this plan for ecommerce or membership sites, such as shops or sites with member accounts [1]. Server traffic, called server bandwidth here, is data sent by the site's server. The plan also includes 125GB per month through its CDN, a network that serves site files from other locations [1]. Server traffic and CDN traffic have separate limits. Don't add them into one pool.
Kinsta offers the first month free to new customers on select plans [1]. The Single 20GB monthly offer shows a free first month, then US$35 per month [1]. Its annual option says US$350 after the first month [1]. These are separate payment choices, before tax [1]. An annual rate shown per month does not mean you can pay each month. Check the renewal amount and the full charge before you buy.
WP Engine's Essential page has a one-site choice with 10GB of storage and 25,000 visits per month [2]. The page calls visit numbers estimates [2]. It asks owners of dynamic sites or sites with traffic spikes to get in touch [2]. A dynamic site does work for each user, such as a shop checkout. That estimate is not proof that a busy checkout will cope.
The Essential page advertises a starting annual offer of US$28 per month, with US$336 due today [2]. The first-year offer is for new Essential customers who meet its terms [2]. Renewal prices can change [2]. The page does not tie that price to each choice in its plan builder [2]. Get a quote for your exact plan. Ask what it will cost to renew before you compare the bills.
A visit is a count made under the host's rules, rather than a measure of data sent or stored. Kinsta's visit-based plans use unique IP addresses within a 24-hour period, summed over the month [5]. WP Engine also describes a 24-hour IP rule and excludes bot page views in its overage guide [6]. An IP address is a network address; it need not stand for one person. Bots are software that can visit a site. These rules do not prove that both hosts will count the same visits.
Keep your own traffic report beside each host's quote. Ask the host to show how that traffic fits its billing rules. If all you have is a count from a web analytics tool that reports site traffic, leave the expected bill open.
Read the extra-use charges as separate costs
Kinsta's overage guide lists these charges [5]. An overage is use above what your plan includes.
| Extra use | Kinsta's stated charge | What to check |
|---|---|---|
| Visits on a visit-based plan | US$0.50 per 1,000 extra visits [5] | Use this only for a visit-based plan. |
| Server traffic on a bandwidth-based plan | US$0.50 per extra GB [5] | Keep it apart from CDN traffic. |
| Storage | US$2 per GB per month, worked out daily [5] | A brief increase differs from a full month at that level. |
| CDN traffic | US$0.05 per extra GB [5] | Check the CDN's own usage total. |
Kinsta has a separate early-charge rule for server bandwidth [5]. If you exceed your plan's server bandwidth by more than 250GB and have not upgraded, it charges you at the end of the first week after the overage [5]. If the second billing attempt fails, Kinsta can suspend your account until the issue is resolved [5].
The same guide also allows early action for an extreme overage [5]. Its threshold is the plan cost or US$500, whichever is less [5]. Kinsta can ask for payment or an upgrade and can limit access until the issue is resolved [5]. The pricing page's broad promise to keep sites online needs that condition beside it [1], [5]. An alert is not a spending cap.
WP Engine's overage page quotes US$2 per 1,000 extra monthly visitors for named plans such as Startup and Growth [6]. Its current sales page uses Essential [2]. Those names do not show that the fee applies to Essential. Ask for the fee that applies to your exact Essential quote. Until then, a total-cost winner would rest on an unknown.
Match the backup to the loss you can bear
Both hosts describe daily automatic backups [3], [4]. A daily copy can still leave recent work outside the saved state. The right question is how much work your business could rebuild if the latest usable copy were older than expected.
Kinsta lists 14 days of backup history for Single 20GB [1]. WP Engine's restore guide says it keeps 30 days of backups [4]. Ask support for access beyond those shown in its control panel [4]. Its pricing page uses a broader range of at least 30 and no more than 60 days [2]. Plan on the stated 30 days here. Don't count on a specific older copy.
A longer history can help when you find a fault late. It does not make the latest copy more recent. A shop may not be able to lose a day's orders. Ask how often the host saves a copy, even if it keeps a long history.
Kinsta's extra-backup options cost US$20 per site per month for a copy every six hours, or US$100 for a copy every hour [3]. Those extra copies remain available for 24 hours [3]. Daily backups continue too [3]. If you turn off the extra-backup service, Kinsta deletes its available extra copies [3]. This is a choice about both cost and how far back you can go.
Before a risky change, you can make a manual backup. Kinsta allows up to five manual backups, stored for at least 14 days [3]. The period depends on the plan [3]. A plugin adds site features; a theme controls how the site looks. The update backups have different rules: manual plugin and theme update backups last two hours, while Kinsta Automatic Updates backups last three days [3]. A restore point is a saved version from a given time. Don't assume each one has your plan's normal life.
Check where the copy is and how you can use it
Kinsta's snapshot backup saves the site as it was at a given time [3]. It sits on the same host machine as the site [3]. It includes files, the database of site records, and settings such as redirects and server rules [3]. Redirects send visitors from one web address to another. Server rules control how the server handles requests. MyKinsta is Kinsta's site control panel. Its download contains files and the database, but leaves out MyKinsta and custom server settings [3]. Those copies cannot stand in for each other without extra work.
You can create a Kinsta download once per week [3]. Once ready, it is available to download for 48 hours [3]. Save it somewhere you control, with a separate record of the settings it leaves out. A saved file still needs a restore check before you rely on it.
Kinsta's external-backup add-on sends files, the database or both to your Amazon S3 or Google Cloud Storage account each week or month [3]. These are separate online storage services. It costs US$2 per site backup per month plus US$1 per GB of bandwidth per month [3]. The storage company bills its own costs too [3]. You cannot restore these external copies directly in MyKinsta [3].
WP Engine stores backups offsite on Amazon S3 [4]. Its guide says they are in the site's region, with a stated exception for Tel Aviv backups in Frankfurt [4]. Offsite does not always mean a different region. A ZIP file packages the backup into a file you can download. A prepared ZIP download stays available for up to seven days [4]. The guide says it has no automatic export of its generated backups to another service [4]. A separate backup tool is a different route.
WP Engine lists files it leaves out [4]. These include logs, caches and other backups [4]. Logs are records of site events. Caches hold saved data for reuse. Some custom database features can cause a restore to fail [4]. Its guide names custom views and functions [4]. These are ways a developer can change how the site reads or handles stored data. If your developer added these, ask for a supported recovery path before you depend on the built-in restore.
Choose a recovery path before a host
For a shop, seek quotes for plans that fit that use; do not use Single 20GB as the shop choice [1]. Use the same example for those quotes: your site takes orders, a change breaks checkout, and orders came in after the last clean backup. Ask each host how you would recover without losing those orders.
Kinsta's snapshot restore rolls back the files, database and saved settings [3]. It can also remove domain entries added in MyKinsta after the backup [3]. These are records of site addresses in the control panel. Removing one does not take away your ownership of that domain. WP Engine calls its restore destructive [4]. It writes over content and removes files that were not in the saved copy [4]. Its built-in tool cannot select single database tables [4]. Tables hold groups of records within the database. Neither description is a promise to merge old data with new orders.
An environment is a separate live or test copy of a site. WP Engine permits only one backup, copy or restore operation per environment at a time [4]. A second operation can fail while the first is still active [4]. Its guide says a restore can take a few minutes to several hours [4]. The time depends on the site's size and file count [4]. That is not a deadline for your site.
Fill in this sheet for each exact plan. Keep the answers and their source beside the quote.
| Your need | Evidence to ask for | Decision |
|---|---|---|
| Keep recent orders | Copy frequency and a way to preserve later orders | Stop if the proposed restore loses work you cannot rebuild. |
| Recover an older clean state | Available history for that backup type | Stop if the needed copy could expire first. |
| Recover without the live server | Copy location, included settings and a supported restore route | Ask for a trial restore if the route is untested. |
| Keep the bill within reach | Exact plan, billing unit, extra-use fees and renewal charge | Leave cost undecided while a required amount is unknown. |
| Get the site working again | A named person with permission to restore, plus a check of checkout after recovery | Keep the current host until the new path is proved. |
Rule out a plan that fails a needed task before you compare its price. If neither quote answers the questions, wait. Keeping the current host while you close those gaps is a valid choice.
For the plans above, the public pages support useful backup and billing checks. They do not yet support an all-in cost winner, a speed winner or a promise that either host will recover your particular shop. Choose only after the exact quote and the recovery path meet your needs.




