SoftwareTestPilot
Free tool · 100% in-browser · no signup

Cron Expression Builder & Tester

Build, translate, and test any cron expression. Get the next 10 run times in any timezone, and export ready-to-paste schedules for Jenkins, GitHub Actions, Kubernetes CronJob, Quartz, Node-cron, Vercel Cron, systemd, AWS EventBridge, and Postgres pg_cron.

Visual builderNext 10 run timesTimezone-awareQuartz 6/7-fieldPlatform warnings100% local
Plain English: Runs at minute 0, at hour 2, every month, every day.

Common presets

Next 10 run times

  1. 1.Sat, Jul 18, 2026, 02:00:00
  2. 2.Sun, Jul 19, 2026, 02:00:00
  3. 3.Mon, Jul 20, 2026, 02:00:00
  4. 4.Tue, Jul 21, 2026, 02:00:00
  5. 5.Wed, Jul 22, 2026, 02:00:00
  6. 6.Thu, Jul 23, 2026, 02:00:00
  7. 7.Fri, Jul 24, 2026, 02:00:00
  8. 8.Sat, Jul 25, 2026, 02:00:00
  9. 9.Sun, Jul 26, 2026, 02:00:00
  10. 10.Mon, Jul 27, 2026, 02:00:00

Export to your platform

GitHub Actions cron runs at MOST every 5 minutes and always in UTC.
GitHub Actions · yaml
# .github/workflows/scheduled.yml
name: Scheduled QA Run

on:
  schedule:
    # Runs at minute 0, at hour 2, every month, every day.
    - cron: "0 0 2 * * *"
  workflow_dispatch:

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 20 }
      - run: npm ci
      - run: npx playwright install --with-deps
      - run: npx playwright test

Cron field reference

FieldRangeSpecialExample
Second (Quartz only)0-59, - * /*/30 → every 30 s
Minute0-59, - * /*/15 → every 15 min
Hour0-23, - * /9-17 → 9 am to 5 pm
Day of month1-31, - * / ? L W1,15 → 1st & 15th
Month1-12 or JAN-DEC, - * /JAN,JUL → Jan & Jul
Day of week0-6 or SUN-SAT, - * / ? L #MON-FRI → weekdays

Why SDETs and DevOps engineers need a cron builder in 2026

Every CI/CD platform reinvented cron slightly differently — and every subtle difference is a production outage waiting to happen. GitHub Actions ignores seconds; Kubernetes rejects Quartz's ?; Jenkins adds the H hash operator; AWS EventBridge requires a year field; Quartz forbids * in both day-of-month and day-of-week at once; Vercel Cron always runs in UTC no matter what your team's timezone is. This tool encodes every one of those quirks so you can build the expression once, verify it against the next 10 actual run times in your target timezone, and export the exact syntax your platform expects.

How this tool beats crontab.guru for QA and automation teams

  • Framework export — one click emits Jenkins pipeline syntax, GitHub Actions workflow YAML, Kubernetes CronJob manifests, Quartz cron for Spring's @Scheduled, Node-cron, Vercel Cron, systemd timers, AWS EventBridge (CDK + console), and Postgres pg_cron for Supabase scheduled jobs.
  • Timezone-aware next runs — pick UTC, America/New_York, Europe/London, Asia/Kolkata, or any IANA zone and the run schedule recomputes instantly, catching DST bugs before they land.
  • Quartz 6/7-field mode — supports seconds and year fields, plus ?, L, W, and # tokens with plain-English explanations.
  • Platform validation warnings — flags "GitHub Actions doesn't support seconds" before you commit a broken workflow.
  • 100% in-browser — safe to paste internal job schedules; no server, no telemetry.

Common CI/CD cron recipes

  • Nightly full regression — 0 2 * * * (2 AM daily). Pair with a timezone header so the run happens at 2 AM local to your dev team, not UTC.
  • Hourly smoke tests — 0 * * * *. On Jenkins use H * * * * so 100 pipelines don't stampede at the top of every hour.
  • Business-hours API monitor — */15 9-17 * * 1-5. Every 15 minutes, 9-to-5, Monday to Friday.
  • Weekly executive report — 0 6 * * 1. Monday 06:00 — email lands in inboxes before standup.
  • Monthly billing / cleanup — 0 0 1 * *. Midnight on the 1st.
  • Off-hours load test — 0 3 * * 0,6. 3 AM on weekends.

