Hetzner vs DigitalOcean for WordPress hosting

We move WordPress sites onto Hetzner and DigitalOcean most weeks, so this is not a spec-sheet comparison written from the two providers’ pricing pages. It is what actually changes for a WordPress site once it lives on one box or the other. Every “Hetzner vs DigitalOcean” article ranking today compares raw vCPUs, bandwidth, and dollar figures. Almost none of them mention that WordPress does not run itself on either one, and that omission is what this post is about.

Short version: for a single WordPress site where the monthly bill matters, Hetzner gives you two to three times the CPU and RAM per dollar and does not charge you for traffic until you are well past what a normal site pulls. DigitalOcean costs more for the same specs but has more datacenters near more customers and a bigger ecosystem of managed add-ons. Neither of them is managed WordPress hosting, and that is the part people get wrong.

Both give you an empty Ubuntu box, not a WordPress host

This is the sentence that saves people the most grief. When you spin up a Hetzner CX server or a DigitalOcean droplet, you get a bare Linux machine with an IP address. No control panel, no PHP tuned for WordPress, no caching, no automatic backups you would actually trust, no firewall rules beyond the defaults. Managed WordPress hosts like Kinsta or WP Engine hand you a running site and charge $30 to $300 a month for the babysitting. Hetzner and DigitalOcean hand you the keys to an empty room.

So the real comparison is not Hetzner vs DigitalOcean. It is “who sets up and maintains the server.” If that is you, both providers are fine and the rest of this post helps you pick. If it is not you, you need either a managed host or someone on retainer to run the box. We do the second for a flat monthly fee, which is usually cheaper than managed hosting once you have more than one site.

Price and performance: Hetzner wins, and it is not close

On pure price-to-performance, Hetzner is the cheaper machine by a wide margin. A Hetzner CX or CPX server with 2 vCPU and 4 GB of RAM sits around 4 to 6 EUR a month. The nearest DigitalOcean droplet with the same memory runs roughly two to three times that. For a WordPress site that means the difference between a box that never sweats under WP-Cron, image processing, and a couple of plugins, and a box you have to keep nudging. Front-end scripts weigh in here too; see Google Tag Manager without wrecking your Core Web Vitals.

The bandwidth gap is even wider and it catches people out. Hetzner includes 20 TB of traffic on most cloud plans. DigitalOcean gives each droplet a slice of pooled transfer, and once you cross it you pay per gigabyte. A brochure site never notices. A WooCommerce store running a sale, or a media-heavy site that has not put a CDN in front of its images, absolutely notices. We have seen DigitalOcean overage lines that quietly doubled a hosting bill because nobody put Cloudflare in front of the origin.

Where DigitalOcean earns its higher price is the ecosystem around the droplet. Managed Postgres and MySQL, object storage that behaves like S3, load balancers, a mature API, and a marketplace of one-click stacks. If your WordPress site is one piece of a larger application, that matters. If your WordPress site is the whole thing, you are paying for a buffet you will not eat.

Where the servers physically sit

Latency to your visitors is set by which datacenter you pick, and this is the one category where DigitalOcean has the broader map. DigitalOcean runs regions in New York, San Francisco, Toronto, London, Amsterdam, Frankfurt, Bangalore, Singapore, and Sydney. Hetzner has fewer: Germany and Finland in Europe, plus US sites in Ashburn, Virginia and Hillsboro, Oregon, and a location in Singapore.

For most WordPress sites this decides less than you think, because a properly configured site serves cached HTML and pushes static assets to a CDN edge anyway. Pick the region closest to the bulk of your readers, put Cloudflare in front, and the origin’s exact city stops mattering for page speed. If your audience is spread across Australia and South America, DigitalOcean’s map gives you more options. If it is Europe and North America, Hetzner covers you fine. The bigger speed lever is the caching plugin you put on top and whether the host runs LiteSpeed.

Backups and snapshots: read the fine print

Both providers sell snapshots and scheduled backups, and both charge roughly 20 percent on top of the server price for automated backups. That number is not the interesting part. The interesting part is that a provider snapshot is a full-disk image, not a WordPress backup. Restoring one brings back the entire machine to a point in time, which is great for “I broke the server” and useless for “I need last Tuesday’s version of one post.”

We never rely on the host’s snapshot alone. On every WordPress box we run, we layer an application-level backup on top so the database and the uploads can be restored independently of the disk image. The provider snapshot is the seatbelt; the WordPress backup is the airbag. If you want the long version of why one is not a substitute for the other, we wrote it up in the WordPress backup strategies post, including the failure modes we see on emergency restore calls.

The stack we actually install on both

Because neither provider tunes anything for WordPress, the setup work is identical whether you land on Hetzner or DigitalOcean. Here is what goes on the box before a site is production-ready:

• A control panel so you are not editing configs by hand for every change. We run CyberPanel with LiteSpeed on most WordPress servers because LSCache is built in and the memory footprint is lower than an nginx and PHP-FPM stack at the same traffic.
• PHP tuned for WordPress: sane memory limits, OPcache on, upload sizes that match the media library.
• Server-level caching plus a CDN in front, so the origin serves cached pages and the datacenter’s exact location matters less.
• A firewall, fail2ban, automatic security updates, and locked-down SSH. A fresh droplet or CX server is exposed the moment it boots.
• Application backups running on a schedule, tested by an actual restore, not just a green checkmark.

None of that is exotic. It is a day of work done right, or an afternoon of work done badly that comes back as a support ticket in three months. This is also why the underlying provider is the smaller decision. A well-run WordPress box on DigitalOcean beats a neglected one on Hetzner every day, and the reverse is just as true.

Support and reliability

DigitalOcean has the friendlier front door: enormous documentation, community tutorials for nearly every task, and paid support tiers if you want a human. Hetzner’s documentation is thinner and its support is more “the server works, figure out the software yourself,” which is exactly what you would expect at the price. On raw uptime both are solid; Hetzner’s old reputation for being flaky is a decade out of date, and their hardware has been dependable in our experience.

The honest read is that neither company’s support will fix your WordPress site, because your WordPress site is not their product. They keep the machine online. Everything above the operating system is on you or on whoever you hire. That is the same on both, so it should not swing your decision.

So which one

Pick Hetzner if the monthly cost matters, your audience is mostly in Europe or North America, and you want the most CPU, RAM, and bandwidth for the money. That covers the majority of single WordPress sites and small WooCommerce stores we migrate. Pick DigitalOcean if you want datacenters close to a globally spread audience, or your WordPress install lives next to a larger application that will use managed databases, object storage, or load balancers. Paying more for that ecosystem is reasonable when you will actually use it.

What should not decide it: which logo you have seen more often, or which one a random benchmark says is 8 percent faster on a synthetic test. WordPress performance is set by the stack and the caching, not by the last few percent of raw hardware. Get the server configured properly and either provider will carry a normal site without complaint.

If you would rather not build and babysit the box yourself, that is what we do. We set up WordPress on Hetzner or DigitalOcean, harden it, wire up caching and backups, and keep it running on a flat monthly fee through our managed VPS onboarding. Tell us where your audience is and what the site does, and we will tell you which provider we would put you on and why. If you are moving off shared hosting for the first time, start with our guide on migrating from shared hosting to a VPS, then come back to this decision.

The host is only half the decision; the other half is managed hosting versus a cheap self-run box.

If AWS is in the mix, the calculus shifts. We compare a managed AWS box against a plain rented server in AWS Lightsail vs a $5 VPS, including where the bandwidth bill bites. Whichever you pick, if you are migrating off a managed host the platform code has to come out cleanly, which is the heart of moving a site off WP Engine.