Cron expression tester
Paste a cron schedule and get it in plain English, plus the next times it fires. Then, if you want, arm a free dead-man’s-switch so you’re told the moment it stops. No signup.
At 04:30, every day.
Times below are shown in UTC. Pick your box’s zone above — cron reads the fields in the server’s local time. (Fixed offset; DST shifts aren’t modeled.) The dead-man’s-switch itself is timezone-free: it watches the gap between pings, so a late run is late in any zone.
Next 5 runs
| #1 | Tue 2026-08-25 04:30 UTC | in 8325 sec |
| #2 | Wed 2026-08-26 04:30 UTC | in 94725 sec |
| #3 | Thu 2026-08-27 04:30 UTC | in 181125 sec |
| #4 | Fri 2026-08-28 04:30 UTC | in 267525 sec |
| #5 | Sat 2026-08-29 04:30 UTC | in 353925 sec |
Will you know if it silently stops?
A cron line that stops firing — a broken crontab, a dead box, a paused container, a schedule someone commented out — throws no error. Nothing pages you. You find out when the thing it was supposed to do didn’t happen.
Cronping arms a dead-man’s-switch from this exact schedule: your job pings a URL each run; if a ping is late, we email (or Slack/Discord) you. Free, no account.
Arm a free monitor for this schedule →Monitor a whole crontab at once → · how Cronping works · cron troubleshooting guides