Loading Shrinkify...
Loading Shrinkify...
Build and decode cron expressions in plain English, and convert Unix timestamps to dates and back.
minute · hour · day-of-month · month · day-of-week
Valid examples: 1-5, */15, 1,5,10. Invalid: 1-5-10, 1--5, */2/3.
Runs at 09:00 on Monday, Tuesday, Wednesday, Thursday, and Friday.
Decode any crontab line into plain English and preview the next five run times.
Convert epoch seconds or milliseconds to local, UTC, and ISO 8601 — and back.
Cron and Unix time are two of the most common sources of confusion in backend and DevOps work. These tools turn cryptic expressions and integer timestamps into something you can read at a glance, with instant validation so mistakes surface before they reach a scheduler or a database.
Everything runs locally in your browser, which means schedules for internal infrastructure and timestamps pulled from private logs are never uploaded to a server.
Standard 5-field crontab: minute, hour, day-of-month, month, and day-of-week. It supports *, ranges (1-5), steps (*/15), and lists (1,3,5), and follows the convention that when both day-of-month and day-of-week are restricted, a run fires when either matches.
Unix time can be expressed in seconds (10 digits) or milliseconds (13 digits). The converter auto-detects which you pasted and shows both, plus local time, UTC, and ISO 8601.
No. All parsing and calculation happens in your browser, so internal infrastructure schedules and timestamps from private logs never leave your device.
Run times are shown in your local browser timezone for readability. Remember that most servers run cron in UTC, so account for the offset when deploying.