How to Disable WP-Cron in WordPress (2026 Guide)

Disable WP-Cron in WordPress — laptop with server terminal schedule on desk

When you schedule a post for 9:00 AM, you expect it live at 9:00 AM — not at 11:30, when the first visitor of the day finally loads a page. That gap is the most common symptom of WP-Cron, and it is why many site owners choose to disable WP-Cron in WordPress and hand the job to a real server cron instead.

WP-Cron is not a real cron job. It has no clock of its own: it only checks for due tasks when somebody loads a page. On a quiet site, or one behind a full-page cache, that check may not happen for hours. This guide explains how it works, when it hurts you, and how to replace it with a reliable server cron job in about fifteen minutes.

What Is WP-Cron — and Why It Isn’t a Real Cron

WP-Cron is WordPress’s built-in task scheduler. It handles publishing scheduled posts, update checks, emptying the trash, deleting expired transients, plugin backups, and WooCommerce order emails and subscription renewals.

A real cron job is run by your server’s operating system on a fixed timetable, whether anyone visits or not. WP-Cron works the other way round: every time somebody loads a page, WordPress checks whether any tasks are due. If one is due, it fires off a quick, non-blocking request to its own wp-cron.php file (timeout: 0.01 seconds) and carries on rendering the page.

On a busy site that works well enough. On a quiet one, a post scheduled for 2:00 PM will not publish until somebody loads a page — 5:00 PM, in WordPress’s own documentation. The task is not skipped; it simply waits for the next visit.

WordPress 6.9 (December 2, 2025) improved things: the spawn moved from the init hook to the shutdown hook, so the background request now fires after the page has been sent. The performance team reported up to a second off time to first byte on affected requests. A genuine improvement — but WP-Cron still depends on visitors to run at all.

5 Signs WP-Cron Is Causing Problems

If scheduled posts always go out on time, the default setup is fine. Consider switching when you recognise any of these symptoms:

  1. Scheduled posts show “Missed schedule.” The classic symptom: your tasks are waiting on visitors who never arrive. See my guide on how to fix the WordPress missed schedule error.
  2. Backups and emails run late — or never. Backup, newsletter and WooCommerce emails all queue through WP-Cron — late tasks mean lost data and unhappy customers.
  3. Your first byte is slow. The loopback request can add noticeable delay on requests that spawn cron work. If you are already reducing server response time in WordPress, WP-Cron is one more source of overhead worth removing.
  4. Your site is behind a full-page cache. A cached page served by a plugin, host or CDN never reaches PHP, so it never triggers WP-Cron. A heavily cached site can go hours without a single cron check.
  5. Your site is quiet at night. Membership renewals and nightly backups do not care that nobody visited at 3:00 AM. A server cron job runs on a timetable, not on traffic.

Before You Start: What You’ll Need

This is a fifteen-minute job, but it touches wp-config.php, one of the most important files on your site — so take a backup first (see my complete WordPress backup guide if you don’t have a recent one). A single typo there can take your whole site down. You will also need file access (FTP, SFTP or your host’s file manager) and a scheduler: cPanel Cron Jobs, Plesk Scheduled Tasks, or SSH access to crontab on a VPS.

The order matters: set up the server cron job first, and only then disable WP-Cron — disabling it with nothing to replace it stops every scheduled task on your site.

Step 1: See What’s Actually Scheduled

Install the free WP Crontrol plugin and open Tools > Cron Events: every scheduled event, its interval and next run time, with overdue events flagged. Note which events matter most; you will return here at the end to confirm the new setup works.

Step 2: Set Up the Real Cron Job First

A real cron job is a command your server runs on a fixed schedule. Use WP-CLI when your host provides it; a plain HTTP request works everywhere else.

Option A: WP-CLI (recommended)

If your host gives you SSH and WP-CLI, add this line to the crontab of the user that owns your site files (run crontab -e; never root — files created by cron tasks would end up with the wrong owner):

*/5 * * * * wp cron event run --due-now --path=/home/username/public_html --quiet

