DreamHost fees grow in small line items: renewal jumps, add-ons nobody remembers buying, and a monthly charge for keeping a site on an end-of-life PHP version. Support shifted to chat and tickets, and replies slowed. If your bill went up while answers got slower, audit what you pay per site, then move.
What fees show up on a long-time DreamHost bill?
The pattern people describe is not one big charge. It is six or seven small ones. An intro rate that expired years ago. Domain privacy. A backup or restore add-on. A security add-on. Mailboxes billed per user. And, more recently, a monthly line item for staying on a PHP version that no longer gets security fixes.
None of that is a scam. It is all in the terms. The problem is that a customer who signed up in 2006 has never re-read the terms, and the bill has been on autopay for 19 years.
- Renewal pricing. The three-year promo rate ends, and the renewal is the standard rate. This is normal across the industry, which is why we wrote about why your hosting bill doubled at renewal.
- Legacy PHP support. DreamHost documents a charge for keeping a site on an end-of-life PHP version. The amount is set by them and appears as its own line on your invoice, so read it off your own bill rather than off a blog post.
- Add-ons you bought once. Domain privacy, a dedicated IP, a security scanner, a page builder license bundled at signup. Each is a few dollars. Together they are not.
- Email per mailbox. Five staff mailboxes at a few dollars each is a real recurring cost, and it grows every time you hire.
- Support tiers. Chat and tickets are standard. A call back is tied to plan level, so the entry plan does not get one.
Write each line item down. Then check which ones you would notice if they vanished tomorrow.
Why the fee for old PHP is the one that stings
PHP is the language WordPress runs on. Each version gets security fixes for a fixed window, then stops. According to W3Techs, PHP is the server-side language on roughly 74% of websites whose language is known (2026), so a version going end-of-life is a large event, not a niche one.
When a host charges to keep you on a dead version, they are covering the cost of patching something the PHP project no longer patches. Fair enough. But look at what the fee tells you about your setup. Your site is on old PHP because something on it breaks on PHP 8. Usually it is one abandoned plugin, a theme function from 2014, or custom code that calls a function removed years ago.
The fee does not fix that. It rents you more time with the problem. Meanwhile the abandoned plugin is also your biggest attack surface. According to Patchstack's State of WordPress Security report, 97% of new WordPress vulnerabilities disclosed came from plugins rather than core (2024).
A managed host handles this differently. We test the site on a newer PHP version in staging, find the file that throws the fatal error, and either patch it or replace the plugin. If you want the version-by-version detail, our PHP version guide for WordPress covers what breaks and when. The point is that somebody does the work instead of billing you monthly to avoid it.
The support part is what turns a billing annoyance into a decision. A fee you can absorb. Waiting four days for a reply on a site that is down is different. Our SLA page spells out what we commit to, because a response-time promise you cannot read is not a promise.
How to check what you are paying per site
Do this before you talk to any host, including us. It takes about 40 minutes and it is the only way to know if a move is worth it.
- Download the last 12 months of invoices from your billing panel.
- List every line item in a spreadsheet, one row each, with the yearly total.
- Add the things that never touch the hosting invoice: plugin and theme licenses, backup services, uptime monitors, mailboxes, SSL, a security plugin's pro tier.
- Add labor. Count the hours you or a freelancer spent on updates, cleanups, and "why is this slow" last year. Multiply by your rate.
- Divide the total by the number of sites you actually run. Not the number of sites your plan allows.
Then pull your last five support tickets and write down how long each one took to get a useful answer. Not the auto-reply. The answer.
Most people are surprised twice. Once by the per-site number, and once by how much of it is not hosting at all. We broke the arithmetic down in is managed WordPress hosting worth the extra cost, including the cases where the answer is no.
What a small law firm found when it did that math
Bellhaven Law is a small firm. Two partners, a few staff, one website that brings in consultation requests. Nobody there wanted to think about hosting.
Their setup had grown the way most do. Cheap shared hosting from years back. A stack of plugin licenses renewing on different dates, $470 a year in total. A freelance developer who built the site, did good work, and then got busy with other clients. When the contact form quietly stopped emailing leads, it took days to get a reply. Nobody knew how long the form had been broken before anyone noticed.
The diagnosis was boring, which is usually the case. The site was on an old PHP version because two plugins had not been updated in years. Backups existed in one place only, on the same server as the site. Half the plugin licenses were paying for features the firm did not use. And the monthly total nobody had added up came to about $310.
The fix was not clever. It was consolidation. One flat bill, one team accountable for the whole stack, updates tested before they ship, backups off the server, and monitoring that catches a broken form instead of waiting for a client to mention it.
Bellhaven now pays one flat $89 a month and gets a senior developer who answers in under two hours during business hours. The full numbers are in the Bellhaven Law case study, including what came off the invoice.
The part that mattered to the partners was not the savings. It was that a form failure now has an owner. If a silent failure is the thing you are worried about, what uptime monitors miss on a WordPress site explains why a green status page and a working contact form are two different questions.
DreamHost or managed WordPress hosting: what each covers
Every host draws the line between "included" and "add-on" somewhere. Here is where the lines usually fall. Fill the middle column from your own invoice, not from marketing pages.
| Line item | Typical shared or entry hosting plan | TopSyde at $89/mo per site |
|---|---|---|
| Hosting plan renewal | Promo rate ends, standard rate applies | Flat, same price at renewal |
| Legacy PHP version | Billed monthly per site to stay on end-of-life PHP | No such fee; we test and move you to a supported version |
| Plugin and theme updates | You or your developer | Tested on staging, then applied |
| Off-site backups and restores | Often an add-on or self-serve | Included, stored off the server |
| Malware detection and cleanup | Security add-on, cleanup often quoted separately | TopSyde Sentinel, with 24/7 monitoring |
| Monitoring beyond uptime | Not covered | Forms, checkout, and error monitoring |
| Human support | Chat and tickets, call back by plan tier | Senior developer, under 2 hours during business hours |
| Migration | Free for some platforms, fee for others | Free, we do the work |
Two notes on reading a table like this. First, a "free" add-on bundled at signup is frequently a capped trial that converts to a paid tier later, which we covered in marketing tools in managed hosting. Second, a security scanner that checks your public HTML is not the same as a server-side scan, and the gap is explained in what free WordPress malware scanners cannot see.
If you want the full list of what sits inside our plan, it is on the spec sheet, and the tiers are on pricing.
What a migration off DreamHost looks like
A single WordPress site moves in a few hours of real work, most of which is testing rather than copying. Here is the order we use.
First, inventory. Domains, where each one is registered, where DNS is hosted, every mailbox, every SSL certificate, and every plugin license with its renewal date. Registrar and DNS are often not at the same company as the hosting, and people get this wrong.
Second, lower your DNS TTL to 300 seconds a day before the cutover. This makes the switch fast if something needs reverting.
Third, copy the site to staging on the new server. Run it on a current PHP version there and watch for fatal errors. This is where the reason for that legacy PHP fee finally shows itself, usually as one plugin throwing an error on one page.
Fourth, test the parts that make money. Contact forms, the checkout, the booking calendar, any integration that posts data somewhere else. Send a real test lead and confirm it lands in the inbox.
Fifth, switch DNS. Keep the old account alive for 30 days so you have a fallback, then cancel it before the next renewal date rather than after. If something looks broken in the first hour, check DNS and SSL before assuming anything worse. Our triage order is in check DNS before you assume your WordPress site was hacked, and the full process is in our WordPress migration guide.
We do all of this as part of onboarding. You send credentials, we build staging, you approve, we cut over.
A checklist before you cancel your old host
- Confirm your domain registrar and note whether the domain is locked.
- Save the auth code for any domain you plan to move later.
- Export mailboxes before the account closes. Email loss is the most common regret in a host move.
- Screenshot your current plugin licenses and renewal dates.
- Note the renewal date on the hosting account and set a reminder two weeks before it.
- Ask the new host, in writing, who owns updates, backups, malware cleanup, and PHP upgrades.
- Keep the old account active for 30 days after cutover, then cancel.
That last one is the difference between a calm migration and a stressful one. Redundancy for a month costs less than one emergency.
If you run more than a handful of sites, the same audit applies at a larger scale, and the savings compound. Our case studies include agencies and enterprises that consolidated fleets of 100 to 740 sites onto one bill. For a single business site, start with the invoice audit above. It answers the question in an afternoon.
Frequently Asked Questions
Does DreamHost really charge a fee for running an old PHP version?
DreamHost documents a recurring charge for keeping a site on a PHP version that has reached end of life. The amount and the affected versions change over time, so check your own invoice and panel for the current line item rather than trusting a third-party figure.
Why did my DreamHost bill go up when my plan did not change?
Most increases come from a promo term ending, an add-on renewing at full price, or a new per-site charge like legacy PHP support. Download 12 months of invoices and compare line items month by month. The difference is almost always a specific row, not a general increase.
Will moving hosts break my email?
It can, if your mailboxes live on the hosting account you are cancelling. Export every mailbox first and decide where email will live before you touch DNS. Many businesses move mail to a dedicated provider during the migration so hosting and email are no longer tied together.
How long does a migration off DreamHost take?
For a typical WordPress site, the copy takes under an hour and testing takes a few more. DNS propagation is usually minutes if you lower the TTL first. TopSyde handles migration as part of onboarding at no extra charge, including PHP compatibility testing on staging.
What if my site only works on old PHP?
Then something on it is unmaintained, and that is worth finding out about. We run the site on a current PHP version in staging, identify the plugin, theme, or custom function that fails, and patch or replace it. Paying monthly to stay on a dead version leaves the underlying problem in place.
Senior WordPress Engineer
8+ years WordPress & WooCommerce development
Rachel is a senior WordPress engineer at TopSyde specializing in WooCommerce performance and plugin architecture. She has built and maintained high-traffic e-commerce sites processing millions in annual revenue.
