Crontab Syntax · Natural Language · Next 5 Executions · SysAdmin Cheat Sheet

Cron Expression Descriptor & Translator

Convert cryptic Unix crontab strings into friendly, human-readable English schedules. Verify execution timing, inspect individual fields, and prevent scheduling mistakes.

Enter 5-Field Standard Cron Expression:

Popular Cron Presets:

English Schedule Translation:

Every 15 minutes

Minute*/15(0 - 59)

Hour*(0 - 23)

Day of Month*(1 - 31)

Month*(1 - 12 / JAN-DEC)

Day of Week*(0 - 6 / SUN-SAT)

Next 5 Projected Execution Timestamps (Local Timezone):

UTC

#1Mon, Nov 2, 2026, 10:15 AM

#2Mon, Nov 2, 2026, 10:30 AM

#3Mon, Nov 2, 2026, 10:45 AM

#4Mon, Nov 2, 2026, 11:00 AM

#5Mon, Nov 2, 2026, 11:15 AM

Complete Crontab Entry Generator:

Command or Script to Run:

Add this line to your crontab (crontab -e):

*/15 * * * * /usr/bin/python3 /var/www/script.py >> /var/log/cron.log 2>&1

The Complete Guide to Cron Expressions & Crontab Management

01.The 5 Standard Unix Cron Fields

Traditional POSIX crontab files consist of 5 time and date fields followed by the command string to execute:

┌───────────── minute (0 - 59)

│ ┌───────────── hour (0 - 23)

│ │ ┌───────────── day of month (1 - 31)

│ │ │ ┌───────────── month (1 - 12 or JAN-DEC)

│ │ │ │ ┌───────────── day of week (0 - 6 or SUN-SAT)

│ │ │ │ │

* * * * * <command-to-execute>

Note on Sunday: In standard Linux cron (vixie-cron / cronie), both 0 and 7 represent Sunday.

02.Special Cron Operators: * / , -

Four primary operators allow expressive schedule configuration:

Asterisk (*): Wildcard matching every possible value in that field.
Slash Step (*/N): Step intervals. For instance, */10 in the minute field triggers at :00, :10, :20, :30, :40, :50.
Comma (,): Discrete list of values. For example, 1,15,30 matches day 1, 15, and 30 of the month.
Hyphen (-): Contiguous range. For instance, 1-5 in the weekday field matches Monday through Friday.

03.Essential Crontab CLI Commands

Manage user cron tables via the terminal without manually editing system spool directories:

crontab -e – Open the active user crontab in your default editor ($EDITOR).
crontab -l – Display currently scheduled cron entries to terminal stdout.
crontab -r – Caution! Deletes the user crontab without confirmation.
sudo crontab -u www-data -e – Edit jobs for a specific system user account.

04.The #1 Cron Pitfall: Minimal Environment & PATH

The single most frequent reason cron jobs fail silently in production is environment differences.

When running a command interactively in your shell, .bashrc or .zshrc populates your rich $PATH and variables like NODE_ENV.

Cron, however, launches subshells with a bare-bones PATH=/usr/bin:/bin. Always specify absolute binary paths (e.g. /usr/bin/python3 instead of python3) and redirect stderr to a log file: >> /var/log/app.log 2>&1.