Stuck on "Briefly unavailable for scheduled maintenance"? Here's How to Fix It

If your WordPress site is showing "Briefly unavailable for scheduled maintenance. Check back in a minute." and it won't go away, the fix is usually quick. WordPress got stuck part-way through an update and left behind a file that's still telling everyone the site is closed. Delete that one file and your site comes straight back. Below is exactly why it happens, how to fix it without breaking anything, and how to stop it recurring.

This is one of those errors that looks scary because your whole front end vanishes behind a plain text message, but it's nearly always harmless and easy to reverse. No data is lost. Your content is fine. WordPress just needs a nudge.

Key takeaways

• The message appears because WordPress is in maintenance mode, which it switches on automatically during updates to core, plugins or themes.
• It normally clears itself in seconds. If it sticks around, a temporary .maintenance file in your site's root folder failed to delete.
• The fix is to delete that .maintenance file using your host's File Manager or an FTP client. That's it.
• Common causes are low server storage, a slow server, an incompatible plugin or theme, or an update that got interrupted.
• You can avoid it by not closing the update tab early, not bulk-updating dozens of plugins at once, and giving your hosting enough headroom.

What this message actually means

WordPress is open-source software maintained by developers all over the world. They're constantly fixing bugs, adding features and patching security holes, which is why staying on the latest version matters for both performance and safety.

Every time you run an update, whether that's the WordPress core, a plugin or a theme, WordPress temporarily takes your site offline so visitors don't land on a half-updated, broken-looking page. That's maintenance mode. To do it, WordPress drops a small temporary file called .maintenance into your site's root folder. While that file exists, every visitor sees "Briefly unavailable for scheduled maintenance. Check back in a minute."

When the update finishes, WordPress deletes the file automatically and your site reappears. Most of the time you never even notice it happened. The problem starts when that file doesn't get deleted. WordPress thinks it's still mid-update, keeps the maintenance message up, and your site stays "closed" indefinitely.

Why WordPress gets stuck in maintenance mode

The .maintenance file getting stuck nearly always comes down to one of these:

• Low memory. Every process in WordPress, updates included, runs on PHP scripts. If your server is short on storage, the script handling the install can fail before it gets to the step that deletes the .maintenance file.
• Slow server response. WordPress caps how long a script is allowed to run. If your server is sluggish, the update script can time out before it disables maintenance mode, leaving the file in place.
• Compatibility issues. If a plugin or theme update doesn't play nicely with your version of WordPress, it can throw a bug that halts the update part-way through.
• The update was interrupted. Disabling maintenance mode is the very last step of the update process. If you close the tab, navigate away, or the connection drops before it finishes, that last step never runs.

None of these damage your site. They just leave the door locked with the key still in it. The good news is the fix is the same regardless of which cause triggered it.

How to fix the error: delete the .maintenance file

The entire fix is deleting the .maintenance file from your site's root directory. You've got two practical ways to reach it: your web host's File Manager, or an FTP client. Both do the same job.

A quick note before you start: .maintenance begins with a dot, which means it's a hidden file on most systems. If you go looking and can't see it, you'll usually need to turn on "show hidden files" in whatever tool you're using.

Option 1: using your host's File Manager

Most hosts give you a File Manager inside their control panel. The steps are broadly the same wherever you are:

1. Log in to your hosting control panel and open the File Manager (often under a "Files" section).
2. Open your site's root directory. On most setups this is the public_html folder.
3. Find the .maintenance file in that folder. If it isn't showing, enable hidden files in the File Manager's settings.
4. Right-click the file, choose Delete, and confirm.

That's it. Refresh your site and it should load normally again. On Hostinger, for example, you'd open hPanel, go to Files, click File Manager, open public_html, then right-click .maintenance and delete it. The exact wording differs from host to host, but the logic is identical everywhere.

Option 2: using an FTP client

If you already use FTP, this route works just as well. Using FileZilla as the example:

1. Connect to your site with your FTP details so you can see your web files.
2. In the Remote Site panel, open the public_html folder where your site lives.
3. Look for the .maintenance file.
4. If you can't see it, it's probably hidden. Click Server in the menu bar and choose Force showing hidden files.
5. Right-click .maintenance and delete it.

Once the file's gone, your WordPress site should work normally again. These same steps apply to any FTP client, not just FileZilla.

A word of caution

