Unix Timestamp Converter
Epoch time to dates, dates to epoch time, across every time zone
1790000000 into readable dates, turns
dates back into timestamps, and shows the same moment in as many time
zones as you like. It detects whether a timestamp is in seconds,
milliseconds, microseconds or nanoseconds, and shows the current Unix
time live at the top of the page.
What Is a Unix Timestamp?
A Unix timestamp, also called epoch time or POSIX time, is the number of seconds since 00:00:00 UTC on 1 January 1970. Because it is a single number and the same everywhere in the world, it is the standard way to store and exchange moments in time in databases, APIs, logs and file systems. Times before 1970 are negative.
Seconds, Milliseconds, Microseconds or Nanoseconds?
- Seconds (10 digits today): Unix, PHP, Python's
time(), most APIs - Milliseconds (13 digits): JavaScript, Java, many JSON APIs
- Microseconds (16 digits): PostgreSQL internals, some analytics tools
- Nanoseconds (19 digits): Go, InfluxDB, OpenTelemetry traces
In Auto mode the converter picks the unit from the number of digits, and you can override it at any time. Nanosecond values are read exactly, without the rounding errors ordinary JavaScript numbers would introduce.
How to Convert a Timestamp to a Date
Step 1: Enter the Timestamp
Paste the number into "Timestamp to date". Commas, spaces and
underscores are ignored, and decimals like
1790000000.5 are accepted. Click "Convert now" to load
the current time.
Step 2: Read the Results
You get the date in your local time and in UTC, ISO 8601 and RFC 2822 strings, a relative time such as "3 days ago", the value in seconds and milliseconds, and the day of the year and ISO week number. Every row has its own Copy button.
Step 3: Compare Time Zones
The "In other time zones" table shows the same moment in several cities with their UTC offsets, including half-hour and 45-minute zones like India and Nepal. Add any IANA time zone from the list or remove the ones you don't need; your choice is remembered.
How to Convert a Date to a Timestamp
In "Date to timestamp", pick a date and time and choose the time
zone it belongs to. The converter accounts for daylight saving time
in that zone, so 12:00 in New York gives a different timestamp in
July than in January. You can also type a date as text, for example
2026-09-27T10:30:00Z or
2026-09-27T10:30:00+02:00. If the text has no time zone,
it is read as your local time, and the tool says so.
Unix Time in Popular Languages
| Language | Current timestamp | Timestamp to date |
|---|---|---|
| JavaScript | Math.floor(Date.now() / 1000) | new Date(1790000000 * 1000).toISOString() |
| Python | int(time.time()) | datetime.fromtimestamp(1790000000, tz=timezone.utc) |
| PHP | time() | date('c', 1790000000) |
| Go | time.Now().Unix() | time.Unix(1790000000, 0).UTC() |
| Java | Instant.now().getEpochSecond() | Instant.ofEpochSecond(1790000000) |
| PostgreSQL | extract(epoch from now()) | to_timestamp(1790000000) |
| MySQL | UNIX_TIMESTAMP() | FROM_UNIXTIME(1790000000) |
| Bash (GNU) | date +%s | date -u -d @1790000000 |
Common Pitfalls
- Mixing units: A date in 1970 usually means milliseconds were read as seconds or the other way round
- Local vs UTC: Timestamps have no time zone. Only the display does, so always say which one you mean
- Daylight saving: Some local times happen twice a year and some not at all. Store UTC timestamps and convert only for display
- The Year 2038 problem: Signed 32-bit timestamps run out at
2147483647, which is 19 January 2038 03:14:07 UTC. Use 64-bit integers - Leap seconds: Unix time ignores them, so every day is exactly 86,400 seconds
Privacy
All conversions run in your browser using its built-in time zone data. Nothing you enter is sent anywhere.
Conclusion
Whether you are reading a log line, checking a token expiry or scheduling across continents, the converter gives you every format and time zone at once. Try it at tools.typinks.com/timestamp-converter.
Got a Timestamp to Decode?
Paste it in and see it in every format and time zone.
Launch Timestamp Converter