Skip to content

Category

Scheduling tools.

Understand, convert and verify cron and systemd timer schedules.

3toolsAll tools

Scheduling tools

  • SchedulingLive

    Cron Expression Tester

    Explain any cron expression in plain English — and see the next runs.

    Paste a cron expression and get a plain-English description plus the next run times. Supports ranges, steps, lists and @macros. Pure client-side.

    Open tool
  • SchedulingLive

    Cron to systemd Converter

    Turn a crontab line into a systemd timer + service unit.

    Convert a crontab entry into an equivalent systemd .timer and .service unit, with an OnCalendar expression and migration notes. Pure client-side.

    Open tool
  • SchedulingLive

    Systemd Unit Validator

    Lint .service, .timer and .socket files for typos and misconfigurations — in your browser, no root.

    Paste a unit file and get line-numbered findings: a directive in the wrong section, a typo systemd silently ignores, an OnCalendar= that never fires, Restart= that stops the unit loading at all. Every finding says what systemd itself does about it, and carries the fix. No systemd, no root, no upload.

    Open tool

When you reach for Scheduling tools.

Cron syntax is five fields that everyone half-remembers. The ambiguity is real: day-of-month and day-of-week are ORed, not ANDed, so 0 0 13 * 5 fires on the 13th and on every Friday, not on Friday the 13th. Step values, ranges and lists compose in ways that are easy to write and hard to read back.

systemd timers solve some of this and introduce their own vocabulary. OnCalendar is more expressive than cron and less familiar, and the mapping between them is not one-to-one — a cron line with a step value does not always have an obvious OnCalendar equivalent.

These explain an expression in plain English, show you the next actual run times so you can sanity-check the reading, and convert between crontab and systemd units when you are migrating.

Back to all tools