Turn a calendar date and time into a Unix timestamp. Pick the time zone the date is written in: 2027-01-01 00:00 in New York (UTC−5) is 1798779600, five hours after the same wall-clock time in UTC. The result is shown in seconds, milliseconds and ISO 8601 with the offset, ready to paste into code or a database query.
How to use
- The big number is the current Unix time in seconds; tap it (or the milliseconds) to copy. Pause freezes it.
- Paste a timestamp: seconds, milliseconds, microseconds or nanoseconds are detected from the number of digits. Pick a unit to override.
- Read the date in UTC, your local time, ISO 8601, RFC 2822 and any time zone. Tap a row to copy it.
- Use Date → timestamp to turn a date and time in any zone into seconds and milliseconds, or Batch to convert a whole list to CSV.
- A Unix timestamp counts seconds since January 1, 1970, 00:00:00 UTC, ignoring leap seconds. It is the same everywhere on Earth.
- Up to 11 digits is read as seconds, 12–14 as milliseconds, 15–17 as microseconds and 18+ as nanoseconds.
- You can also paste a date such as 2025-03-01T12:00:00Z to get its timestamp.
- JavaScript: Math.floor(Date.now() / 1000)
- Python: import time; int(time.time())
- PHP: time()
- Go: time.Now().Unix()
- Java: Instant.now().getEpochSecond()
- SQL: SELECT EXTRACT(EPOCH FROM NOW())::bigint; — MySQL: SELECT UNIX_TIMESTAMP();
- Bash: date +%s
What a Unix timestamp is
Unix time counts the seconds since January 1, 1970, 00:00:00 UTC, the Unix epoch, ignoring leap seconds. The same number means the same instant everywhere on Earth; only the displayed local time changes. For example, 1000000000 was September 9, 2001, 01:46:40 UTC, and 1798761600 is January 1, 2027, 00:00:00 UTC.
Up to 11 digits is read as seconds, 12–14 as milliseconds, 15–17 as microseconds and 18 or more as nanoseconds. You can override the unit when a value is ambiguous.
The year 2038 problem
Systems that store Unix time in a signed 32-bit integer run out at 2147483647, which is January 19, 2038, 03:14:07 UTC; one second later the value wraps to a date in 1901. Modern languages and databases use 64-bit values, which last for billions of years, but older embedded systems and file formats can still be affected.
Frequently asked questions
What is the current Unix timestamp?
The large number at the top of the page is the current Unix time in seconds, updating live. Tap it to copy it, or tap the milliseconds value below.
How do I convert a Unix timestamp to a date?
Paste the number into the converter. The date appears in UTC, your local time, ISO 8601, RFC 2822 and any time zone you choose.
Is my timestamp in seconds or milliseconds?
Count the digits. Current dates have 10 digits in seconds and 13 in milliseconds; the converter detects this for you.
Does a Unix timestamp depend on the time zone?
No. It always counts from midnight UTC on January 1, 1970. Time zones only affect how the same instant is displayed.
How do I get the current timestamp in code?
JavaScript: Math.floor(Date.now() / 1000). Python: int(time.time()). PHP: time(). Bash: date +%s. Go: time.Now().Unix().
What happens in 2038?
Signed 32-bit timestamps overflow after January 19, 2038, 03:14:07 UTC. Software that uses 64-bit time is not affected.