Available tool
Base64 Encoder / Decoder
Encode text to Base64 and decode Base64 back to readable text locally in your browser.
Open toolDeveloper Tools
Explain standard five-field cron expressions and preview upcoming run times locally in your browser.
Runs locally in your browser
Explain a five-field cron expression and preview upcoming run times in your local time zone.
How to use it
Use this Cron Parser to explain backend schedule expressions before putting them into jobs, workers, deployment scripts, or monitoring checks.
The tool supports the common five-field cron shape:
minute hour day-of-month month day-of-week
Examples include */15 * * * * for every 15 minutes and 0 9 * * MON-FRI for 9:00 on weekdays.
The first version supports:
* for every allowed value.0 or 15.1,15,30.9-17.*/10 or 9-17/2.JAN and MON-FRI.It does not support Quartz-specific seconds, year fields, ?, L, W, or # syntax.
Always confirm cron behavior in the scheduler you deploy to. Linux cron, Kubernetes CronJobs, GitHub Actions schedules, Cloudflare Workers Cron Triggers, and Quartz can differ in supported syntax and time-zone handling.
Use the Unix Timestamp Converter when comparing scheduled run times with log timestamps or epoch values. For API retry patterns that often run from scheduled jobs, read Idempotency in APIs Explained.
Related tools
These local-first tools often pair well with Cron Parser.
Available tool
Encode text to Base64 and decode Base64 back to readable text locally in your browser.
Open toolAvailable tool
Convert CSV, TSV, or delimited text to JSON locally in your browser for API mocks, imports, fixtures, and documentation.
Open toolAvailable tool
Format, validate, minify, and copy JSON locally in your browser without sending input to a server.
Open toolFAQ
No. Parsing and next-run previews run locally in your browser, and the tool does not upload cron expressions.
It supports standard five-field cron expressions: minute, hour, day of month, month, and day of week.
No. The first version does not support Quartz seconds, year fields, question marks, or special L/W/# syntax.
Next run times are shown in your browser's local time zone so they match the machine where you are testing.