/

UNIX Timestamp Converter

Processed Client Side

Convert UNIX timestamps to human-readable dates and vice versa. Supports seconds and milliseconds.

Input
Current UNIX time
1,788,854,323
UNIX:1,788,854,280
Results
Valid timestamp0s agoPast
Local9/8/2026, 7:58:43 AM
UTCTue, 08 Sep 2026 07:58:43 GMT
ISO 86012026-09-08T07:58:43.000Z
Date only9/8/2026
Time only7:58:43 AM
Unix (s)1788854323
Unix (ms)1788854323000
DayTuesday
Relative0s ago

Bookmark this tool now — skip the search next time you need it.

About UNIX Timestamp Converter

This tool runs entirely in your browser. Whatever you paste is processed on your own device and is never uploaded, logged, or sent to any server.

Convert UNIX timestamps into readable dates and readable dates back into UNIX timestamps. A UNIX timestamp is the number of seconds since 1 January 1970 UTC — compact and unambiguous for machines, unreadable for people, which is why every log file and API response eventually needs translating. Paste a timestamp and you get the moment expressed nine ways at once: local time, UTC, ISO 8601, date only, time only, seconds, milliseconds, day of the week, and a relative description such as "3 hours ago". The current UNIX time is displayed live at the top and can be dropped into the input with one click.

Key features

  • Timestamp to date, and date to timestamp, both directions on one page
  • Nine simultaneous output formats: local, UTC, ISO 8601, date only, time only, Unix seconds, Unix milliseconds, weekday, and relative time
  • Live current UNIX time with a Use now button that fills the input instantly
  • Past and Future badges so the relationship to right now is obvious at a glance
  • Accepts both seconds and milliseconds and interprets the magnitude correctly
  • Relative descriptions such as "3 hours ago" or "in 2 days" for quick log triage
  • Copy any individual output value
  • Runs entirely in your browser, using your machine local timezone for the local values

How to use it

  1. Paste a UNIX timestamp into the timestamp field, or click Use now for the current time.
  2. Read the conversions — local, UTC, ISO 8601, and the rest are all shown together.
  3. To go the other way, pick a date and time in the date field and read the timestamp it produces.
  4. Check the Past or Future badge and the relative description for context.
  5. Copy whichever representation you need.

Tips & common mistakes

  • UNIX timestamps are seconds; JavaScript Date works in milliseconds. Forgetting the factor of 1000 puts your date in 1970, which is the classic symptom.
  • A timestamp around 1.7 billion is seconds and lands in the present day. One around 1.7 trillion is milliseconds. That magnitude check identifies the unit instantly.
  • A timestamp itself has no timezone — it is always an absolute moment in UTC. Only the formatted output has a timezone, which is why the local and UTC rows here differ.
  • Use ISO 8601 when passing dates between systems. It sorts lexicographically, is unambiguous about ordering, and is what JSON APIs should be emitting.
  • A date rendering as 1 January 1970 means your timestamp was zero, null, or an unparsed empty string somewhere upstream.
  • The 32-bit signed timestamp overflows on 19 January 2038. Any system still storing timestamps in a 32-bit integer will need migrating before then.
  • Local values use your own machine timezone and daylight-saving rules, so the same timestamp shown to a colleague elsewhere will read differently — compare using the UTC row.
  • Prefer a form-based date and time picker over free typing? The Epoch / Date Converter does the same conversion.

Related tools

Browse all 3 Number tools

Frequently asked questions

10

Paste your Unix timestamp into the input field — the tool auto-detects seconds vs milliseconds and shows the date and time in both local and UTC format.

A Unix timestamp is the number of seconds (or milliseconds) elapsed since January 1, 1970 00:00:00 UTC. It is the most common way to represent dates in APIs and databases.

Yes — if the number is greater than 10 to the power of 12 it is treated as milliseconds (JavaScript Date format); otherwise it is treated as seconds (standard Unix time).

Both local time (using your browser's system timezone) and UTC are shown simultaneously so you can compare them without manual conversion.

Click the "Now" button to fill in the current timestamp automatically. You can also use Date.now() in JavaScript or date +%s in a terminal.

Check the magnitude. A present-day value around 1.7 billion is seconds; around 1.7 trillion is milliseconds. Getting this wrong by a factor of 1000 is what puts a date in 1970 or far in the future.

The timestamp evaluated to zero — typically a null, an empty string, or an unparsed value somewhere upstream. That is the epoch itself, so it is a reliable signal that the value never arrived.

No. A timestamp is an absolute moment measured in UTC. Only the formatted output carries a time zone, which is why the local and UTC rows here show different wall-clock times for the same value.

ISO 8601. It sorts correctly as plain text, is unambiguous about ordering, and is what JSON APIs are expected to emit. Reserve raw timestamps for internal storage and arithmetic.

A signed 32-bit timestamp overflows on 19 January 2038 and wraps to a negative number. Any system still storing timestamps in a 32-bit integer needs migrating to 64-bit before then.