Hetzner Webhosting for WordPress, pricing and migration

Who Hetzner may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

German, English, French and Spanish.

Control panel

konsoleH. French interface coverage to be confirmed.

Support

Tickets through konsoleH and phone advertised for XL. French support to be confirmed.

Hetzner Webhosting for moving a WordPress site

Webhosting provides a managed shared web environment with konsoleH, PHP, databases, email and backups. Hetzner also sells Cloud servers and managed servers with separate scopes. Their prices and support follow their own tables.

A fictional Lyon association wants to leave its old host. Its small site presents drop-in hours, a form and a contact link configured by a plugin. Migration creates a verification environment with a temporary address. The page may look intact while a database setting still redirects to the original site. The goal is to retrieve a readable option after modification and confirm that the source remains available until transfer validation.

Plan selection therefore concerns three concrete elements: enough capacity to import files and the database, access suited to the migration method and a rollback procedure that restores modified elements together. A team with a local workstation can prepare and verify the address change before import. A team wanting to run commands on hosting must check SSH access and features available for its plan.

Reconstruct the initial invoice and later charges

The November 10, 2026 review concerns the international table in euros excluding VAT. Monthly caps for S, M, L and XL are €1.60, €4.12, €8.32 and €16.72 respectively. Hourly rates displayed in the same order are €0.0026, €0.0066, €0.0133 and €0.0268. All four cards show setup fees currently reduced to €0. The crossed-out amount is €8.32 for S and €4.12 for M, L and XL. Check setup when ordering. Crossed-out amounts refer to one-off fees, separated from usage prices in the table.

Hetzner advertises no minimum duration and describes billing after use. For a partial month, the hourly rate applies up to the monthly cap under billing terms. The billing schedule and threshold may combine several periods on one invoice. No introductory promotional price or separate renewal table was identified for these four plans. Budgets for later periods therefore use the current rate, subject to price changes. The annual domain follows a different deadline.

For M, one full month of hosting alone costs €4.12 excluding VAT in the review. With a domain bought elsewhere and linked to the account, add €0.64 excluding VAT per domain per month, totaling €4.76 excluding VAT for hosting and one such link. The registrar’s cost remains separate. A domain ordered from Hetzner starts at €4.90 excluding VAT per year depending on extension. The technical comparison also specifies €0.77 excluding VAT per additional GB per month for overages. In the French example without a valid intra-community VAT number, documentation displays 20% VAT. This gives approximately €5.71 including VAT on the €4.76 excluding-VAT item, excluding the registrar invoice. Cases with a valid number follow Hetzner’s documented billing rules. The review is in EUR. The selector also offers USD and a country choice.

Choose a plan by limits and required access

Reference points taken from the offer cards. — Illustration by BlogPasCher.Open full-size illustration ↗

S advertises 10 GB, one database, two PHP processes and a PHP memory limit of 192 MB. M raises these to 50 GB, five databases, five processes and 256 MB. L advertises 100 GB, twenty databases, ten processes and 384 MB. XL displays 300 GB, fifty databases, twenty processes and 512 MB. Documentation specifies PHP execution times of 120, 180, 240 and 360 seconds. These are a per-script allowance and a process count, useful for identifying risk during imports or concurrent visits. PHP memory is not memory dedicated to the entire installation.

All four plans advertise Varnish. L and XL add SSH and Redis. The XL card also specifies phone support. For the association site, M allows a site database and a verification database in the same account, subject to a domain or access suited to checking. S may fit if testing and rewriting the copy occur elsewhere before import and the site database fits the allowance. L is worth examining if the team must run WP-CLI on hosting or an operation needs a larger PHP allowance. Check SQL file size, media directories, email share and upload limits before deciding.

A domain remains necessary for several web and email functions. The FAQ specifies that the technical your-vhost.de address is not a preview for a customer site. Verification before switchover can be performed locally or with a domain configured for that purpose. Record the linked domain and its corresponding file root. Establish required web and email DNS entries before any intervention.

Divide administration between Hetzner and the WordPress team

Hetzner administers the web platform, including the system, email service and web server, and supplies konsoleH. The product page advertises one-click WordPress installation. The team retains responsibility for application security settings, plugins and testing before production. During transfer, it must first choose between importing its existing installation’s database and files or creating a new installation. Writing a new installation into the root intended for the copy complicates diagnosis. Prepare an empty database, create its user, then verify that WordPress configuration points to the correct server, database and prefix.

Administration of installed WordPress remains work to allocate. The association controls accounts, permissions, theme, plugins, application updates and form behavior. The team distinguishes a platform outage from a plugin-specific setting. For a form, test with fictional data, verify the expected record and intercept sending in the verification environment. Then check that the contact page no longer sends visitors to the old temporary address, and restore appropriate receiving settings when the validated site becomes public.

For an address change, knowing available access is enough to choose the method. A team with WP-CLI processes a database copy through the command line. On a plan without SSH, it can perform this on its workstation and then import the database through the panel after checking versions and engine. Whichever route is used, retain an initial SQL file and record targeted tables. This copy allows work to restart if the change affects an unexpected option.

Verify a database address change locally

