How to Update WordPress Manually Without Breaking Your Site

The normal update button is fine until it fails halfway, asks for FTP details, or leaves you staring at a site that will not load. If you need to update wordpress manually, the goal is simple: replace WordPress core files without touching your content, then confirm the site still works.

TL;DR: Replace WordPress core files, keep your existing wp-content folder, complete any database update, clear caches, and test the site. Do not start without a restorable backup. Use a backup plugin first, and test the update on a staging site if the site earns money or handles logins, orders, leads, or client work.

Manual updates are useful when the dashboard update fails, wp-admin is unavailable, or you want full control over a risky update. They are also unforgiving. One wrong folder can overwrite uploads, themes, or plugins.

Before You Start

Manual control only helps if you can undo the change. Set up your recovery path before you open FTP, cPanel, or SSH.

🛟 Note: If WordPress asks for FTP details during an automatic update, the deeper issue may be server file ownership or permissions. A manual update can get you unstuck, but ask your host to fix the permission problem afterward.

Choose the Right Method

“Manual update” can mean four different things. Pick the method that matches your access, comfort level, and risk.

Method	Use it when	Access needed	Main risk
Dashboard	wp-admin works and you want to choose the timing	WordPress admin	A plugin or theme conflict after update
SFTP or FTP	Dashboard update failed or wp-admin cannot finish it	Hosting file access	Incomplete upload
cPanel or File Manager	You prefer host tools over an FTP app	Hosting control panel	Extracting files into the wrong folder
WP-CLI	You are comfortable with SSH commands	SSH and WP-CLI	Updating the wrong WordPress install

Use the dashboard if wp-admin works. Use SFTP, FTP, or File Manager when you need file-level control. Use WP-CLI if you know the exact WordPress folder and are comfortable with commands.

🔎 Note: WP-CLI is a command-line tool for WordPress. It is fast and clean, but it is not beginner-friendly if you are unsure where your site files live.

A) Update from the Dashboard

Use this when wp-admin still works. It is the safest manual-by-choice route because WordPress handles the file replacement for you.

From wp-admin

Skip this method if wp-admin will not load. Go straight to SFTP, FTP, File Manager, or WP-CLI.

B) Update with SFTP or FTP

This is the main file-level way to upgrade WordPress manually. Use SFTP if your host supports it because the connection is encrypted. FTP works, but it is less secure.

Download a clean WordPress package

Open the correct site folder

Replace only core files

Protect wp-content

⚠️ Note: Replacing wp-content is the mistake that turns a core update into lost uploads, missing themes, or broken plugins.

Finish the database update

Clear caches and test

For post-update speed checks, Airlift’s guide to speeding up WordPress is a useful next step after caches are clear and the site is stable.

C) Update with cPanel or File Manager

Use this if your host’s File Manager is easier than an FTP client. Host screens vary, so focus on the folder rules.

Move the WordPress files carefully

📁 Note: The common File Manager mistake is extracting into public_html/wordpress/ instead of updating public_html/. If the site still shows the old version, check the path before doing anything else.

D) Update with WP-CLI

WP-CLI is the cleanest route for technical users. It avoids browser timeouts and FTP transfer failures.

Run the core update from SSH

Use this method only if you have SSH access and understand where the WordPress install lives. SSH is a secure way to connect to your server and run commands.

Check the Site After Updating

The update is not done when the upload ends. It is done when the site still works for real users.

The homepage loading is a good sign. It is not proof that checkout, forms, or member pages work.

Fix Common Problems

Start with the least destructive fix. If the site earns money and the cause is unclear, restore first and troubleshoot on staging site.

Problem	First safe action
Site stuck in maintenance mode	Delete .maintenance from the WordPress root
Database update prompt appears	Follow the prompt or visit /wp-admin/upgrade.php
Critical error or white screen	Restore if the site is important, or disable plugins and check logs
wp-admin broken but frontend loads	Re-upload core files and check failed transfer logs
Site still shows the old version	Clear caches and confirm you updated the right folder

Recover without making things worse

🧯 Note: Do not troubleshoot a broken production site for hours while customers are affected. Restore the last clean backup, then find the cause on staging.

Core, Plugin, and Theme Updates Are Different

This guide is about WordPress core. Plugin and theme updates are different because they replace folders inside wp-content/plugins or wp-content/themes.

Mistakes to Avoid

Most manual update failures come from a small set of avoidable mistakes.

Slow down where the mistake is expensive.

FAQs

How do I update WordPress manually?

Back up the site, download a fresh WordPress package, replace wp-admin, wp-includes, and root core files, keep wp-content, complete any database update, clear caches, and test the site.

What files should I replace?

Replace WordPress core files only: wp-admin, wp-includes, and root WordPress files. Do not replace your existing wp-content folder.

Can I update WordPress manually without wp-admin?

Yes. Use SFTP, FTP, File Manager, or WP-CLI to replace core files. You may still need wp-admin or WP-CLI afterward to finish the database update.

Is WP-CLI safer than FTP?

WP-CLI avoids transfer failures and browser timeouts, so it is cleaner for technical users. It is not safer if you are unsure which WordPress install you are updating.

What should I do if the update breaks my site?

If the site is important and you have a clean backup, restore first. Then test the update on staging and fix the cause there.

Conclusion

Manual WordPress updates are worth knowing because they can save you when the dashboard update fails. The safe path is backup, staging when needed, core file replacement, database update, cache clearing, and real testing. Keep wp-content protected the whole time.

For a live business site, I would not treat manual updates as the default maintenance plan. For routine releases, automated WordPress updates are cleaner when backups and restore are ready. Use a backup plugin like BlogVault before you start, keep restore ready, and update WordPress safely away from production whenever possible.