Unix / Epoch Timestamp Converter
Convert Unix epoch timestamps to human-readable dates (Local and UTC), or convert standard date configurations back to numeric timestamps.
Current Unix Epoch Timestamp:
0
Related Tools
Shows the current Unix epoch second, ticking live, and converts both ways: an epoch number into local time, UTC and ISO-8601, or a picked date and time back into epoch seconds and milliseconds. The clock reads your system time and all conversion is done client-side.
How to use it
- Read the live epoch number at the top of the page.
- Paste an epoch number into the first field and press Convert Date for local time, UTC and ISO-8601.
- Or pick a date and time in the second field and press Convert Epoch for the seconds and milliseconds values.
Worked example
1716943183becomesConverted Results:
Local Time: Wed May 29 2024 01:39:43 GMT+0100 (British Summer Time)
UTC Time: Wed, 29 May 2024 00:39:43 GMT
ISO-8601: 2024-05-29T00:39:43.000Z
Assumed Unit: SecondsThe Local Time line is formatted with your machine's timezone and offset name; the UTC and ISO lines are fixed. This was run on a Europe/London machine.
date field set to 2024-01-01T00:00becomesConverted Results:
Unix Timestamp (Seconds): 1704067200
Unix Timestamp (Milliseconds): 1704067200000
UTC Date String: Mon, 01 Jan 2024 00:00:00 GMTA datetime-local field has no timezone, so the value is read as local time. On a machine in Britain in January that equals UTC.
When to use it
- Working out what a Unix timestamp in an API response or a log line actually means.
- Turning a release date or an event time into epoch seconds for a config file.
- Reading the exact current epoch value while writing a cache TTL or a token expiry.
What it does not do
- The unit is guessed from the size: any number above 50,000,000,000 is treated as milliseconds and everything else as seconds, so a seconds value from the far future would be misread.
- The live clock takes the time from your operating system, so it inherits any clock skew or wrong timezone on the machine.
- The date field is a native datetime-local picker with no timezone selector, so a value like 09:00 means 09:00 where you are, not in a zone you choose.
- Epoch output is always whole seconds; sub-second precision is only visible in the ISO string, and the millisecond figure is never broken out separately in the epoch-to-date direction.