A webcron (sometimes written as web cron or online cron) is a service that triggers scheduled tasks over HTTP instead of relying on a local cron daemon.
You give it a URL and a schedule, and the service sends an HTTP request to that URL at the specified time. The target script runs and returns a response. No SSH, no crontab editing, no server-level permissions required.
The term came out of shared hosting, where providers locked users out of the system crontab. If you couldn't edit crontab, you couldn't schedule anything. Webcron services solved that by moving the trigger outside the server entirely. The script still runs on your host, but the clock that starts it lives elsewhere. Webcron is a subset of external cron job services, specifically the ones that trigger tasks via HTTP rather than SSH or API calls.
How webcron works#
The webcron service maintains a scheduler on its own infrastructure that fires HTTP requests on a cron-style schedule. When the timer hits, it sends a request to your endpoint. Your server receives it, executes the task, and returns an HTTP status code. The service logs the response code, response time, and sometimes the body.
This is different from a traditional cron job, where the daemon and the script live on the same machine. With webcron, the trigger and the execution are decoupled. That separation means you can schedule tasks on servers where you have no shell access, or trigger jobs across multiple servers from a single scheduler.
When webcron makes sense#
Shared hosting is the classic case. WordPress sites on budget hosting plans often can't set up real cron jobs (which is why wp-cron problems are so common). A webcron service pings wp-cron.php on a fixed schedule and the site processes its queued tasks reliably.
Serverless and PaaS environments (Vercel, Railway, Render) are the modern equivalent, since none expose a system crontab. If your app needs a scheduled task, you point a webcron at an HTTP endpoint in your app. We covered this pattern in our running cron jobs without a server guide, and there's a broader list of approaches in our scheduling HTTP requests online overview.
The limitation: webcron only works for tasks you can trigger via HTTP. Background processes, file system operations, or tasks that need to run as a specific system user still need a local cron daemon.
Webcron vs. Cloud Cron#
Traditional webcron services (EasyCron, cron-job.org) focus on triggering: they hit your URL on schedule. If the request fails, you might get a basic email notification.
WatchCron's Cloud Cron adds monitoring on top of the trigger. Every request is tracked with response codes, response times, and body content. If a task fails, starts running slow, or returns unexpected output, you get alerted through whatever channels you've set up. Our online cron services comparison covers how the major providers differ.