Unix Timestamp Converter
Convert between Unix timestamps and human-readable dates instantly — no server, no signup, no limits.
Timestamp ⇄ Date
Runs entirely in your browserType in either field — the other updates live. Nothing is sent to any server.
What is a Unix timestamp?
A Unix timestamp (epoch time) is the number of seconds elapsed since 00:00:00 UTC on January 1, 1970, not counting leap seconds. It's a single, timezone-independent number that represents an exact point in time.
Epoch Start
Jan 1, 1970, 00:00:00 UTC — timestamp 0
Year 2038 Problem
32-bit signed timestamps overflow at Jan 19, 2038, 03:14:07 UTC
What is Unix Time?
Unix time (also called epoch time or POSIX time) counts seconds since an arbitrary reference point — the Unix epoch — chosen by early Unix developers.
Because it's a single incrementing number with no timezone attached, Unix time is the universal way computers store and compare points in time — from database rows to JWT tokens to HTTP cache headers.
- Counts seconds (or milliseconds) since Jan 1, 1970 UTC
- Ignores leap seconds — every day is exactly 86,400 seconds
- Timezone-independent by design
- Native support in virtually every programming language and database
Epoch to Date
That last one is the Year 2038 problem — the max value of a signed 32-bit second counter.
Common Timestamp Formats
The same instant in time, represented a few different ways.
| Format | Example | Used by |
|---|---|---|
| Unix Seconds | 1751375530 |
Unix/Linux, JWT iat/exp, most REST APIs |
| Unix Milliseconds | 1751375530000 |
JavaScript Date.now(), Java currentTimeMillis() |
| ISO 8601 | 2025-07-01T13:12:10.000Z |
JSON APIs, logs, most modern data formats |
| UTC / RFC 2822 | Tue, 01 Jul 2025 13:12:10 GMT |
HTTP headers, email Date: headers |
| UUID v1 / v6 / v7 | 017f22e2-79b0-7cc3-98c4-dc0c0c07398f |
Sortable database IDs — timestamp embedded in the ID itself. Decode one with our UUID Timestamp Decoder. |
How This Converter Works
This tool uses your browser's native Date object to convert between Unix timestamps and calendar dates entirely on your device.
Typing a value into either field immediately recalculates the other, along with every output format below it:
- Parse the input as either a Unix timestamp or a calendar date
- Build a single internal
Dateinstant from it - Re-render every field and output format from that one instant
- Nothing is ever sent over the network
Common Use Cases
Unix timestamps show up constantly in:
iat / exp claims
Database created_at columns
Server & application logs
REST API request/response bodies
Cache & session expiry (TTL)
Cron & job scheduling
HTTP cache headers
Video/audio metadata
Blockchain transaction timestamps
Frequently Asked Questions
Concise answers about Unix time and this converter.
00:00:00 UTC on January 1, 1970, not counting leap seconds. It's a single number that unambiguously represents a point in time regardless of timezone.
Date.now() and many modern APIs instead use milliseconds since the epoch for finer precision. A millisecond timestamp is exactly 1000 times larger than the equivalent second timestamp.
2,147,483,647 seconds after the epoch — which corresponds to 03:14:07 UTC on January 19, 2038. After that point, the value overflows and wraps to a negative number, causing incorrect dates on affected systems. Most modern 64-bit systems are unaffected.
Explore All Free Developer Tools
UUIDs, QR codes, barcodes, image tools, converters and more — all free, all client-side.