Build and understand cron expressions visually. Schedule tasks for Linux, macOS, or any cron-compatible system.
| Field | Allowed Values | Special Characters |
|---|---|---|
| Minute | 0-59 | * , - / |
| Hour | 0-23 | * , - / |
| Day (M) | 1-31 | * , - / ? L W |
| Month | 1-12 or JAN-DEC | * , - / |
| Day (W) | 0-6 or SUN-SAT | * , - / ? L # |
* — Any value, — Value list (e.g., 1,3,5)- — Range (e.g., 1-5)/ — Step (e.g., */15)? — No specific valueL — Last (day of month/week)0 0 * * * — Daily at midnight*/15 * * * * — Every 15 minutes0 9 * * 1-5 — Weekdays at 9am0 0 1 * * — First of month30 4 * * 0 — Sundays at 4:30am0 0 * * * — Runs every day at 00:00. Perfect for daily backups or cleanup tasks.
*/15 * * * * — Runs every 15 minutes. Ideal for monitoring or polling tasks.
0 9 * * 1-5 — Runs Monday through Friday at 9:00 AM. Great for business hours tasks.
0 0 1 * * — Runs at midnight on the 1st of every month. Perfect for monthly reports.
5-field cron (standard): minute hour day month weekday. 6-field cron (Quartz/extended): adds seconds as the first field. Most systems use 5-field format.
Use day of week field: 1-5 (Monday-Friday) or MON-FRI. Example: 0 9 * * 1-5 runs at 9am on weekdays.
*/15 means 'every 15 units'. In the minute field, */15 means every 15 minutes. In hours, */2 means every 2 hours.
Cron runs in the server's local timezone. For UTC, set your server timezone to UTC or use tools that support timezone specification.
Cron schedules are based on system time. During DST transitions, tasks may run twice or be skipped depending on your system's timezone handling.
Category:
Developer Tools →Encode text or files to Base64, or decode Base64 back to its original form. Supports URL-safe Base64...
Format, validate, minify, and explore JSON data. Interactive tree view with syntax highlighting and ...
Generate MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes for text or files. Verify hash integrity a...