WordPress shows a page that says the site is "Briefly unavailable for scheduled maintenance" every time it runs an update, usually for a few seconds. If it has been longer than a few minutes and the message has not gone away, the update did not finish and the site is stuck showing that screen instead of returning to normal. This is not a sign the site is gone or that anything was deleted. It is a stalled cleanup step, and the fix is small.
Version and verification. Written against WordPress 7.0.2, released 2026-07-17, current stable. Last verified 2026-08-06 against wordpress.org's own update documentation.
What you are looking at, and why it is not a sign your site is gone
Every time WordPress runs an update (core, a plugin, or a theme), it briefly puts the site into maintenance mode so visitors do not see a half-updated site mid-write. Under normal conditions this lasts a few seconds and clears itself automatically the moment the update finishes. When it does not clear, the update process was interrupted somewhere in the middle: a slow server response, the connection dropping, or a bulk update of several plugins that took longer than expected, and the marker that puts the site into maintenance mode never got removed.
Your content, database, and files are not affected by this. The site is not down in the sense of anything being broken; it is showing a maintenance screen because a specific temporary file was never cleaned up.
How long is too long
Before treating this as stuck, rule out the simpler explanation: the update may genuinely still be running. A single plugin update finishes in seconds. A WordPress core update, a large batch of several plugins updating together, or an update on a slower shared-hosting plan can reasonably take a few minutes. As a working rule: if the maintenance screen has been showing for more than five to ten minutes with no other activity on the site (no visible progress, no additional loading), treat it as stuck and move to the fix below. If it has only been a minute or two, it is worth waiting before touching anything, since deleting the marker file mid-update is one of the few ways to actually make this situation worse rather than better.
Before anything else: the backup you have not tested is an assumption
Before you delete anything, even a small marker file, confirm you actually have a backup you could restore from if this turns out to be more than the simple case. Know where it is and whether it includes both the database and the files. This is a short, low-risk fix in the overwhelming majority of cases, but "low-risk" is not the same as "no risk," and the backup check costs a few minutes against a much larger cost if this situation turns out to be something else.
The fix: find and delete one file
WordPress's own documentation names this exact fix directly: delete the file .maintenance from your WordPress root directory. That is the same folder that holds wp-config.php and your wp-admin and wp-content directories: the top level of your WordPress installation, not inside any subfolder.
- Connect to your site with FTP or your host's file manager.
- Navigate to the WordPress root directory.
- Find
.maintenanceand delete it. - Reload your site. It should return to normal immediately, with no further steps needed.
Deleting this file is a documented, ordinary part of WordPress's own recovery instructions for a failed or interrupted update, not a workaround, and not something that risks your content, since the file contains no site data at all.
If you cannot see the file
Files that start with a dot are hidden by default in most FTP clients and file managers, which is a common reason people conclude the file "isn't there." Look for a setting to show hidden files (in FileZilla, for example, this is under the Server menu), and it will appear alongside your other WordPress root files.
Why this happened: the mechanism, in one paragraph
WordPress writes this file at the start of an update specifically so that a visitor loading the site mid-update sees a clean maintenance message instead of a half-updated page, and it removes the file itself once the update finishes successfully. A stuck maintenance screen means that removal step never ran, which happens when the update process itself was cut off before completion. A server timeout, a lost connection, or a very large batch of plugin updates running at once are the common triggers. The file being present with the update otherwise incomplete is exactly what "stuck" means here, and deleting it manually finishes the cleanup that the interrupted process did not get to do on its own.
If the maintenance screen comes right back
If you delete the file and the site returns to normal, but the maintenance screen reappears shortly afterward, that is a different and more specific situation. Something is actively re-triggering it, most often a plugin's own update routine retrying and failing again. Deleting the file a second time will not resolve that on its own.
In that case, deactivate every plugin at once by renaming your wp-content/plugins folder through FTP or your host's file manager (to something like plugins-off), which prevents any plugin code from running without needing admin access. If the maintenance screen stops reappearing, reactivate plugins one at a time, checking after each, to find the one whose update kept failing. Update or, if necessary, temporarily leave off the specific plugin you find, rather than the whole set.
After it clears: confirm the update actually finished
Deleting .maintenance removes the stuck screen, but it does not by itself confirm the update completed successfully. Check Dashboard > Updates or Tools > Site Health > Info for the current version, and if you saw a "could not copy file" or similar error before the site got stuck, that specific error has its own explanation and fix, since the maintenance-mode symptom and that error often show up together. If the update did not fully apply and you would rather undo it than push it through, rolling back without losing content covers that separately.
Related in this cluster
For what an update actually does, step by step, which makes this kind of stall easier to reason about the next time it happens, see what actually happens during a WordPress update. For the broader context of the current WordPress 7.x release, the site owner's guide to WordPress 7 covers what changed and why updates matter this cycle in particular.
Frequently asked questions
Is it safe to delete the .maintenance file?
Yes. It is a temporary marker with no site data in it. WordPress's own documentation names deleting it as the standard fix for a stuck or failed-update state.
How long should I wait before deleting the .maintenance file?
At least five to ten minutes of no visible activity. A core update or a large batch of plugin updates can reasonably take a few minutes on its own.
Why can't I find the .maintenance file in my FTP client?
Files starting with a dot are hidden by default in most FTP clients. Turn on the option to show hidden files, then look in your WordPress root directory.
Why does the maintenance screen keep coming back after I delete the file?
Something is re-triggering it, usually a specific plugin's update routine failing repeatedly. Deactivating all plugins at once by renaming the plugins folder, then reactivating one at a time, finds the specific one responsible.
Did I lose any content because of this?
No. The maintenance-mode file has nothing to do with your posts, pages, or database. It only controls whether visitors see the maintenance screen.
