Unix timestamp converter (Epoch)
Paste a timestamp or type a date in any format and instantly get every representation: Unix seconds and milliseconds, ISO 8601, RFC 2822, a readable date in your time zone and relative time.
Processed 100% in your browser
| Unix (seconds) | ||
|---|---|---|
| Unix (milliseconds) | ||
| ISO 8601 (UTC) | ||
| ISO 8601 (selected zone) | ||
| Readable date | ||
| RFC 2822 | ||
| HTTP · RFC 7231 | ||
| Relative | ||
| Calendar |
Get the current timestamp in your language
| JavaScript | Math.floor(Date.now() / 1000) |
|---|---|
| Python | import time; int(time.time()) |
| PHP | time() |
| Java | Instant.now().getEpochSecond() |
| C# | DateTimeOffset.UtcNow.ToUnixTimeSeconds() |
| Go | time.Now().Unix() |
| Rust | SystemTime::now().duration_since(UNIX_EPOCH)?.as_secs() |
| Ruby | Time.now.to_i |
| MySQL | SELECT UNIX_TIMESTAMP(); |
| PostgreSQL | SELECT EXTRACT(EPOCH FROM NOW())::bigint; |
| Bash | date +%s |
| PowerShell | [DateTimeOffset]::UtcNow.ToUnixTimeSeconds() |
Ctrl + Enter runCtrl + C copy result
How to use
- 1Paste a Unix timestamp (10, 13, 16 or 19 digits) or a date such as “2026-10-15 10:30”.
- 2The unit is detected automatically; change it under “Unit” if needed.
- 3Choose the time zone for the readable date.
- 4Copy any format with its button or share a link to the conversion.
Use cases
- Read dates from logs, databases or API responses stored as epoch.
- Debug JWT claims (exp, iat) and HTTP cache headers.
- Get the timestamp of a specific date for SQL queries or cron jobs.
- Check what local time an event in another time zone corresponds to.
Frequently asked questions
What is a Unix (epoch) timestamp?
The number of seconds elapsed since January 1, 1970 at 00:00:00 UTC (the “Unix epoch”), not counting leap seconds. It is time-zone independent, which is why systems, databases and APIs use it.
How do I know if a timestamp is in seconds or milliseconds?
By its length: current dates have 10 digits in seconds, 13 in milliseconds (JavaScript, Java), 16 in microseconds (Python, PostgreSQL) and 19 in nanoseconds (Go). The tool detects it automatically.
What is the year 2038 problem?
Systems that store the timestamp as a signed 32-bit integer will overflow on January 19, 2038 at 03:14:07 UTC. 64-bit systems have no practical limit.
What is the difference between ISO 8601 and RFC 2822?
ISO 8601 (2026-10-15T10:30:00Z) is the standard format for data and APIs and sorts alphabetically. RFC 2822 (Thu, 15 Oct 2026 10:30:00 +0000) is used in email headers and RSS feeds.
Are negative timestamps valid?
Yes: they represent dates before 1970. For example, -86400 is December 31, 1969.