A WordPress value may contain a serialized PHP array with string lengths in bytes. Replacing an address in an SQL file using an editor can lengthen the address without updating that length. The site may load its home page yet lose the contact setting. The PowerShell script in the ZIP under “Prepare your site” creates an isolated local WordPress and writes a fictional option with a nested address. It also prepares a sample page whose GUID serves as a control. Both addresses end in example.test. No provider site or public DNS is involved.

In the negative test, PHP replaces a short address with a longer one in the raw representation. Unserialization fails. The WordPress workflow then uses WP-CLI in dry-run mode to count replacements. The option must retain its original address after this step. During the write pass, the option must retain its other content, the link must point to the destination and the page GUID must remain unchanged. A final dry run looks for remaining occurrences within the same scope. The script then restores the initial database copy and verifies the original link.

On an isolated copy of a real site, explicitly specify the destination path. Use wp --path=CHEMIN_CIBLE search-replace ANCIENNE_URL NOUVELLE_URL --precise --skip-columns=guid --dry-run, with complete URLs. After reviewing affected tables and keeping a database copy, rerun the command without the final flag. For plugins creating their own tables, verify inclusion before widening the search. Check the result with a plugin setting and a sample page. If it differs, restore the working database and correct scope. To confirm terminal context, follow “WP-CLI targets the wrong WordPress: check the server, directory and site.”

Match file and database restore points

Hetzner advertises nightly backups retained for fourteen days in a separate center for Webhosting. In konsoleH, select the account, then Services and Backup. The guide allows selecting files or directories and restoring to a new directory or their original location. It separately describes database restoration to a new database or by overwriting. On S, with one included database, prepare a test destination outside the account if the quota prevents another. If the team is unsure about the copy, choose a new directory and database using available resources. Record both points’ names, times and scopes before reconnecting the site.

For the association, consistency is checked through a photo, contact page, form and reference entry. A Monday media directory and Wednesday database may point to files absent from the copy. Restoring only the database may also reintroduce an old plugin setting. After an update modifying files and data schema, select compatible states. Keep a record of operations between the copy timestamp and restoration time.

The local test restores the database without reinstalling demonstration WordPress. Real recovery combines correct files, database and destination settings. If requests arrived after the selected point, determine how to handle them separately before a general restoration. Keep an SQL export and files in a location separate from the account, with restricted access. To choose a method suited to scope, use the selection “WordPress migration, staging and imports: choose the right tool.”

Prepare departure and define support and AI scope

The commercial site offers German, English, French and Spanish versions. Consulted technical documentation exists in German and English in particular. French offer and contract versions make terms easier to read. Languages available across all konsoleH functions and written French support remain to be confirmed. The contract provides for written support through konsoleH, and the commercial table reserves the phone indication for XL. Data-center coverage hours cited in the help center concern particular services. Use the selected Web plan’s channel to arrange intervention.

The contract describes transfer service limited to certain internal accounts. For a site from another host, the team prepares migration and requests separate intervention if it wants to delegate it. Export files and databases, then record mailboxes, redirects and DNS entries. Test access to the new site and email before deleting the old account. Cancellation in konsoleH separates hosting decisions from domain decisions. The guide warns that canceled-product data can no longer be retrieved. The domain can be kept or transferred according to the chosen workflow.

No included WordPress site generator or AI credits were identified in the consulted Webhosting S to XL cards. Any provider assistance tool and third-party plugins have their own scopes. If the association wants a generative tool, treat its license, received data and content portability as independent of hosting price. Migrating the contact option depends on none of these services.

Decide before changing DNS

The choice is made before modifying the DNS zone. For a simple site, M may fit if testing is prepared on a workstation and the copy stays within limits. It provides more database-count headroom than S. L provides SSH when the team must run the procedure directly on hosting. Choose the plan for an observed need, such as import method or process count, and recurring cost with the domain. Account for separate domain billing even if the association simply wants to keep its registrar.

Before changing DNS, the association records access points for the copy and previous site. It compares visible URLs on reference pages, opens a recent image, checks administration login and submits a form to a test recipient. The browser padlock must correspond to the domain that will actually be used. For this check, follow “The HTTPS certificate does not cover your WordPress domain: fix the name and destination.”

Timing must also limit divergence between the two sites. If the form stays open on the old instance during propagation, agree on a freeze interval or a way to collect requests still arriving there. Keep previous DNS entries and a usable initial copy. If the new form fails or a setting still points to the wrong place, return to the source using the prepared procedure and retain information that may have entered the destination. DNS delays may postpone the effect, and data collected on both sides must be reconciled. Rollback becomes verifiable when the expected site responds and a sample request reaches the correct recipient.

After switchover, retain results and the quote actually applied. Monitor recurring hosting, domain and any additional fees. The skill needed is the ability to manipulate a WordPress copy and explain what is being restored. These conditions are separate from Hetzner’s server operations. If the team delegates migration, specify who checks the database, validates DNS and retains exports before closure.

In the French version, public HTML displays €1.92, €4.94, €9.98 and €20.06 per month including 20% VAT for S through XL. These caps provide a second reference for a French quote. A complete month can therefore be compared on the same tax basis while keeping setup, domain and options separate.

Prepare your site

• WP-CLI targets the wrong WordPress: check the server, directory and site
• WordPress migration, staging and imports: choose the right tool
• The HTTPS certificate does not cover your WordPress domain: fix the name and destination
• Download the WordPress exercise (ZIP)