Current Unix Timestamp
--
--
Epoch Timestamp to Human Date
Paste a timestamp (e.g. 1747546800 or 1747546800000)
Seconds timestamp--
Milliseconds timestamp--
UTC (ISO 8601)--
Your local time--
Date (YYYY-MM-DD)--
Time (HH:MM:SS)--
Day of week--
Unix time (microseconds)--
Human Date to Epoch Timestamp
Pick or enter a date and time
Seconds timestamp--
Milliseconds timestamp--
ISO 8601--
Batch Convert (one per line)
Paste timestamps, one per line
0 results
Results will appear here...
Frequently Asked Questions
What is a Unix timestamp?
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap seconds. It is widely used in programming, databases, APIs, and log files because it is timezone-independent and easy to compute with.
Why are there 10-digit and 13-digit timestamps?
10 digits = seconds since epoch (standard Unix time). 13 digits = milliseconds since epoch (JavaScript's Date.now() and many APIs). 16 digits = microseconds. This tool auto-detects which format you are using and converts accordingly.
What happens on January 19, 2038?
The Year 2038 Problem (Y2K38) occurs when 32-bit signed integers overflow for Unix timestamps. At 03:14:07 UTC on January 19, 2038, the timestamp 2,147,483,647 is the max for a 32-bit signed integer. Systems using 64-bit integers (most modern systems) will not be affected for billions of years.
How do I get the current Unix timestamp?
This tool shows the current timestamp in real-time at the top of the page. You can also run
date +%s on Linux/macOS, Get-Date -UFormat %s in PowerShell, or Math.floor(Date.now() / 1000) in JavaScript.Are Unix timestamps affected by timezones?
No. Unix timestamps are timezone-independent - they are always measured from UTC. The same timestamp represents the same moment everywhere on Earth. Only the human-readable conversion changes based on your timezone.