What WP Crontrol gets right
WP Crontrol is the tool most WordPress developers reach for when they need to see what the WP-Cron system is actually doing. It is maintained by John Blackbourn, a longtime WordPress core contributor who also makes Query Monitor and User Switching, and that pedigree shows. From the admin screens you can view every scheduled event with its arguments, schedule, callback, and next run time, then edit, delete, pause, resume, or run any of them on demand. It adds and removes custom cron schedules, exports the event list to CSV, and warns you about events that missed their schedule or have no action attached.
It is also genuinely trusted: a free plugin on WordPress.org with 300,000+ active installations and a high rating across well over a hundred reviews, actively maintained with a recent release, timezone-aware, and fully compatible with the Action Scheduler system that powers WooCommerce subscriptions and background orders. If your goal is to understand, debug, and control the cron events already running on your site, WP Crontrol is excellent at exactly that, and it is free.
The difference: managing cron versus running the work
WP-Cron is plumbing. It is the schedule that fires events; it does not, by itself, contain any tasks. WP Crontrol gives you a clear dashboard over that plumbing: it shows you the events plugins and WordPress core have scheduled and lets you control them. What it does not do is hand you a library of things to run.
To make a cron event in WP Crontrol actually do something, you have three routes, and its own documentation lays them out: register a hook and then write a PHP callback in your theme's functions.php, paste raw PHP into a "PHP cron event" (gated behind file-editing permissions, and disableable by a constant), or schedule a "URL cron event" that requests a URL. All three assume you are bringing the task yourself, as code, as a snippet, or as an endpoint.
TrueCommander comes at it from the other side. It ships the tasks. You pick a built-in command, back up the site, optimize images, trim revisions, scan for broken links, run a find-and-replace, send a templated email, and put it on a schedule from the Scheduled Commands module, with no hook to register and no callback to write. Where WP Crontrol manages the cron system, TrueCommander gives you the work to run on it.
The honest way to read this: they are not really rivals. Many developers will happily run both, WP Crontrol to inspect and debug the whole cron system, TrueCommander to schedule real maintenance without writing it from scratch.
Shown in advanced mode, where commands start with tp. In easy mode you type the same command without the tp prefix.
See Scheduled Commands in action
A short, unscripted demo of putting a command on a schedule and letting it run, no cron syntax, no callbacks.
WP Crontrol vs TrueCommander, feature by feature
An honest side by side. They overlap on the word "cron," but they are built for different jobs, and WP Crontrol wins outright on everything to do with inspecting and controlling the cron system itself.
| Feature | WP Crontrol | TrueCommander |
|---|---|---|
| View and debug all cron events (core + plugins) | Its core purpose | Not a cron debugger |
| Pause, resume, run, and delete cron events | Manages its own scheduled commands | |
| Fix missed events, system health warnings | ||
| Action Scheduler / WooCommerce cron support | Not its focus | |
| Export cron events to CSV | ||
| Ships a library of ready-to-run tasks | You supply the code, snippet, or URL | 91 commands |
| Schedule a real task with no code or callback | URL events yes; actions need code | |
| Chain multiple steps into one scheduled job | Macros | |
| Does more than cron (palette, security, email, AI) | Cron only, by design | 10 modules |
| Price | Free | $59/year, everything included |
| Maintenance | Actively maintained, recent release | Actively maintained |
WP Crontrol figures (installs, rating, reviews) are from its WordPress.org listing as of June 2026 and will change over time. Check the live listing for current numbers.
When WP Crontrol is the right pick
For a whole class of jobs, WP Crontrol is the better tool, and we would point you to it ourselves. Choose it when:
- You need to see and debug what is scheduled on your site, including events added by other plugins and WordPress core.
- A cron event is misbehaving, missing its schedule, firing twice, or showing "None" for its action, and you need to diagnose it.
- You work with Action Scheduler or WooCommerce background jobs and want visibility into them.
- You are a developer who is going to write the callback anyway and just want a clean interface to register and trigger the hook.
- You want a free, trusted, actively maintained tool focused on doing one thing well.
When to choose TrueCommander
TrueCommander is the better fit when the goal is the task, not the plumbing:
- You want to schedule real maintenance without writing code, backups, image optimization, revision cleanup, broken-link scans, find-and-replace, templated emails.
- You would rather pick from a library of built-in commands than register a hook and author a PHP callback for each task.
- You want to chain several steps into one scheduled macro, for example clean revisions, then optimize images, then email yourself the result.
- You would rather have one tool that also handles the rest of your admin work, search, security, WooCommerce, AI, than assemble a cron manager plus a backup plugin plus an email plugin plus a snippets plugin.
They work well together. Because TrueCommander schedules its commands through the normal WordPress cron system, WP Crontrol can see, inspect, and debug those events right alongside everything else. Running both is a perfectly reasonable setup.