Hetzner for WordPress Beginners: Hosting or VPS First?

Hetzner for WordPress Beginners: Hosting or VPS First?

Most WordPress beginners should start with Hetzner web hosting, not a cloud server. Web hosting gives you a control panel with a one-click WordPress installer and no server administration. Choose a Hetzner cloud server only if you are willing to log in over SSH, enable the prebuilt WordPress app yourself, and take responsibility for updates, backups and security.

That recommendation is editorial judgment. Hetzner's own documentation explains both products but does not name one as the beginner pick. The real dividing line is simple: who administers the server.

What Hetzner Actually Offers for WordPress

Hetzner gives you two practical routes, and they feel very different to a first-time site owner.

Web hosting is the shared-hosting product. You manage content through a user-friendly interface, and Hetzner states that no programming knowledge is required. WordPress is one of the content management systems Hetzner publishes installation guides for. In practice, you install WordPress from the hosting panel using a one-click installer such as Softaculous, and you choose the directory it lives in, such as /wordpress or the main directory.

Cloud servers are virtual machines you administer yourself. Hetzner offers a prebuilt WordPress app image that contains a ready-to-use WordPress installation including MySQL and Apache2. The image is based on Ubuntu 24.04 and bundles Apache, MySQL, several PHP extensions and WordPress from source. You create the server through the Hetzner Console or the Hetzner Cloud API.

The cloud route is more capable and more work. Nobody configures the stack for you beyond the initial image, and everything after that is your job.

How to Choose Between Them

Ask yourself one question: will you run commands over SSH and own server maintenance?

If the answer is no, start with web hosting. You get a panel, an installer and a WordPress site without touching a terminal.

If the answer is yes, or you genuinely want to learn, the cloud WordPress app is a reasonable first server. You will still need to enable WordPress, create your admin user and handle security yourself.

A few practical signals point to each side:

Factor Web hosting Cloud server (WordPress app)
Install method Panel one-click installer Boot app image, then complete setup over SSH
Server administration Handled by the host Yours
SSL Provided through the hosting setup Let's Encrypt during setup or later with Certbot
Backups Host-dependent Optional Auto Backups add-on, plus your own site backups
Best for Non-technical first site Readers comfortable with a terminal

Sizing a First Cloud Server

For a self-managed production server, SpinupWP recommends at least 2 GB of memory. That figure comes from SpinupWP's own provisioning workflow, not from Hetzner, so treat it as a sensible floor rather than an official requirement. You can upgrade a Hetzner cloud server to a larger size later from the dashboard, but the server goes offline while it resizes.

If you plan to run a web shop, Hetzner recommends its Webhosting XL plan. That points to web hosting as the simpler path for commerce on a first site.

Before You Install: Domain and DNS

You need a domain name pointed at your Hetzner setup before WordPress can go live on a real address. The exact DNS steps depend on your registrar and on whether you use Hetzner's DNS service, so follow the instructions provided by whichever service holds your domain. Have the domain ready, and know where its DNS records are managed, before you start the install.

For SSL, the cloud WordPress app offers Let's Encrypt support during setup. If you skip it, you can activate Let's Encrypt later by running Certbot with the Apache plugin.

Installing WordPress on Hetzner Web Hosting

This is the shorter path.

  1. Log in to your Hetzner hosting panel.
  2. Open the installer, such as Softaculous or another one-click option.
  3. Choose the directory for WordPress, either /wordpress or the main directory.
  4. Start the installation and complete the WordPress setup screens.
  5. Point your domain at the hosting space and enable SSL through the panel.

Hetzner publishes a dedicated tutorial for this process, and it is worth following alongside the panel, since button labels can change.

Installing WordPress on a Hetzner Cloud Server

The official app image does most of the heavy lifting, but it does not finish the job for you.

  1. Create a cloud server and select the WordPress app image in the Hetzner Console or via the Cloud API.
  2. Note the server's IP address once it is running.
  3. Log in to the server over SSH using your SSH key, or with the root password Hetzner emails you if you did not select a key.
  4. Complete the setup so WordPress is enabled and your admin user is created.
  5. When prompted, activate Let's Encrypt for HTTPS, or run Certbot with the Apache plugin afterward.

If you need a database password, the app image stores auto-generated passwords in /root/.hcloud_password. Keep that file private.

A third option exists for readers who want a managed layer on top of a Hetzner server. Tools such as SpinupWP provision a Hetzner server with a stable stack of Nginx, PHP-FPM and Redis, and provisioning takes around 10 minutes. That approach sits between raw cloud and shared hosting, and it is worth knowing about if you later outgrow the panel.

SSL, Site Address and First-Run Settings

Once HTTPS is active, check that WordPress knows about it. After installing WordPress on a Hetzner cloud server with Nginx and Certbot, the WordPress Address and Site Address settings should be changed to start with https. You will find these under Settings, then General.

Then work through a short first-run checklist:

  • Confirm your admin account uses a strong, unique password.
  • Set permalinks to a readable structure such as post name.
  • Verify the site loads correctly over https with no mixed-content warnings.
  • Install only the plugins you actually need.

Backups, Updates and What You Own After Launch

This is where the two routes diverge most.

Hetzner offers optional Auto Backups for cloud servers as an add-on for an additional monthly fee, billed directly by Hetzner. These are server-level backups. They are not the same as application-level site backups that capture your WordPress files and database rather than the whole server. If you run a cloud server, plan for both: the Hetzner add-on for disaster recovery, and a WordPress-level backup routine for your content.

On web hosting, backup and restore options depend on your plan and panel, so confirm what is included before you rely on it.

Either way, a self-managed cloud user owns the ongoing work: operating system updates, WordPress core and plugin updates, security hardening, monitoring and backup verification. Hetzner's documentation covers the initial WordPress app setup, not a full maintenance program, so build your own routine.

Common Beginner Mistakes

  • Skipping the cloud app setup. WordPress is preinstalled when the image boots but not enabled, so the site will not work until you log in and complete setup.
  • Assuming server backups cover WordPress. Server-level Auto Backups and site-level backups solve different problems.
  • Choosing a cloud server without SSH skills. If a terminal login feels daunting, web hosting removes that step entirely.
  • Forgetting the HTTPS switch. Leaving the WordPress and Site Address on http after installing a certificate causes redirect and login problems.
  • Picking a server that is too small. The 2 GB memory guidance is a floor for production, and resizing takes the server offline.

When a Simpler Host Is the Better First Step

Hetzner web hosting is already the low-administration option within Hetzner, and it is the right starting point for most beginners. If even a hosting panel feels like more control than you want, a fully managed WordPress host removes server and panel administration altogether. That trade-off usually costs more and gives you less flexibility, but it is a legitimate choice for a first site where your priority is publishing, not infrastructure.

If you are unsure, start with web hosting. You can always move to a cloud server later, once you know your traffic, your comfort with the command line and what you actually need to control.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top