Dates ⇄ Unix timestamp, in UTC and your local time
Paste one or more epochs (seconds or milliseconds), one per line.
| Epoch | UTC | Local |
|---|
| Format | Example |
|---|---|
| Unix timestamp (s) | 1735689600 |
| Unix timestamp (ms) | 1735689600000 |
| ISO 8601 / RFC 3339 | 2025-01-01T00:00:00.000Z |
| RFC 2822 | Wed, 01 Jan 2025 00:00:00 GMT |
| SQL datetime | 2025-01-01 00:00:00 |
It's the number of seconds (or milliseconds) elapsed since January 1, 1970 00:00:00 UTC, known as the "Unix epoch". Most languages and databases use it to represent dates in a compact, timezone-independent way.
1970 was chosen as an arbitrary reference point when Unix was designed, and it has since become the de facto standard for representing time in computer systems.
JavaScript and many web APIs use milliseconds (around 13 digits), while Unix, many databases and backend languages use seconds (around 10 digits). This tool auto-detects which one you're using.
Yes. An epoch timestamp represents a single instant in UTC; the local time you see depends on your browser or system's timezone, not the number itself.