Replace the path with your real installation path. --due-now runs only due events, and --quiet keeps the output clean. Because this runs PHP directly, it bypasses HTTP entirely — firewall rules, Cloudflare settings and broken loopback requests cannot interfere.

Option B: A web request via cPanel

If WP-CLI is not available, use cPanel’s Cron Jobs screen (under Advanced). Set the interval to once every five minutes and enter this command, replacing yoursite.com with your domain:

wget -q -O - https://yoursite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

If your host has curl but not wget, this equivalent works just as well:

curl -s https://yoursite.com/wp-cron.php?doing_wp_cron > /dev/null

How often should the job run?

Every five minutes suits most sites; a quiet blog can use fifteen, a busy WooCommerce store or membership site every minute. A run with nothing due finishes in milliseconds, so when in doubt, pick five minutes. One more check: some managed hosts already run WP-Cron from their own servers — ask support before adding your own job.

Step 3: Disable WP-Cron in WordPress (wp-config.php)

With the server job in place, open wp-config.php in your site’s root folder and add this line above the comment that says /* That's all, stop editing! */:

define( 'DISABLE_WP_CRON', true );

Save the file. That is the whole change.

The name is misleading: this does not switch scheduling off. Every event stays scheduled, and wp-cron.php still runs them whenever it is called — the constant only stops page loads from triggering the check. Your server cron job is now the only thing starting those tasks. To undo it, remove the line and delete the server cron job.

Step 4: Verify Everything Still Runs

Wait ten to fifteen minutes, then check:

  1. WP Crontrol shows nothing overdue. Go back to Tools > Cron Events: every event should have a next-run time in the future. If events pile up as overdue, your server job is not reaching WordPress — double-check the path in the WP-CLI command or the domain in the wget command.
  2. A test post publishes on time. Schedule a draft post five minutes out and confirm it goes live on time.
  3. Site Health is happy. Check Tools > Site Health > Status for warnings about scheduled events.

You can also check wp-cron.php is reachable by visiting https://yoursite.com/wp-cron.php: a blank page means it answers requests. A 404 means the file is missing (reinstall from Dashboard > Updates); a 403 usually means a security plugin, an .htaccess rule or a Cloudflare rule is blocking it.

WooCommerce Sites: Don’t Forget Action Scheduler

WooCommerce uses Action Scheduler, a job queue that also powers subscription renewals, webhooks and store emails. It runs on top of WP-Cron, so this guide’s setup covers it. Check the queue under WooCommerce > Status > Scheduled Actions; failed actions there point at the server cron job.

Common Mistakes to Avoid

  • Disabling WP-Cron with no replacement. With DISABLE_WP_CRON set and no server job, nothing scheduled runs at all. Always complete Step 2 first.
  • Adding the constant below the stop-editing line. Custom constants belong above /* That's all, stop editing! */ — lines added below it can be lost or ignored by some hosts.
  • Using the wrong path in the WP-CLI command. --path must point at the folder containing wp-config.php. A wrong path fails silently, and your events quietly stop running.
  • Blocking wp-cron.php with a security rule. Some security plugins and firewall rules block wp-cron.php. If the server job runs but nothing executes, check your security plugin and Cloudflare WAF rules first.

Frequently Asked Questions

Is it safe to disable WP-Cron in WordPress?

Yes — as long as a server cron job replaces it. The constant only removes the page-load trigger; events are untouched and run the next time wp-cron.php is called. The unsafe setup is disabling WP-Cron and adding nothing.

Final Thoughts

WP-Cron was a clever solution for its time: a scheduler that works on any hosting, with no server access required. But it was never a real cron job, and “whenever the next visitor arrives” is not a schedule to rely on.

The fix is small and reversible: one server cron job every five minutes, one line in wp-config.php, one check in WP Crontrol.

If you’d rather have a developer handle the server side — or your scheduled tasks are already misbehaving and you want the cause found properly — get in touch through my contact page and I’ll take a look.