Time Tools Hub
About this hub
A 13-digit epoch, a meeting across zones, or a crontab missing one field can land you in 1970 or the wrong hour. This hub groups epoch conversion, timezones, and five-field cron. Cron still has no zone—set TZ on the host.
What it is for
A 13-digit epoch, a meeting across zones, or a crontab missing one field can land you in 1970 or the wrong hour. This hub groups epoch conversion, timezones, and five-field cron. Cron still has no zone—set TZ on the host.
When to use it
- An API returns a 13-digit timestamp you need as a date
- Beijing and New York need the same instant on a calendar
- A nightly backup crontab should be confirmed as 0 0 * * *
Why use these tools
- The timestamp page separates seconds and milliseconds so you do not invent 1970
- Timezone conversion uses IANA data, not a habit of adding eight hours
- Cron generate and explain work together when you inherit a crontab line
FAQ
Seconds vs milliseconds?
Ten digits are usually seconds; thirteen are milliseconds. Mixing them yields 1970 or a far-future date.
Timestamp vs timezone converter?
The timestamp page maps epoch to wall time. Use timezone conversion to move the same instant between cities.
Which timezone does cron use?
None in the expression. The host or CronJob TZ applies—especially easy to miss in containers.
What does 0 0 * * * mean?
Midnight every day. The clock still follows the machine. Read the generator’s explanation to confirm.
Beijing time vs UTC?
CST is UTC+8 with no DST in mainland China. Use timezone conversion for US and Europe DST.
Are values uploaded?
No. Conversion stays in the browser.
Tools in this hub