Timestamp Converter
Convert Unix timestamps to human-readable dates, or convert ISO 8601 / date strings to Unix timestamps. Supports seconds and milliseconds.
Current time
Seconds: 1776166110
Milliseconds: 1776166110654
ISO 8601: 2026-04-14T11:28:30.654Z
Unix Timestamp
FAQ
What is a Unix timestamp?▼
A Unix timestamp is the number of seconds (or milliseconds) that have elapsed since January 1, 1970, 00:00:00 UTC. It is the standard way to represent time in most programming languages and databases.
How do I know if a timestamp is in seconds or milliseconds?▼
A 10-digit timestamp is in seconds. A 13-digit timestamp is in milliseconds. This tool auto-detects based on magnitude (values > 10¹² are treated as milliseconds).
What is ISO 8601?▼
ISO 8601 is the international standard for date and time representation. Example: 2026-03-10T12:00:00Z where Z indicates UTC.
Frequently Asked Questions
What is a Unix timestamp?
A Unix timestamp is the number of seconds elapsed since January 1, 1970 00:00:00 UTC (the Unix epoch). It is the standard time representation in most programming languages and databases.
Seconds or milliseconds — how do I tell?
10-digit timestamps are in seconds (seconds since epoch); 13-digit timestamps are in milliseconds. This tool auto-detects the format based on the magnitude of the number.
What is ISO 8601?
ISO 8601 is the international standard for date/time notation (e.g. 2026-03-10T14:30:00Z). The Z suffix indicates UTC. It is the recommended format for APIs and data exchange.
What is Unix Time (Epoch)?
Unix time (also called epoch time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on Thursday, 1 January 1970 — the Unix epoch. It is the standard time representation in operating system kernels, databases, log files, JWT tokens, HTTP cookies, and virtually every programming language standard library.
Unix time has a single global reference point and no timezone offsets, making it ideal for storing and comparing timestamps across distributed systems. Converting it to a human-readable date is done by the application layer, which applies the desired timezone.
Timestamp Formats Compared
| Format | Example | Notes |
|---|---|---|
| Unix seconds | 1741824000 | 10 digits (until 2286) |
| Unix milliseconds | 1741824000000 | 13 digits — used in JS Date.now() |
| ISO 8601 UTC | 2026-03-10T14:00:00Z | Recommended for APIs (RFC 3339) |
| ISO 8601 offset | 2026-03-10T15:00:00+01:00 | Includes timezone offset |
| RFC 2822 | Mon, 10 Mar 2026 14:00:00 +0000 | Used in email headers |
| HTTP date | Mon, 10 Mar 2026 14:00:00 GMT | Cache-Control, Last-Modified |
Notable Unix Timestamps
0— Unix epoch: 1 January 1970 00:00:00 UTC.1000000000— Billion-second birthday: 9 September 2001 01:46:40 UTC.1234567890— Geek milestone: 13 February 2009 23:31:30 UTC (celebrated worldwide).2147483647— Year 2038 problem: 19 January 2038 — maximum value for a signed 32-bit integer. Systems still using 32-bit time will overflow.2000000000— 18 May 2033 03:33:20 UTC.