WordPress Stuck in Maintenance Mode? Fix It in 5 Steps

WordPress stuck in maintenance mode after an update? This usually happens when the temporary .maintenance file remains in the WordPress root directory after a core, plugin, or theme update is interrupted.

A WordPress stuck in maintenance mode problem is usually caused by an unfinished update. WordPress creates a temporary .maintenance file while it updates core files, plugins, or themes. When the process finishes normally, WordPress removes that file automatically.

The steps below show how to identify the error, locate the WordPress root folder, find the hidden file, remove it safely, and confirm that the website is working again. The local example uses XAMPP, but the same fix applies to a live site through cPanel File Manager.

Why Does WordPress Get Stuck in Maintenance Mode?

During an update, WordPress briefly puts the website into maintenance mode so files can be replaced safely. A temporary .maintenance file is created in the root directory.

The problem appears when the update is interrupted, times out, or fails before WordPress removes the file. That can leave WordPress stuck in maintenance mode even though the update itself is no longer running.

Step 1: Identify the Maintenance Mode Error

Open your website in a browser. If you see the following message, WordPress is displaying its built-in maintenance screen:

Briefly unavailable for scheduled maintenance. Check back in a minute.

Wait a few minutes before making any changes. Normal WordPress updates usually finish quickly and remove maintenance mode automatically.

If the message remains and you know the update is no longer running, continue to the next step.

Step 2: Open the WordPress Root Folder

Open the main directory where WordPress is installed. You are in the correct folder when you can see items such as:

• wp-admin
• wp-content
• wp-includes
• wp-config.php
• index.php

In the XAMPP example used in this tutorial, the path is:

C:\xampp\htdocs\wordpress-test\

On a live website using cPanel, the WordPress installation is often inside:

cPanel → File Manager → public_html

If WordPress is installed in a subfolder, open that folder instead.

This tutorial uses XAMPP as a safe local test environment. If you want to create the same setup, follow our step-by-step guide to installing WordPress on XAMPP .

Step 3: Find the .maintenance File

Inside the WordPress root directory, look for a file named exactly:

.maintenance

The dot at the beginning of the filename matters. WordPress creates this temporary file while an update is in progress.

Step 4: Delete the .maintenance File

Select the .maintenance file and delete it from the WordPress root directory.

Do not delete .htaccess, wp-config.php, or any other WordPress files. Only remove the .maintenance file.

For a WordPress stuck in maintenance mode issue caused by an interrupted update, deleting this temporary file is usually enough to restore access. You do not need to edit its contents.

Step 5: Refresh the Website

Return to the website and refresh the page. The normal WordPress site should load instead of the scheduled maintenance message.

If the site opens normally, the fix is complete. You can then return to the WordPress dashboard and check whether the interrupted core, plugin, or theme update needs to be run again.

Still Stuck in Maintenance Mode?

If deleting .maintenance does not solve the problem, check the following:

• Open the website in a private or incognito browser window.
• Clear your browser cache.
• Clear any WordPress caching plugin or hosting cache.
• Confirm that .maintenance is no longer present in the root directory.
• Check whether the interrupted update completed successfully.
• Check hosting error logs if the website now displays a different error.

If WordPress stuck in maintenance mode is no longer the issue but the website now shows a 500 error or another PHP error, troubleshoot that new error separately rather than deleting additional WordPress files.

Official WordPress Resources

WordPress documents the “Maintenance Mode Following Upgrade” problem in its Common WordPress Errors guide and recommends deleting the .maintenance file from the site root when it remains after an update.

The official Updating WordPress guide also explains how to recover from a failed update and remove the .maintenance file when necessary.

Frequently Asked Questions

Why is my WordPress site stuck in maintenance mode?

A WordPress core, plugin, or theme update may have been interrupted before WordPress could remove the temporary .maintenance file.

Where is the WordPress .maintenance file?

It is located in the WordPress root directory. On many cPanel hosting accounts this is public_html, although WordPress may also be installed inside a subdirectory.

Is it safe to delete the .maintenance file?

Yes, when an update is no longer running and the website remains stuck in the built-in WordPress maintenance screen. Delete only .maintenance and leave the other WordPress files unchanged.

Why can’t I see .maintenance in cPanel?

Because it is a dotfile, cPanel may hide it by default. Open File Manager settings and enable Show Hidden Files (dotfiles).

Will deleting .maintenance delete my content?

No. Removing the temporary .maintenance file does not delete posts, pages, themes, plugins, media, or the WordPress database.

Final Check

If WordPress stuck in maintenance mode after an interrupted update, check the root directory for .maintenance first. Removing that temporary file and refreshing the website usually restores access in seconds.