If WordPress is stuck in maintenance mode, visitors may see a message saying the site is briefly unavailable while scheduled maintenance is being carried out. Normally that screen disappears automatically. When it does not, the update process was usually interrupted before WordPress could clean up after itself.
Do not keep refreshing and retrying updates.
Confirm whether an update is still running, take a backup if possible, then remove the maintenance lock only when you are sure the process has stopped. After the site returns, check which update failed and test the front end, forms and admin area.
Why WordPress enters maintenance mode
WordPress uses a temporary maintenance state during software, plugin and theme updates. A hidden file named .maintenance in the WordPress installation folder tells it when the update began.
An interrupted update can leave the file behind. However, standard WordPress core normally ignores it once the stored update timestamp is ten minutes old. A message that persists can also involve caching, a maintenance plugin, a hosting setting or an update that keeps restarting. Removing the file does not repair an incomplete update.
The process did not reach its cleanup step.
The update may have been interrupted mid-process.
Memory, execution time or disk space can interrupt updates.
The update itself may have failed.
How long should maintenance mode last?
Normally it lasts for the update. WordPress core has a ten-minute check based on the time recorded in the maintenance file. This is a technical timeout, not a promise that the website or its failed update will be repaired in ten minutes.
If the message remains, check the update status and which system is displaying it. Do not assume the mere presence of an old file means core will keep the site offline indefinitely.
Step 1: confirm the update is not still running
Check WordPress Admin in another tab, your hosting activity, and any update notifications. If a managed host is still processing an update, deleting the maintenance file too early can expose the site while files are incomplete.
Step 2: check whether you have a current backup
Before making server-level changes, make sure you have a recoverable backup if the hosting platform allows it. If the site handles orders or bookings, note the time of the backup so you know what data could be lost if a restore becomes necessary.
Step 3: remove the maintenance lock only after the process has stopped
- Open the affected site in your hosting file manager or connect with SFTP. Confirm the site and installation folder, especially if the account holds several websites.
- Find the WordPress folder containing
wp-admin,wp-contentand usuallywp-config.php. It is not always the hosting account’s firstpublic_htmlfolder. - Enable “show hidden files” if needed. The filename starts with a full stop:
.maintenance. - After confirming that the update has stopped, remove only that stale file. Leave WordPress folders and configuration files intact.
- Open the clean public URL while logged out and check the admin area. If the old message remains, check the site, hosting and CDN cache after confirming the update is finished.
On a standard WordPress installation, a failed update can leave a hidden .maintenance file in the WordPress root directory. Once you have confirmed no update is still running, removing that stale file can allow WordPress to load normally again.
If you are not comfortable using a hosting file manager or SFTP, ask your host or developer to do this. Do not delete random files in the WordPress root folder.
Look for failed or incomplete updates.
Open key layouts on desktop and mobile.
Send a real test enquiry.
If relevant, run the customer journey.
What if there is no maintenance file, or it returns?
| What you see | What to check |
|---|---|
| The standard scheduled-maintenance message after an update | Update status and the correct installation folder. Check hidden files and the core timestamp behaviour. |
| A branded coming-soon or maintenance design | The maintenance plugin, page builder or host’s own maintenance setting. Removing a core update file may not change it. |
| The site works for an administrator but visitors see the old page | Plugin rules and cached responses. Compare the logged-out public page after clearing the relevant cache. |
| The file appears again after removal | A continuing or repeated update job. Check the host’s activity and errors rather than deleting the file repeatedly. |
| A critical error replaces the maintenance message | The failed update, error logs and affected component. Restoring access is different from repairing the cause. |
Routine removal of a stale update file does not require editing wp-activate.php or changing installation constants. If the basic checks do not explain the problem, ask the host or developer to diagnose the actual update or plugin failure.
What if the site is still broken after maintenance mode is removed?
That is a different problem. The stale maintenance file may only have hidden the fact that a plugin, theme or WordPress update failed. Look for missing plugin files, fatal errors, incompatible versions or database-update notices.
If the issue started after an update, our guide on how to update WordPress safely explains why backups and staging matter before higher-risk changes.
Can you prevent WordPress getting stuck in maintenance mode?
You cannot eliminate every failed update, but you can reduce the risk. Keep enough free disk space, avoid running many large updates simultaneously, use a stable PHP version, maintain recoverable backups and test important updates on staging.
For WooCommerce, booking systems and lead-generation sites, the real goal is not simply to avoid the maintenance screen. It is to make sure the update process does not interrupt the customer journey.
For a repair request, send the public URL, the exact message, when it began and the last update you ran. Say whether the admin area opens and whether the site takes orders or bookings. Do not send passwords in the first message. Confirm the diagnosis, scope and cost of repair before work begins.
A site that is already losing enquiries needs emergency website fixes. Routine updates, backups and monitoring fit the website maintenance and support plans.
FAQ
Does maintenance mode mean the site has been hacked?
No. It is normally part of WordPress’ update process. A site that remains stuck should still be checked, but the maintenance message itself is not evidence of a security breach.
Will deleting the .maintenance file damage WordPress?
If the update process has finished or failed and the file is simply stale, removing it is the normal way to release the maintenance state. Do not remove it while a legitimate update is still running.
Why does this happen repeatedly?
Repeated failures can point to server limits, slow hosting, compatibility problems, insufficient disk space or an update workflow that is too aggressive for the site.
How can you avoid getting stuck in maintenance mode again?
Maintenance mode often appears when an update is interrupted. Keep the browser open during important updates and avoid running many large updates at the same time on a busy site.
A recent backup gives you a safer way back if an update fails.
- Update in smaller groups.
- Check hosting resources before major updates.
- Use staging for higher-risk changes.
- Verify the site after updates finish.
Core maintenance-mode behaviour checked against the WordPress developer reference for wp_is_maintenance_mode() on 23 October 2026. Hosting tools and maintenance plugins can behave differently.
