# Unix Timestamp Converter

> Free in-browser tool that converts Unix timestamps to readable dates and dates back to Unix timestamps, in seconds, milliseconds, microseconds or nanoseconds, with timezone support and batch conversion. Independent tool, not affiliated with any vendor. Updated 2026-11-06. Full page: https://lab.awaara.cn/unix-timestamp-converter/

## What it does

- Live clock: the current Unix timestamp in seconds and milliseconds, ticking once a second, with copy buttons. Both numbers name the same moment.
- Timestamp to date: paste a timestamp and get UTC, local time, a chosen IANA timezone, ISO 8601, RFC 2822, relative time, day of week, day of year, ISO week number, daylight saving time status, and the value back in seconds and milliseconds. The unit auto-detects from the size of the number (under 100 billion is seconds, under 100 trillion is milliseconds, under 100 quadrillion is microseconds, larger is nanoseconds), or can be picked by hand.
- Date to timestamp: pick a date and time and a timezone, and get the Unix timestamp in seconds and milliseconds plus the ISO 8601 UTC form. The date is read as a wall-clock time in the chosen zone, with daylight saving time from that zone's own rules.
- Batch converter: paste up to 200 lines, timestamps or whole log lines. The first number of 8 to 19 digits in each line is converted, the rest of the line is ignored, and lines with no such number are reported, not silently dropped. Results can be copied out as converted lines.
- Everything runs locally in the browser. Nothing is sent to a server; the page works offline once loaded.

## What a Unix timestamp is

- A Unix timestamp (Unix time, POSIX time, epoch time) is the number of seconds since January 1, 1970, 00:00:00 UTC, the Unix epoch. 1716192000 is May 20, 2024, at 08:00:00 UTC. The number itself carries no timezone.
- Unix time ignores leap seconds: every day is exactly 86,400 seconds. 27 leap seconds have been inserted since 1972.
- Units: seconds (10 digits today, most APIs and databases), milliseconds (13 digits, JavaScript Date.now(), Java System.currentTimeMillis()), microseconds (16 digits, Python time.time_ns()), nanoseconds (19 digits, Go time.Now().UnixNano()).
- Negative timestamps name moments before the epoch: -1 is December 31, 1969, 23:59:59 UTC.
- The year 2038 problem: signed 32-bit storage tops out at 2147483647, January 19, 2038, 03:14:07 UTC, then wraps to a negative number read as December 1901. 64-bit systems are not affected.
- Notable values: 0 is the epoch, 1000000000 is 2001-09-09 01:46:40 UTC, 1234567890 is 2009-02-13 23:31:30 UTC, 1700000000 is 2023-11-14 22:13:20 UTC.

## Code snippets (from the page)

- JavaScript: new Date(seconds * 1000), Math.floor(Date.now() / 1000), Math.floor(date.getTime() / 1000). The JavaScript and Python snippets were run while the page was written.
- Python: datetime.fromtimestamp(timestamp, tz=timezone.utc), int(time.time()).
- Go: time.Unix(1716192000, 0).UTC(), time.Now().Unix(), time.Now().UnixNano().
- SQL and shell: PostgreSQL to_timestamp(1716192000), MySQL FROM_UNIXTIME(1716192000), GNU date -u -d @1716192000.

## Sources

- Mozilla Developer Network, Date: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date
- Wikipedia, Unix time: https://en.wikipedia.org/wiki/Unix_time
- Internet Engineering Task Force, RFC 3339: Date and Time on the Internet: https://www.rfc-editor.org/rfc/rfc3339
- Go project, time package: https://pkg.go.dev/time
- Python Software Foundation, datetime: https://docs.python.org/3/library/datetime.html