Deleting .maintenance is safe. It's a temporary file and WordPress recreates it the next time it needs to. But while you're poking around in public_html you're sitting next to files that genuinely matter, like wp-config.php and your .htaccess. Delete the .maintenance file and nothing else. If you're nervous about touching files over FTP at all, that's a reasonable signal to hand it to someone who does it daily. A managed website maintenance plan means errors like this get handled before you've even noticed your site is down.

How to stop it happening again

Fixing the error takes a minute, but you don't want to be doing it every time you run updates. Better to remove the causes. Here's how.

Keep the update tab open until it finishes

When you update WordPress core from the admin dashboard, watch the screen. WordPress tells you when it's working, and when it's done you'll see a message reading "Disabling Maintenance mode... All updates have been completed."

Don't close the tab or click away before that confirmation appears. Closing early can cause a server connection timeout and interrupt the process at exactly the point where it should be switching maintenance mode off. That's one of the most common ways sites get stuck.

Don't bulk-update dozens of plugins at once

You should absolutely apply plugin and theme updates promptly, ideally as soon as they're available, because that's how you stay patched against security issues. But updating a huge batch in one go is asking for trouble. It slows the whole process down and raises the chance of your site getting jammed in maintenance mode.

Bulk updates also make plugin and theme conflicts harder to untangle. If something breaks after updating twenty plugins together, working out which one caused it is slow and painful. The fastest recovery in that situation is restoring a backup, which means losing the updates you just installed and starting over. Update in smaller, sensible batches and you keep that risk down.

Check compatibility before you update

Before updating a plugin or theme, make sure it's compatible with the version of WordPress you're running. You can check this in the plugin or theme's details in the WordPress directory.

Better still, set up a staging environment, a private copy of your site, and test updates there first. If something breaks in staging, your live site never sees it. This is one of the biggest differences between running updates by crossing your fingers and running them properly. We go into the wider case for ongoing care in why website maintenance is necessary for your business, and staging is a core part of that.

Give your hosting enough room to breathe

Low server storage is a real cause of this error. When you're short on space, PHP scripts can stop before they finish updating, leaving the .maintenance file behind. If you're regularly bumping up against your limit, upgrading your hosting plan for more space can fix the underlying problem.

To give you a sense of how much a single WordPress install actually needs, here's a rough breakdown of typical disk usage:

Component	Approximate size
WordPress core software (4.9.5+)	30.8 MB
Themes	1-25 MB
Plugins	up to 100 MB
Media files	600-800 MB on average
MySQL database	65 MB

Add that up and you'll want at least 1 GB of disk space to run a functional WordPress site. That's a bare minimum, though. It's always worth leaving extra headroom so the site has room to grow and runs better day to day. Media files are usually the part that balloons over time, so if your storage is creeping up, that's the first place to look.

Make the maintenance page look less alarming

When your site is in maintenance mode, the default screen is a plain HTML page with the "Briefly unavailable for scheduled maintenance. Check back in a minute." message. It does the job, but it looks broken to anyone who lands on it, which isn't great if a customer or a lead happens to visit mid-update.

You can replace it with a proper branded page using a plugin. One well-regarded option is Coming Soon Page, Maintenance Mode & Landing Pages. It's rated 5/5, includes mobile-ready pages, WooCommerce integration and spam protection, and runs on a freemium model with premium plans starting from $79.5. A custom maintenance page reassures visitors that you're working on the site rather than that it's fallen over, and it keeps your brand looking professional even while you're updating.

This is a small touch, but it matters for businesses that get steady traffic. A clean "we'll be back shortly" page with your logo on it reads very differently from a stark line of system text.

Where IceBoxDesigns fits in

Most of the time this error is a five-minute fix, and now you know how to do it. But it's also a symptom. Sites that keep getting stuck in maintenance mode usually have something underneath driving it: tight hosting, no staging, plugins updated in huge unmanaged batches, or nobody actually watching the updates run.

That's the gap a proper maintenance routine closes. Updates get applied in controlled batches, tested on staging first, with backups taken before anything changes, so a stuck .maintenance file is caught and cleared in minutes rather than leaving your site offline while you work out what FTP is. If you'd rather not think about any of this, our WordPress development and maintenance team keeps sites updated, monitored and recoverable, so the front end stays up while the housekeeping happens quietly in the background.

If your site is down right now, delete that .maintenance file and you're sorted. If it keeps happening, that's the bit worth fixing properly. Talk to us about a website maintenance plan and let someone else carry the worry.