Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsYou can reinstall WordPress without deleting posts, pages, media, plugins, themes, or settings when you replace only the core files and keep a verified copy of both parts of the site: the database and the files. The database holds your publishing data and configuration; the files hold WordPress code, wp-content, uploads, themes, plugins, wp-config.php, and other server files.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The safe sequence is simple: export the database, download the complete site directory, confirm that both backups can be opened, upload a fresh package that matches your intended WordPress version and language, leave the configuration and content directories in place, then test the site and complete any required database upgrade.
As an Amazon Associate I earn from qualifying purchases.
What a WordPress reinstall actually replaces
A reinstall is normally a repair of WordPress core files, not the creation of a new, empty site. WordPress keeps information in two separate places, so treating one as a substitute for the other is the most common cause of data loss.
| Site component | What it contains | What happens during a core-file replacement |
|---|---|---|
| Database | Posts, pages, comments, links, settings, and other structured site data | It remains untouched; export it before starting so it can be restored if a mistake occurs. |
| WordPress core files | The files supplied by the WordPress package | These are replaced with clean copies of the selected version. |
wp-content/ |
Plugins, themes, uploads, and related content files | It is preserved and must not be overwritten as part of a normal core refresh. |
wp-config.php |
Database connection details and site-specific configuration | It is preserved; replacing it can disconnect the site from its database. |
| Other custom files | Custom code or server rules outside the standard package | They stay in place unless you have identified a particular file as damaged and backed it up first. |
A copy of the files alone cannot restore posts or settings, and a database export alone cannot restore themes, plugins, or uploaded images. The backup set has to include both.
#1 Best Overall
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Prepare a recoverable backup before touching the server
Do not begin by deleting the existing installation. First create a rollback point that is stored away from the server you are about to change.
- Export the database. Use your hosting control panel or database administration tool to create a complete export in SQL, GZ, or BZ2 format. The export should include the tables used by the WordPress installation, not just a selection of posts.
- Download the entire WordPress directory. Include
wp-content/,wp-config.php, all themes and plugins, the uploads directory,.htaccesswhen present, and custom files. Downloading only the package files misses the material that makes your site yours. - Keep the two backups together. Store the database export and the file archive on a local computer or another separate location. Keeping more than one recent copy, ideally in different locations, protects you if an archive is damaged or the local machine fails.
- Check that the backups are usable. Confirm that the archive opens, the database file can be read, and the download contains the expected directories. A backup that was never checked is only an assumption.
- Record access and configuration details. Write down the database name, database username, database password, database host, table prefix, site URL, and administrator credentials. These details are needed if you must reconnect the files to the database or finish recovery manually.
- Choose a quiet maintenance window. Put the site in maintenance mode or work during a period of low traffic. Visitors could otherwise submit comments or orders while files are being replaced, leaving the backup and live database out of sync.
Why both backups are mandatory
The database contains every post, comment, and link, along with pages and settings. The files contain the executable code and the assets that the database references, including uploaded images, themes, and plugins. Restoring only one side can produce a site that loads but has no content, or content that cannot render correctly.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Choose the reinstall route that fits your access
There are two practical approaches. A dashboard reinstall is convenient when the administration area works. A manual replacement through SFTP, FTP, or a hosting file manager gives you control when the dashboard is unavailable or the existing core is suspected to be incomplete.
| Route | Access required | Control over protected files | Best use |
|---|---|---|---|
| Dashboard core reinstall | Working administrator access and a functioning update screen | The updater handles core files; you still need an independent backup before starting | A quick same-version refresh when the site can be managed normally |
| Manual SFTP, FTP, or file-manager replacement | Server file access and the fresh WordPress package | You explicitly leave the configuration and content directories in place | A broken dashboard, failed automatic update, suspected missing core files, or a controlled version change |
If the administration area is inaccessible, do not force a dashboard repair. Use the manual route after making the database and file backups.
Manual reinstall: replace core files without deleting content
1. Select the package
Download a fresh WordPress package from WordPress.org that matches the version you intend to run and the language used by the site. A same-version package is appropriate when you are repairing damaged or incomplete files. A newer package is an upgrade and may require database changes after the upload.
Rank #2
- Slim durable design to help take your important files with you
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
2. Connect to the correct directory
Connect with SFTP, FTP, or the file manager supplied by your host. Confirm that you are in the directory containing the live wp-admin, wp-includes, and WordPress root files. Uploading into a neighboring or temporary directory does not repair the public site.
3. Identify the items that must stay
Before copying anything, identify wp-config.php and the complete wp-content/ directory. Also note any custom files outside the standard package, including server rules or application-specific code. These are part of the site backup and are not disposable core files.
4. Replace the core directories and files
Upload the fresh package over the existing installation. Replace the standard core directories and root files supplied by that package, while leaving the protected configuration and content items untouched. Do not upload a blank configuration file over the live one.
5. Handle failed overwrites
Some uploaders report success while leaving old or partial files in place. If files cannot be overwritten reliably, remove the old core copies first and then upload the fresh copies. Do this only after confirming your backup and only while preserving wp-config.php, wp-content/, and identified custom files.
6. Finish the database step
Log in after the upload. WordPress may display a database-upgrade request, especially when you installed a newer release. Allow the upgrade to complete, and do not close the browser or interrupt the process while it is running.
Rank #3
- High-capacity external hard drive with up to 2TB of storage The ModusTech Facet portable external hard drive gives you dependable HDD storage in a slim 2.5-inch design. Multiple capacities available up to 2TB — back up photos, videos, music, documents, and game libraries with room to grow. A trusted external storage solution for everyday backup, media archives, and creative work.
- USB-C and USB 3.1 connectivity with included 2-in-1 cable The Facet ships with a USB-C to USB-C cable and tethered USB-A adapter, so this external hard drive connects to modern laptops, USB-C iPhones, tablets, and older USB-A computers without buying an extra cable. USB 3.1 Gen 1 (5Gbps) interface delivers real-world transfer speeds up to 100MB/s — fast enough to back up 50GB of files in about 8 minutes.
- Plug-and-play external hard drive for PC, Mac, and laptops Preformatted in exFAT and ready to use the moment you plug it in. The Facet works out of the box with Windows PCs, macOS Macs, MacBooks, Chromebooks, and laptops — no drivers, no software, no setup required. A true plug-and-play external hard drive built for everyday use across every major operating system.
- External hard drive for PS4, Xbox One, and Smart TV gaming The Facet is compatible with PlayStation 4, Xbox One, and Smart TVs with USB support. PS4 and Xbox One games run directly from the drive — plug it in, format through the console, and add to your storage. Also works with Smart TVs that support USB recording or external media playback.
- Slim, shock-resistant portable external hard drive — 160g At 2.5 inches and just 160g, this portable external hard drive is bus-powered through a single USB-C cable — no separate power adapter, no extra cables. Slim enough for a laptop bag, jacket pocket, or camera bag, with a shockresistant casing and faceted diamond-texture top panel that resists fingerprints and everyday wear. Backed by a 1-year limited warranty from ModusTech, a consumer electronics brand specializing in external storage.
7. Test before declaring success
Open the front end and several administration screens. Check a recent post, a page, the media library, navigation, forms, and any function that matters to your site. Test on both a logged-in and a logged-out browser session so cached administrator output does not hide a failure.
Dashboard reinstall when administration still works
A dashboard reinstall is useful when WordPress can authenticate you and the update screen loads. In current WordPress installations, the core refresh is available from the administration area under Dashboard → Updates, where a reinstall option appears when the installation supports it. Labels can vary by version or hosting environment.
- Complete and verify the database and file backups first.
- Open the update screen and choose the option to reinstall the current WordPress version, or select the intended version if an upgrade is planned.
- Keep the browser window open until the update reports completion.
- Visit the front end and administration area, then perform the same media, permalink, plugin, and theme checks used after a manual replacement.
This route does not remove the need for a backup. If the dashboard itself is failing because of a damaged plugin, theme, database, or permission problem, an automatic core download may not address the underlying cause; switch to the manual method or isolate the extension first.
Same-version refresh or version upgrade?
Decide the goal before uploading anything. A same-version refresh repairs file integrity while minimizing change. An upgrade moves the site to a newer release and can trigger database migrations or expose compatibility problems in extensions.
| Goal | Package to use | Database expectation | Main risk to check |
|---|---|---|---|
| Repair missing or corrupted core files | The same version and language already intended for the site | Usually no structural change; complete any prompt WordPress shows | The original problem may be a plugin, theme, permission, or database fault rather than core files |
| Move to a newer WordPress release | The target release and matching language package | WordPress may require a database upgrade after the files are replaced | Plugin and theme compatibility, custom code, and interrupted upgrade processing |
Do not use a reinstall as a substitute for a planned migration. If your objective is simply moving to another server, transfer the backed-up files and database, update configuration for the new environment, and test there.
Rank #4
- No wall warts: Work freely with its bus-powered USB-C. No wall outlet required.
- Big on space: High-capacity storage to store all your files in one place.
- Reliable backup: Safeguard assignments, projects, or sensitive files with trusted performance.
- Fuss-free, clutter-free: One port, one cord, quick connect.
- Peace-of-mind: Comes with two-year limited warranty and Rescue Data Recovery Services.
Post-reinstall verification checklist
Run these checks in order so you can identify which layer failed.
- Front page and representative URLs: Open the home page, a post, a page, an archive, and a media attachment. Look for server errors, blank output, or missing styling.
- Administration: Sign in, open the dashboard, edit a draft, and confirm that settings pages load without warnings.
- Media: Open the media library and several older images. A broken image can indicate a missing upload file or an incorrect path rather than a core problem.
- Permalinks: Test more than the home page. If post URLs return not-found errors, refresh the permalink settings and verify the server rewrite file was preserved.
- Plugins: Check the plugin screen and activate extensions in a controlled sequence if you had disabled them. Watch for a fatal error after each activation.
- Theme: Confirm that the active theme, menus, widgets, and custom templates are present. If the site fails only with that theme, switch temporarily to a default theme.
- Forms and integrations: Submit a test contact form, sign-up, or other critical workflow without using real customer data.
- Logs and scheduled work: Review the host’s PHP or web-server error log and confirm that scheduled tasks continue to run.
Troubleshooting when the reinstall does not fix the site
The white screen or fatal error remains
A clean core does not repair a faulty extension. Temporarily disable all plugins and switch to a default theme. If the site returns, re-enable components one at a time until the failing plugin or theme is identified. Keep the backup untouched while testing so you can restore the original state.
The dashboard is still unavailable
Use the manual file method if the automatic updater cannot run. Check file permissions, confirm that the upload reached the live document root, and inspect the server error log. A login failure caused by a database or configuration problem will persist until those layers are corrected.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Images or styles are missing
Compare the live wp-content/uploads/ directory with the downloaded backup. If the files exist, check the site URL and upload paths recorded in the database and verify that the web server can read the directories. Replacing core files again will not recreate a missing upload archive.
Post links return not-found errors
Confirm that the rewrite configuration file was preserved, then save the permalink settings once in the administration area to regenerate rewrite rules. If only certain URLs fail, inspect custom rewrite rules or a plugin that manages routing.
Best Value
- USB-C and USB 3.1 compatible.Specific uses: Business, personal
- Innovative style with refined metal cover
- Password protection with 256-bit AES hardware encryption
- Formatted for Mac
The database-upgrade screen loops or stops
Do not repeatedly refresh during an incomplete upgrade. Check the server log, confirm that the database user has the required permissions, and restore the pre-upgrade database and files if the site is worse. A same-version file refresh is safer than repeatedly applying an interrupted version upgrade.
Old or custom code disappeared
Compare the downloaded file backup with the live directory. Core replacement should not intentionally remove custom files, but an overbroad deletion can. Restore the specific file from the backup only after confirming that it belongs in the live document root.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not lose theme customizations on the next update
Direct edits to a bundled default theme can be overwritten by a core or theme update. Keep custom templates, styles, and functions in a child theme or another separately maintained location. Document where those changes live before reinstalling so you can verify them afterward.
Self-managed backups and managed hosting backups
A host may offer automatic snapshots, but provider backups should complement rather than replace an independent copy. The practical differences are effort, redundancy, restoration control, and dependence on the provider.
| Approach | Manual effort | Off-site redundancy | Restore tooling | Dependency |
|---|---|---|---|---|
| Self-managed backup set | You export the database, download files, verify archives, and choose storage locations | You decide how many copies exist and where they are stored | You restore files and the database using your own tools | Requires you to retain access details and maintain the archives |
| Managed hosting backups | The provider automates much of the capture process | Depends on the provider’s retention and storage design | The host may provide one-click or assisted restoration | Restoration depends on the provider’s availability, policy, and supported interface |
Before a risky change, keep a current local or off-site copy even when automated snapshots exist. Verify that the snapshot includes both the database and files and that you know how to request or perform a restore.
When a reinstall is the wrong solution
- Moving to a new server: This is a migration. Move the database and files, update the configuration for the new host, and test before changing DNS.
- A single plugin causes an error: Disable or replace the extension instead of replacing all core files.
- The database is damaged: Restore or repair the database; a fresh file package cannot recreate missing tables or content.
- Only uploads are missing: Restore the uploads directory from the file backup and investigate storage or permissions.
- Malware is suspected: Preserve evidence and follow a dedicated compromise-recovery process. A core refresh alone does not clean malicious code in plugins, themes, uploads, or the database.
A concise decision checklist
- Can you produce and read a database export?
- Have you downloaded the complete WordPress directory, including configuration and content?
- Are the backups stored away from the live server?
- Do you know the database connection details, table prefix, site URL, and administrator credentials?
- Are you using a package that matches the intended version and language?
- Will you leave the configuration and content directories untouched during replacement?
- Do you have time to test the front end, administration, media, permalinks, plugins, and theme afterward?
If any answer is no, stop and close that gap before replacing files. The few minutes spent verifying a backup are cheaper than reconstructing a site from incomplete copies.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchBottom line
Reinstall WordPress by refreshing its core files, not by creating a blank installation. Export the database, download and verify every important file, preserve wp-config.php and wp-content/, upload a clean package, complete any database upgrade, and test each layer of the site. When errors survive that process, investigate plugins, themes, permissions, configuration, or the database instead of repeating the core upload.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
