Reinstalling WordPress in Hostinger is safe when you first protect the database, files, and domain settings. The safest method depends on the problem: reinstall WordPress core when the installation is damaged, or remove and rebuild the site only when you have a complete backup and want a clean start.
Before changing anything, review the main hosting controls so you know where your files, database, and domain settings are located.
Choose the right type of WordPress reinstall
There are three different tasks that people call a WordPress reinstall. Picking the wrong one can delete a working site.
- Reinstall WordPress core: This replaces WordPress system files while keeping your posts, pages, media, themes, plugins, and database content. Use it when core files are missing or corrupted.
- Reset the WordPress site: This removes the site’s content and settings while leaving the hosting account in place. Use it when you want to start again on the same domain.
- Delete and rebuild the installation: This removes WordPress files and its database. Use it only for a complete restart, after saving everything you may need.
A core reinstall is usually the safest answer for a broken dashboard, damaged files, or a failed update. A full rebuild is more suitable for a test site, an abandoned installation, or a site that has been compromised and needs a controlled restart.
Do not delete the database because WordPress will not load. The database contains your posts, pages, user accounts, settings, comments, and other site data. Removing it before a backup can make recovery much harder.
What to save before changing WordPress
A safe reinstall starts with two separate backups: the site files and the database. Saving only one of them leaves part of the site unprotected.
Save the WordPress files
Use Hostinger’s file manager or an FTP client to download the WordPress files. The site’s main folder often contains files such as wp-config.php, .htaccess, and folders including wp-content, wp-admin, and wp-includes.
The wp-content folder deserves special attention. It normally contains your uploaded images, active themes, installed plugins, and other custom files. Keep a separate copy even if you plan to reinstall the whole site.
Save wp-config.php as well. It contains the database name, database user, password, and server details that connect WordPress to its database. Remove or protect that file if you store the backup on a shared computer.
Export the database
Open the database management area supplied by Hostinger and export the database used by the site. If the panel lists more than one database, check wp-config.php for the database name before exporting.
Keep the database export in a safe location. A full backup should include both the SQL database file and a copy of the WordPress files. If the site has recent orders, form entries, or user registrations, take the backup during a quiet period and confirm that the export completed.
Record settings that are easy to forget
Write down the following details before the reinstall:
- The website address and preferred version, such as HTTPS.
- The names of active themes and plugins.
- Custom email addresses and SMTP settings.
- DNS records for email, verification, and third-party services.
- Any custom code added to
wp-config.php,.htaccess, or a theme. - Administrator usernames and recovery email addresses.
WordPress documentation at the official WordPress site is useful for checking core files and backup concepts before you begin.
How to reinstall WordPress core in Hostinger
Reinstalling the core is the least destructive option because it replaces WordPress system files without intentionally removing your site content. Take a backup first, even though this method is designed to preserve the database.
- Check the site address. Confirm that the domain opens at the correct Hostinger account and that you are working on the intended installation.
- Back up the files and database. Save both copies outside the hosting account before making changes.
- Open the WordPress administration area. If the dashboard loads, look for the WordPress update or maintenance area and follow the on-screen prompt for reinstalling the current WordPress files.
- Wait for the process to finish. Keep the browser open until WordPress reports that the operation is complete.
- Check the front end. Open the home page, several posts, the media library, and the login page.
- Review plugins and themes. If the problem returns after activating one item, deactivate it and test again.
If the dashboard does not open, use Hostinger’s matching WordPress or application management area, if available, and follow the displayed instructions. The exact controls can vary by account and installation type, so avoid deleting files based on a guessed menu name.
Another option is to replace the core files manually while keeping wp-content and wp-config.php. This requires care. Never overwrite your custom files without checking them first, and never remove the database during a core-only repair.
How to perform a full clean reinstall
A clean reinstall removes the old WordPress installation and creates a new one. It is appropriate when the site is disposable, badly misconfigured, or being rebuilt from a known-good backup.
- Put the site into maintenance mode. Tell visitors that the site is being worked on, especially if it handles orders, memberships, or submissions.
- Save a complete backup. Keep the database export, WordPress files, media, and any custom configuration in separate storage.
- Confirm the domain and document root. Make sure the folder you plan to remove belongs to the correct website, not another site under the same hosting account.
- Remove the old WordPress files. Use the file management area or the method shown in Hostinger’s documentation. Do not remove unrelated folders.
- Remove the old database only when rebuilding from scratch. If you plan to restore the existing site, keep the database until the new installation has been tested.
- Create a fresh WordPress installation. Use Hostinger’s available application installer or follow the manual WordPress installation process.
- Connect the domain. Check that the new installation uses the intended domain and HTTPS address.
- Restore or rebuild the site. Restore the database and files only after confirming that the new installation works on its own.
- Test before opening the site. Check login, pages, images, forms, menus, permalinks, and any payment or email functions.
For a site that needs to be moved rather than rebuilt, use a controlled site migration process instead of deleting the original installation first. Keep the old site available until the replacement has passed your checks.
Restore an existing site after the reinstall
Restoring a site requires matching the files and database to the same installation. A database without its media files will show broken images, while files without the database will not restore posts, pages, or settings.
Upload the saved files to the correct document root, then import the database through the database management tool provided by Hostinger. Update the database details in wp-config.php if the new database name, user, or password differs from the old installation.
Check the site URL after restoring. If the domain or protocol changed, old URLs may still point to the previous address. This can affect images, internal links, login redirects, and scripts.
Permalinks may need to be saved again from the WordPress settings area. That action rebuilds the rewrite rules used for post and page URLs. If the site returns a server error afterward, restore the previous .htaccess file or ask Hostinger support to review the server response.
If HTTPS is missing after the reinstall, review the instructions for checking the SSL setup. DNS changes and SSL issuance can take time to appear, so do not make repeated changes during the waiting period.
What to check after WordPress comes back
A successful login does not prove that the site is fully restored. Test the parts visitors and administrators use.
- Open the home page and several older posts.
- Load images from the media library and from public pages.
- Submit a contact form and confirm delivery.
- Check user login, password reset, and administrator access.
- Test menus, search, categories, tags, and pagination.
- Review the site address and HTTPS behavior.
- Confirm that the active theme displays correctly on mobile screens.
- Reactivate plugins one at a time if they were disabled.
- Check scheduled tasks, backups, analytics, and payment connections.
Clear old caching only after the site works. Caches can show an earlier version of a page and make a completed repair look unsuccessful. If a problem returns after one plugin or theme is enabled, leave that item inactive while you investigate compatibility.
For DNS problems, compare the domain’s records with the intended Hostinger destination. The DNS record instructions can help you identify records used for email, verification, or the website itself.
Common reinstall mistakes to avoid
The biggest risk is deleting the wrong data before confirming that a backup can be restored. Check the backup files, not only the backup date. A zero-byte export or incomplete archive is not a usable recovery copy.
Deleting the database for a core-file problem
A damaged WordPress installation often needs new core files, not a new database. Keeping the database preserves content and reduces the chance of losing settings.
Overwriting custom files
Custom code can live in a child theme, wp-config.php, .htaccess, or a plugin. Compare these files with the backup before replacing them.
Changing DNS too early
If the domain already points to Hostinger, changing nameservers during the reinstall adds another possible failure. Leave DNS alone unless the domain is pointing to the wrong service.
If nameservers do need to change, allow time for DNS propagation. Some networks update sooner than others, so test from more than one connection before deciding that the new site failed.
Restoring infected files without checking them
A backup made after a security problem may contain the same unwanted code. Scan old files, update WordPress and extensions, and change administrator and database passwords before putting the site back online.
When should you ask Hostinger for help?
Contact Hostinger support when the hosting account cannot access the site files or database, the server returns repeated errors after a clean reinstall, or the domain points correctly but the installation still cannot connect.
Give support useful facts: the domain, the time the problem began, the last change made, the exact error text, and whether the issue affects the whole site or one page. Avoid sending passwords in a support message.
Hostinger is a practical fit for owners who can follow backup and restore steps and want WordPress hosting in one account. Look elsewhere if you need a managed service that handles nearly every technical change for you, or if your site requires a specialized server setup.
Questions about reinstalling WordPress on Hostinger
Will reinstalling WordPress delete my posts and pages?
A core reinstall normally keeps your database and content. A full deletion or fresh database removes them unless you restore a backup.
How long does a WordPress reinstall take?
The file replacement itself can be quick, but a full restore takes longer if the site has many images or a large database. DNS and SSL changes can take additional time to appear across different networks.
Can I reinstall WordPress without losing my theme?
Yes, if you reinstall only the WordPress core and keep the wp-content folder. Save the theme first because a full rebuild can remove it.
Should I reinstall WordPress after a hack?
A clean reinstall can remove altered core files, but it is only part of the repair. Check themes, plugins, uploads, administrator accounts, and passwords before restoring the site.
Can I reinstall WordPress if the dashboard will not open?
Yes, but use a file and database backup before working outside the dashboard. Follow the matching Hostinger instructions or ask support rather than deleting folders based on guesswork.
Take the safer next step
Start by exporting the database and saving the site files. If the problem is limited to WordPress core, repair that layer first. Use a full rebuild only when you have confirmed the backup and the correct domain folder.
This page contains affiliate links. If you purchase through the links on this page, we may earn a commission, at no extra cost to you.


