Is Konnect2Tools free?

Yes. These in-browser tools are completely free to use with no account required for core functionality.

Do my files leave my device?

Browser document operations run locally, except where the operation uses an external service, such as AI summarisation. Read the processing note before using sensitive inputs.

Is the Cron Expression Parser tool safe to use?

Local operations process document content on your device. External-service operations may send inputs as described in the processing note. Keep originals and inspect the output.

Why does my cron job run at unexpected times?

Most common reasons: (1) Timezone — server runs in UTC, but you thought in IST (UTC+5:30). A job set for 9am may run at 3:30am or 2:30pm. (2) Day-of-week vs day-of-month conflict — many cron implementations OR these when both are non-asterisk. (3) DST changes shifting job times. (4) System time drift — use NTP. Always specify timezone explicitly when possible.

What is the difference between cron and crontab?

Cron is the daemon (background service) that runs scheduled jobs on Unix/Linux systems. Crontab is the file format/command used to define those jobs. 'Crontab -e' opens the crontab editor; 'crontab -l' lists current jobs. The 5-field expression syntax is what both share. Cloud services (AWS, GitHub Actions) use the same 5-field syntax for their scheduling.

How do I run a job every 5 minutes?

Use */5 * * * * — the */5 means 'every 5 minutes starting from 0' (0, 5, 10, 15... 55). To run every 5 minutes but only during business hours (9am-5pm IST, converting to UTC 3:30am-11:30am): */5 3-11 * * 1-5. Adjust hour range based on your server's timezone.

Does this cron parser work for AWS EventBridge/CloudWatch?

AWS EventBridge uses a 6-field cron syntax: minute, hour, day-of-month, month, day-of-week, year. This tool parses the standard 5-field cron (without year). For AWS, add the year field separately. AWS also uses ? instead of * for the field you don't specify when specifying either day-of-month or day-of-week.

Developer & data utilities

Cron Expression Parser

Parse and describe cron expressions in plain English with next run times.

Run Cron Expression Parser online

In-browserDocument processing runs on your device. External resources may still load.

Enable JavaScript to use the interactive tool. Read the instructions, limitations and FAQs below before starting.

The Cron Expression Parser is a developer tool that translates cryptic cron syntax into plain English descriptions and shows the next scheduled run times. Cron is the standard Unix job scheduler syntax used by Linux cron jobs, GitHub Actions, AWS EventBridge, Kubernetes CronJobs, and virtually every cloud and DevOps scheduling system.

Cron expressions use 5 fields: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-7, where both 0 and 7 mean Sunday). Special characters include: * (every), */n (every n units), ranges (1-5), and comma lists (1,15). The combination creates expressions like '0 9 * * 1-5' meaning 'at 9:00 AM every Monday to Friday'.

Getting cron expressions right is notoriously error-prone — a typo in a production cron job can mean scheduled reports never run, daily database backups don't happen, or billing emails go unsent. This parser lets you verify your cron expression by seeing exactly when it will trigger next, preventing silent failures in your scheduled jobs.

How to use this utility

Use the controls below—paste text, pick files, or adjust options as described on the tool.
Click the main action button. Processing runs in your browser on this device.
Download or copy the output. Check the processing note for any external services used by this operation.

Common use cases

Verifying a GitHub Actions schedule cron expression before committing
Debugging why a cron job didn't run — checking if the expression fires as expected
Building cron expressions for AWS EventBridge or CloudWatch Events rules
Understanding what a cron expression in legacy code actually schedules
Generating standard cron expressions from common human-readable schedules

Tips for best results

1Always test a new cron expression with this tool before deploying — prevents silent failures
2Use */15 for 'every 15 minutes' rather than 0,15,30,45 — it's more readable and equivalent
30 0 * * * runs at midnight every day; 0 0 * * 1 runs every Monday at midnight
4Month and weekday fields can use names (JAN, MON) in some implementations — check your platform
5For cloud schedulers (AWS, GCP), check if they use 5-field or 6-field cron (with seconds or year)

Frequently asked questions

Is Konnect2Tools free?: Yes. These in-browser tools are completely free to use with no account required for core functionality.
Do my files leave my device?: Browser document operations run locally, except where the operation uses an external service, such as AI summarisation. Read the processing note before using sensitive inputs.
Is the Cron Expression Parser tool safe to use?: Local operations process document content on your device. External-service operations may send inputs as described in the processing note. Keep originals and inspect the output.
Why does my cron job run at unexpected times?: Most common reasons: (1) Timezone — server runs in UTC, but you thought in IST (UTC+5:30). A job set for 9am may run at 3:30am or 2:30pm. (2) Day-of-week vs day-of-month conflict — many cron implementations OR these when both are non-asterisk. (3) DST changes shifting job times. (4) System time drift — use NTP. Always specify timezone explicitly when possible.
What is the difference between cron and crontab?: Cron is the daemon (background service) that runs scheduled jobs on Unix/Linux systems. Crontab is the file format/command used to define those jobs. 'Crontab -e' opens the crontab editor; 'crontab -l' lists current jobs. The 5-field expression syntax is what both share. Cloud services (AWS, GitHub Actions) use the same 5-field syntax for their scheduling.
How do I run a job every 5 minutes?: Use */5 * * * * — the */5 means 'every 5 minutes starting from 0' (0, 5, 10, 15... 55). To run every 5 minutes but only during business hours (9am-5pm IST, converting to UTC 3:30am-11:30am): */5 3-11 * * 1-5. Adjust hour range based on your server's timezone.
Does this cron parser work for AWS EventBridge/CloudWatch?: AWS EventBridge uses a 6-field cron syntax: minute, hour, day-of-month, month, day-of-week, year. This tool parses the standard 5-field cron (without year). For AWS, add the year field separately. AWS also uses ? instead of * for the field you don't specify when specifying either day-of-month or day-of-week.

Continue with another utility in developer & data utilities.

Explore all categories

PDF hub Jobs & admissions Image hub Developer hub Finance hub Converters Business Health Real estate GST & tax HR & payroll Legal Design & marketing Education