Hetzner offers two workable routes to a WordPress site: a managed Webhosting plan where you launch WordPress from the hosting panel, or a Cloud server where you either boot a prebuilt WordPress app or build the stack yourself. Choose Webhosting if you want Hetzner to run the server and you would rather not touch a command line. Choose Cloud if you need root access and accept responsibility for updates, backups, and hardening.
What "Hetzner WordPress Hosting Setup" Can Mean
The phrase covers two very different products, and mixing them up is the most common reason people get stuck.
Hetzner Webhosting is a managed plan. You get a hosting panel, a web space, and a one-click installer. You pick a directory, click Install, and WordPress appears. Server maintenance sits with Hetzner.
Hetzner Cloud gives you a virtual server you administer. You can start from Hetzner's WordPress app, which ships Apache, MySQL, and WordPress preinstalled, or you can install a web server, database, and PHP yourself.
A one-line rule helps: if you do not want to administer a server, take Webhosting. If you need root access and will handle maintenance, take Cloud.
Before You Start
Both routes assume a few things are already in place.
- A Hetzner account with billing set up.
- A domain you control, plus access to its DNS settings at your registrar.
- For the Cloud route, basic comfort with SSH and a terminal.
- A decision on whether you want a managed panel or full server control.
The DNS step matters on both paths, but the exact record values depend on your Hetzner product and the IP or hostname Hetzner assigns you. Check the details in your Hetzner panel before editing DNS at your registrar, because a wrong record will leave the site unreachable even when WordPress itself is installed correctly.
Route A: WordPress on Hetzner Webhosting
This is the shorter path, and it stays inside the browser.
- Open your Webhosting product in the Hetzner hosting panel.
- Choose the directory on your web space where WordPress should live, such as
/wordpressor the main directory. - Start the installation from the panel by clicking Install, using the provided one-click installer or Softaculous.
- Follow the installer prompts to finish the site setup.
The supplied Hetzner guidance covers the directory choice and the Install action. The remaining installer screens and the exact credential flow are managed by the installer itself, so follow what the panel shows rather than a fixed script.
After installation, confirm you can reach the WordPress login page at the address tied to the directory you chose. If you installed into /wordpress, the site lives at that subpath until you change it.
Route B: WordPress on a Hetzner Cloud Server
The Cloud route gives you a server you control. The fastest version uses Hetzner's prebuilt WordPress app.
Create the Server with the WordPress App
When you create a server in the Hetzner Console, you can choose the WordPress app instead of a plain image, so it is preinstalled on the new server. The app bundles a ready-to-use WordPress installation with MySQL and Apache2.
You are not limited to the Console. The same app can be deployed through the Hetzner Cloud API. That matters if you want repeatable, scripted provisioning rather than clicking through a form.
WordPress is one of several apps in the Hetzner Cloud Apps catalog, alongside options such as Docker CE, GitLab CE, Nextcloud, and a LAMP stack.
Enable WordPress After the Server Boots
The app image is not a finished site on first boot. WordPress is preinstalled when the image boots, but it is not enabled until you complete the setup.
To enable WordPress and create your admin user, log into the server over SSH using the SSH key you selected, or the root password that was mailed to you. Then run the provided setup routine and follow its prompts. This is also where the setup script offers Let's Encrypt support for HTTPS.
The app uses auto-generated passwords stored at /root/.hcloud_password, so retrieve them from that file rather than guessing. The image itself is based on Ubuntu 24.04 and packages Apache, MySQL, several PHP extensions, and WordPress from source.
Manual Install on a Cloud Server
If you skip the app and build the stack yourself, you take on more decisions. A manual WordPress install needs a web server, a database server, and PHP.
On Ubuntu, a common combination is Nginx, MariaDB, and PHP-FPM installed through apt. Before installing any software, update the system packages first; that is standard practice on a fresh VPS. Older tutorials exist for this route, but commands can drift between Ubuntu releases, so check them against the version you actually deployed.
Prebuilt App vs Manual Install
| WordPress app | Manual install | |
|---|---|---|
| Web server | Apache, preinstalled | Your choice, e.g. Nginx |
| Database | MySQL, preinstalled | Your choice, e.g. MariaDB |
| PHP | Several extensions included | Installed and configured by you |
| WordPress | From source, needs enabling | Downloaded and configured by you |
| Setup effort | Lower | Higher |
| Control | Constrained by the app's layout | Full |
The app shortens the path to a working site but leaves you with its choices. A manual install costs more time and gives you a stack built to your own preferences.
Enabling HTTPS with Let's Encrypt
Let's Encrypt provides the digital certificates needed to enable HTTPS (SSL/TLS) for websites. The Hetzner WordPress setup script offers Let's Encrypt as an option during setup.
If you skip it then, you can still activate it later. Run Certbot, which is preinstalled, with the Apache plugin, then restart Apache.
Two practical notes. Certificates are tied to the domain name, so point DNS at the server before requesting one, or validation will fail. And because certificates expire, renewal has to keep working; Let's Encrypt certificates are short-lived by design, so confirm the renewal job is scheduled after setup.
Backups, Sizing, and Post-Install Checks
A working WordPress site is not the same as a protected one. A few items deserve attention right after install.
Server size. SpinupWP recommends at least 2 GB of memory for production servers hosting WordPress sites. That is one vendor's guidance rather than a Hetzner rule, but it is a reasonable floor for a small production site. Hetzner servers can be resized to a larger plan later from the dashboard, though the server goes offline while it resizes.
Backups. Hetzner offers optional Auto Backups as an add-on for an additional monthly fee, billed by Hetzner. These are server-level backups. They are not the same as site-level backups that capture site files and the database rather than the whole server. Treat them as complementary: a server image can restore the machine, while a site backup lets you roll back content or a database without touching the rest of the system.
Post-install checklist.
- WordPress enabled and the admin user created.
- HTTPS active and the certificate renewing.
- Backups configured, with a clear idea of what they do and do not cover.
- Server memory adequate for the site.
- Admin passwords retrieved from
/root/.hcloud_passwordand changed to your own.
Ongoing maintenance. Keep WordPress core, themes, and plugins current, and remove anything you are not using. The exact update workflow depends on your setup, so follow your host's or management tool's guidance rather than a generic script.
Optional: a Management Layer on Top of Cloud
If you want Cloud servers but not the manual stack work, a third-party tool can sit between you and Hetzner. SpinupWP provisions Hetzner servers with Nginx, PHP-FPM, and Redis for WordPress hosting. Provisioning through it takes around 10 minutes, and you get an email when it finishes.
This is not a native Hetzner path. It is a separate product with its own cost and its own opinions about your stack, so evaluate it as a tool rather than as part of Hetzner's offering.
When Self-Managed Setup Is the Wrong Choice
The Cloud route is a good fit if you want root access, plan to run multiple sites, or need control over the stack. It is a poor fit in a few common situations.
- You have no interest in SSH, package updates, or server logs. Webhosting removes that work.
- You need a site live today and cannot spend time on stack configuration. The one-click installer is faster.
- You will not maintain backups and updates. A self-managed server without either is a liability, and server backups alone do not cover site-level recovery.
- You are unsure about server sizing and do not want to plan for resize downtime.
In those cases, the managed plan or a managed layer over Cloud is the more honest choice than a server you will not maintain.
Choosing Your Path
The decision comes down to who administers the machine. Hetzner Webhosting puts that work on Hetzner and gives you a panel-driven install. A Hetzner Cloud server puts it on you, with the WordPress app as a shortcut that still requires you to log in and enable the site.
Pick the managed route if you want a site, not a server. Pick Cloud if you want control and will fund the time and backups that come with it. Either way, point DNS before requesting certificates, verify HTTPS and backups after install, and revisit sizing once you know how the site actually performs.


