Home / Text & Scheduling

Cron Job Parser

Runs locally in your browser. Your input is not uploaded.

In plain English

Fields
FieldValueMatches

    A cron job parser separates a crontab line into its schedule and command, explains the five scheduling fields, and previews upcoming matches. Use it when reviewing an unfamiliar server entry or checking whether a range, list, step, or named weekday expresses the timing you intended.

    This parser follows a Vixie-style five-field model. It does not execute the command or install a cron job, and its preview uses your browser's local time zone rather than the time zone of a remote server.

    How to Use the Cron Job Parser

    Paste a line, inspect its schedule, and compare the preview with the target system.

    1. Enter a complete entry or a five-field expression in the Crontab line input.
    2. Read In plain English for a description generated by cronstrue.
    3. Review Fields to see each Field, its original Value, and the expanded Matches.
    4. Choose 5, 10, or 25 from Next runs (your local time zone).
    5. Check the ordered run times and the status note for a detected macro, /etc/crontab user, command, or day-field OR behavior.
    6. Correct any reported field, range, macro, or field-count error before using the line in a scheduler.

    How a Five-Field Crontab Line Is Parsed

    The parser reads the first five whitespace-separated fields as minute, hour, day of month, month, and day of week. The remaining text is treated as the command. For an /etc/crontab-style line, it can detect a simple username in the sixth position and treat the rest as the command, although this is a heuristic rather than a complete crontab-file parser.

    Field Accepted numeric range Named values
    Minute 0-59 None
    Hour 0-23 None
    Day of month 1-31 None
    Month 1-12 jan through dec
    Day of week 0-7 sun through sat

    Names are case-insensitive, and both 0 and 7 resolve to Sunday. Each field supports *, comma-separated lists, ascending ranges, and positive steps. A value with a step, such as 10/5 in the minute field, starts at 10 and continues through that field's maximum; reversed ranges and a step of zero are rejected.

    This is not a parser for Quartz or other six- or seven-field dialects. Seconds, years, ?, L, W, and # are not supported. If you need to construct a compatible expression rather than inspect a full line, use the cron expression builder.

    Macros, Commands, and Day-of-Week Semantics

    The page expands lowercase @yearly, @annually, @monthly, @weekly, @daily, @midnight, and @hourly macros into five fields before parsing. @reboot is recognized separately and reported as a one-time daemon-start event with no schedule to preview. Other macros, as well as differently cased versions, are reported as unknown.

    Commands are displayed as text in the status area and are not interpreted or run. Shell redirections, environment variables, quoting, and percent-sign behavior belong to the cron daemon and its shell, not to this schedule parser. A line beginning with # is treated as empty, but the page does not parse multi-line crontab files, environment assignments, or inline comments.

    Vixie cron has a subtle rule when both day of month and day of week are restricted: a date matches when either field matches. For example, 0 9 1 * mon can run on the first of the month and on Mondays. The page reports this OR behavior in its status note; do not read the two fields as an automatic AND condition.

    Next-Run Previews, Time Zones, and Calendar Edges

    Upcoming runs are calculated from the next whole minute in your browser's local time zone. The algorithm searches matching calendar days, then combines them with the selected hours and minutes. The displayed weekday, date, and time are local to the device running the page, not necessarily the machine where cron will execute.

    During a forward clock change, a local time that does not exist is skipped by the preview. Repeated times during a backward change, scheduler downtime, delayed starts, and vendor-specific catch-up policies can behave differently in a real cron implementation. Treat the list as a calendar preview, then verify critical schedules in the actual deployment environment.

    The parser validates allowed field ranges, but it does not validate whether a selected day exists in every selected month. A schedule for day 31 simply has no match in a 30-day month. It also cannot determine whether the command is executable, whether two runs overlap, or whether the cron daemon has the expected permissions and environment.

    Privacy and Safe Review of Crontab Entries

    Parsing, description, and next-run calculation happen locally in the browser. Nothing in the crontab line is uploaded for conversion, and the command is never executed. The third-party library used here is cronstrue, which supplies the plain-English description after the site's own parser accepts the expression.

    Even without execution, crontab commands can contain credentials, internal hostnames, file paths, email addresses, or tokens. Redact those values before sharing screenshots or copied lines. Review the actual crontab with appropriate system tools before changing it, because this page does not model file ownership, daemon configuration, shell escaping, or deployment-specific extensions.

    Frequently Asked Questions

    Does this parser support a seconds field?

    No. It expects exactly five schedule fields: minute, hour, day of month, month, and day of week. A Quartz-style expression with seconds or a year will be rejected or misread as part of a full line, so use documentation for the target scheduler's dialect.

    Can I paste a complete crontab entry with a command?

    Yes. The parser uses the first five fields as the expression and shows the remaining text as the command. It also recognizes a simple /etc/crontab-style user before the command, but that detection is heuristic and does not replace parsing an entire crontab file.

    Which cron macros are supported?

    The supported lowercase macros are @yearly, @annually, @monthly, @weekly, @daily, @midnight, and @hourly. @reboot produces an explanatory status but no future dates. Other macros are reported as unknown.

    Why do the next runs differ from my server?

    The preview uses the browser's local time zone, while the server may use UTC or another configured zone. Daylight-saving rules and scheduler-specific behavior can also differ. Compare the browser zone with the daemon's configuration before treating the preview as authoritative.

    Are day of month and day of week combined with AND?

    Not when both are restricted in this parser's Vixie-style model. In that case, either field can make the date match. When either day field starts with *, both resulting field matches are required, which preserves the usual meaning of a wildcard schedule.

    References: Linux crontab(5) manual · cronstrue documentation.