Date & Time
Unix timestamps, cron expressions and timezone conversions, computed live without sending anything anywhere.
- Cron Expression Parser Type a cron expression to see it explained in plain English, with the next 10 run times in your timezone or UTC and a field-by-field breakdown.
- Timezone Converter Convert a date and time between IANA timezones and compare several zones at once, with day-change badges. Runs on your browser's built-in Intl data.
- Unix Timestamp Converter Convert Unix timestamps to local, UTC and ISO 8601 dates — and dates back to epoch seconds — in your browser. Auto-detects seconds, milliseconds, microseconds.
Three time problems, three tools. A number like 1751500800 sitting in a log line or a database row is a Unix timestamp — the count of seconds since midnight UTC on 1 January 1970 — and the Unix Timestamp Converter turns it into a readable date in your local zone and back again, handling both second and millisecond precision so a JavaScript Date.now() value does not trip you up. When an event is quoted in one city and you need it in another, the Timezone Converter lines up the same instant across zones and folds in daylight-saving offsets, so 9am in Sydney lands on the correct hour in London without counting on your fingers.
And when you come across a line like */15 9-17 * * 1-5 in a crontab or a job scheduler, the Cron Expression Parser reads it back in plain English — every 15 minutes, from 9am to 5pm, Monday to Friday — and lists the next several times it will fire.
Each tool computes in the browser against its built-in timezone database, so nothing about your logs or schedule is sent anywhere. The detail most worth watching is cron's day-of-month versus day-of-week rule: when you restrict both fields at once, most daemons combine them with OR rather than AND, which is the usual reason a job runs more often than its author expected.