Cron Job Tester
Instantly validate cron expressions, see human-readable descriptions, and generate the next 10 scheduled execution times.
Schedule Meaning
""
Common Schedules
About the Tool
Writing a cron schedule can feel like guessing a secret code. You type a few stars and numbers, but you are never totally sure if your job will run every minute or just once a year. Our cron tester solves this problem. It acts as an instant translator that turns confusing cron schedules into plain English.
I built this tool because I got tired of waiting for a scheduled task to fire just to see if I wrote the code correctly. Now, you can test cron job online without waiting. Just type your code, and the tool will show you exactly what it means and exactly when it will run next.
How to Use
Checking your schedule is fast and easy. Here is how you do it.
- Enter your code: Type your five-part cron code into the big text box at the top.
- Read the translation: The tool instantly reads your code and shows a plain English sentence right below it.
- Check the dates: Look at the list to see the next 10 exact dates and times your job will run.
- Verify on server (optional): Click the "Verify on Server" button to see the exact times your job will trigger in UTC time.
Privacy & Security
Testing your job schedules should be totally secure.
When you use our cron expression parser, almost everything happens directly in your browser. This means your schedules stay on your device. If you use the "Verify on Server" feature, we only send the short string of characters to our backend to check the UTC math. We never save your schedules, log your activity, or track your IP address. As soon as the test is done, the data is gone forever.
Features
This is more than just a basic checker. Here is what makes this cron validator online special.
- Instant Translation: See a simple, human-readable sentence as soon as you type.
- Next 10 Runs: Automatically lists the next ten dates and times your job will fire.
- Local Browser Time: Shows the schedule in your own computer's local time zone.
- UTC Server Math: Provides a strict server check to make sure your job runs correctly in UTC time, which most real servers use.
- Quick Buttons: Click common examples like "Every hour" to fill the box instantly.
Technical Specifications
For developers who want to know how the parsing engine works.
| System Part | Details |
|---|---|
| Local Parsing Engine | Browser-based JavaScript validation |
| Server Check Engine | Python croniter library |
| Time Formats | Local system time and UTC |
| Supported Parts | Minute, Hour, Day of Month, Month, Day of Week |
| Special Characters | Asterisk (*), Comma (,), Hyphen (-), Slash (/) |
Frequently Asked Questions
What does the asterisk (*) mean in a cron schedule?
An asterisk means "every". For example, an asterisk in the minute slot means the job runs every single minute. An asterisk in the hour slot means it runs every hour.
Why do I need to check my schedule on the server?
Your computer shows time differently than a cloud server. Your local computer uses your current timezone, but most cloud servers use UTC time. The server check shows you the exact UTC times to prevent nasty surprises.
What are the five parts of a basic cron code?
The standard format uses five spaces: Minute (0-59), Hour (0-23), Day of the Month (1-31), Month (1-12), and Day of the Week (0-6, where 0 is Sunday).
Can I use dashes and slashes?
Yes. A dash creates a range (like 1-5 for Monday through Friday). A slash skips numbers (like */15 to run something every 15 minutes). The tool handles both perfectly.