Unix Timestamp Converter
Convert Unix epoch seconds, milliseconds, microseconds, and nanoseconds into UTC, local time, ISO 8601, RFC-style dates, and timezone-aware output. The current Unix timestamp also updates live while you are on the page.
Current Unix Time
1781162487
2026-06-11T07:21:27.981Z
The server renders the current UTC timestamp first, then your browser keeps the value live from your device clock.
At A Glance
Unix seconds: 1781162487. Milliseconds: 1781162487981. ISO: 2026-06-11T07:21:27.981Z.
Browser time zone: Detected from your device
Unix Seconds
1781162487
Unix Milliseconds
1781162487981
UTC Time
Thu, 11 Jun 2026 07:21:27 GMT
Local Time
Current local date and time
Convert Any Timestamp or Date
Paste a Unix timestamp or date string. The converter auto-detects seconds, milliseconds, microseconds, and nanoseconds for numeric values, then shows UTC, local time, and selected timezone output side by side.
Instant Answer
Awaiting input
UTC
UTC date and time appear here
Selected Time Zone
Selected timezone output appears here
Local Time
Your local browser time appears here
Relative Time
Relative time appears here
More Formats and Raw Values Expand
Unix Seconds
10-digit epoch seconds appear here
Unix Milliseconds
13-digit epoch milliseconds appear here
Unix Microseconds
16-digit epoch microseconds appear here
Unix Nanoseconds
19-digit epoch nanoseconds appear here
ISO 8601
ISO 8601 output appears here
RFC Date
RFC-style date output appears here
Quick Examples
Tap an example to fill the converter instantly.
What This Tool Handles Expand
- Unix seconds, milliseconds, microseconds, and nanoseconds
- UTC, local browser time, and a selected IANA timezone
- Pre-1970 negative timestamps when the browser supports them
- ISO 8601 and RFC-style timestamp strings in the converter input
- DST-aware date-to-timestamp generation in the selected timezone
Build a Timestamp from a Date in a Specific Time Zone
Use this section when you know the wall-clock date and time in a particular region and need the correct Unix timestamp. The selected timezone rules are applied for the chosen date, including daylight saving transitions.
Unix Seconds
Build output appears here
Unix Milliseconds
Build output appears here
UTC Result
UTC output appears here
Selected Zone Result
Selected timezone output appears here
What a Unix Timestamp Actually Is
A Unix timestamp is the number of elapsed seconds since January 1, 1970 at 00:00:00 UTC. That reference point is called the Unix epoch. Many systems still store the value in seconds, while JavaScript and many APIs use milliseconds instead.
Time zones do not change the timestamp itself. They only change how that instant is displayed as a human-readable date and time. That is why the same Unix value can appear as different clock times in London, New York, Tokyo, or your own local browser timezone.
Seconds vs Milliseconds vs Microseconds
The most common confusion is the unit. Current epoch values in seconds are usually 10 digits long. Milliseconds are usually 13 digits, microseconds are around 16 digits, and nanoseconds are around 19 digits. This page auto-detects those scales for integer inputs and also lets you override the unit manually when needed.
If an API returns a timestamp that seems decades away from the expected result, the unit is usually the reason. Converting a millisecond timestamp as if it were seconds will throw the date far into the future.
Timestamp Mistakes to Check First
A date is off by decades: the value is probably milliseconds being read as seconds, or seconds being read as milliseconds.
A local time looks wrong: the timestamp is correct, but it is being displayed in a different time zone. Convert the same instant in UTC and local time to compare.
A database value has decimals: it may include fractional seconds. Keep the fractional part if the event order matters.
An API says “expires in”: that may be a duration, not an epoch timestamp. Add it to the current timestamp before converting.
Common Developer Snippets Expand
| Language | Current Timestamp | Convert Example |
|---|---|---|
| JavaScript | Math.floor(Date.now() / 1000) | new Date(1700000000 * 1000).toISOString() |
| Python | int(time.time()) | datetime.datetime.utcfromtimestamp(1700000000) |
| PHP | time() | date('c', 1700000000) |
| PostgreSQL | EXTRACT(EPOCH FROM now()) | TO_TIMESTAMP(1700000000) |
| MySQL | UNIX_TIMESTAMP() | FROM_UNIXTIME(1700000000) |
| Unix Shell | date +%s | date -d @1700000000 -u |
These examples are reference shortcuts. Use the converter above when you need to verify a real API response, log entry, webhook payload, or database value.
Frequently Asked Questions
Does a timezone change the Unix timestamp?
No. A Unix timestamp represents one instant in time. Timezones only change how that instant is displayed for people.
How can I tell whether a value is seconds or milliseconds?
Current Unix seconds are typically 10 digits and current milliseconds are typically 13 digits. This page auto-detects the common scales for integer input and lets you override the unit when needed.
Can this page convert dates before 1970?
Yes. Negative Unix timestamps represent instants before the Unix epoch, as long as your browser's date implementation supports the range you enter.
What is the Year 2038 problem?
Some older 32-bit systems store Unix time in signed 32-bit integers, which overflow on January 19, 2038. Modern 64-bit systems avoid that practical limit for normal applications.