Related tools for QA automation engineers

Frequently asked questions

1.What does this cron expression builder do?
It turns any cron expression into a plain-English translation, computes the next 10 run times in the timezone you pick, and generates ready-to-paste schedules for Jenkins, GitHub Actions, Kubernetes CronJob, Quartz (Spring / Java), Node-cron, Vercel Cron, systemd timers, AWS EventBridge, and Postgres pg_cron. You can also drive it in reverse — pick a natural-language preset ('every weekday at 9 AM UTC') and the tool writes the cron for you.
2.Which cron dialect does the tool use?
The 5-field POSIX cron used by crontab, Jenkins, GitHub Actions, Kubernetes, and pg_cron — minute, hour, day-of-month, month, day-of-week. The tool also supports the 6-field Quartz variant (seconds prepended) and the 7-field Quartz with year, and warns you when a target platform doesn't support a field you're using (e.g. GitHub Actions rejects seconds; Kubernetes rejects `?`).
3.Are the run times accurate?
Yes. The scheduler walks minute-by-minute (or second-by-second for Quartz) forward from the current time using the standard POSIX rules — including the OR semantics between day-of-month and day-of-week that trip up most home-grown parsers. You can switch the timezone and the next-run column recomputes instantly.
4.How is it different from crontab.guru?
Four differences that matter for SDETs and DevOps engineers: (1) framework export — one click to Jenkins pipeline syntax, GitHub Actions workflow YAML, Kubernetes CronJob manifest, or Quartz spec; (2) timezone-aware next-10-runs (crontab.guru only shows UTC-ish); (3) Quartz 6/7-field mode with second and year handling; (4) validation warnings for the specific platform you're targeting, so you catch 'GitHub Actions doesn't support @yearly' before your workflow silently fails.
5.Does it support Quartz (Spring / Java)?
Yes. Toggle 6-field mode to prepend seconds, or 7-field mode to add year. Quartz-specific tokens `?`, `L`, `W`, and `#` are validated and explained (e.g. `L` in day-of-month = last day of month; `5#3` in day-of-week = third Friday). The tool warns when you use a Quartz-only token in a Jenkins or Kubernetes export.
6.Can I use it for CI/CD schedules?
That's the primary use case. Nightly regression runs, hourly smoke tests, off-hours load tests, weekly report jobs — pick the schedule visually, verify the next 10 runs in your CI's timezone, and copy the exact syntax your platform expects (GitHub Actions cron in `on.schedule`, Jenkins `triggers { cron('H 2 * * *') }`, GitLab `only.schedule`, ArgoCD workflow schedules).
7.What is Jenkins' H (hash) syntax?
Jenkins extends standard cron with `H` — 'hash of the job name into the allowed range'. `H 2 * * *` means 'once per day, some time in the 2 AM hour, deterministically per job' — which spreads load across nodes instead of stampeding every job at 2:00:00. The tool exposes an H toggle when exporting to Jenkins.
8.Does the tool store my expressions?
Recently used expressions are saved to browser localStorage so you can revisit them next time. Nothing is sent to any server — pattern parsing, next-run computation, and code generation all run 100% in your browser.
9.Which special strings are supported (@daily, @hourly, @reboot)?
The nickname strings @yearly, @annually, @monthly, @weekly, @daily, @midnight, and @hourly all expand to the equivalent 5-field expression and are translated to the target platform's own supported form on export. `@reboot` is decoded but flagged as non-portable (crond-only — Kubernetes, GitHub Actions, and Quartz all reject it).
10.Is the cron builder free? Do I need to sign up?
Yes, 100% free with no login, no watermark, no rate limits — same as every other tool at /tools. Bookmark and share it with your team as the internal replacement for crontab.guru + jenkins-cron-tester.