convert between Unix timestamps and human-readable dates. live clock, multiple output formats, timezone selector.
Convert between Unix timestamps, ISO 8601 strings, and human-readable dates. Paste any common format in either direction and see all the others. Includes the current moment as a one-click button.
A Unix timestamp is the number of seconds since midnight UTC on January 1, 1970 — the “Unix epoch.” Pick any moment in time, count the seconds back to that reference point, and that integer is the timestamp. The right now as you read this is somewhere around 1.78 × 109.
Most modern systems use milliseconds instead of seconds (so the same moment is 1.78 × 1012), because subsecond precision matters when you are timing events in a distributed system. JavaScript's Date.now()returns milliseconds. Python's time.time() returns seconds with a decimal. The tool detects which you have based on magnitude.
Unix timestamps stored as signed 32-bit integers wrap around on January 19, 2038 — the timestamp 2147483647 is the largest value that fits, and incrementing it overflows to a negative number that decodes to 1901. Most modern systems use 64-bit timestamps, which push the wraparound to a date 292 billion years in the future, but legacy code that explicitly uses int32 for timestamps is still out there. If you maintain anything that touches timestamps, the next 13 years are when this matters.
ISO 8601 is the “just write the date in a sensible order” format: 2026-04-25T14:23:11Z. Year, month, day, T separator, hour, minute, second, and a timezone designator. The Z at the end means UTC; everything else is an offset like -05:00 or +09:00.
ISO 8601 is the right text format for timestamps stored as strings. It is unambiguous (unlike “04/25/26” which means different things in different countries), it sorts lexicographically into chronological order, and every modern programming language can parse it without a third-party library.
Storage advice
TIMESTAMPTZ). For text logs and APIs, use ISO 8601 strings. Do not store Unix epochs as integers in user-facing systems unless the column is labeled clearly — they are unreadable on inspection.A Unix timestamp is timezone-agnostic. It is a count of seconds since a fixed UTC moment. The same timestamp decodes to different wall-clock times in different timezones — that is the timezone's job, not the timestamp's.
Where this gets people: a server in UTC and a user in PST looking at “the same moment” both see the same timestamp but different wall-clock displays. That is correct behavior. The bug is only when one of those is secretly converting incorrectly — usually because someone used a local-time function (like JavaScript's new Date(2026, 3, 25)) where they should have used a UTC-aware function.
Unix time deliberately ignores leap seconds. UTC has had 27 of them inserted since 1972 to keep atomic time in sync with Earth's rotation. Unix timestamps treat every minute as exactly 60 seconds, which means around the moment of a leap second, the Unix timestamp is briefly ambiguous. Most systems handle this by smearing the leap second across a longer window (Google does it across 24 hours; AWS does it differently). For 99.99% of use cases, leap seconds are a curiosity rather than a bug.
Convert between Unix timestamps, ISO 8601 strings, and human-readable dates. Paste any common format in either direction and see all the others. Includes the current moment as a one-click button.
A Unix timestamp is the number of seconds since midnight UTC on January 1, 1970 — the “Unix epoch.” Pick any moment in time, count the seconds back to that reference point, and that integer is the timestamp. The right now as you read this is somewhere around 1.78 × 109.
Most modern systems use milliseconds instead of seconds (so the same moment is 1.78 × 1012), because subsecond precision matters when you are timing events in a distributed system. JavaScript's Date.now()returns milliseconds. Python's time.time() returns seconds with a decimal. The tool detects which you have based on magnitude.
Unix timestamps stored as signed 32-bit integers wrap around on January 19, 2038 — the timestamp 2147483647 is the largest value that fits, and incrementing it overflows to a negative number that decodes to 1901. Most modern systems use 64-bit timestamps, which push the wraparound to a date 292 billion years in the future, but legacy code that explicitly uses int32 for timestamps is still out there. If you maintain anything that touches timestamps, the next 13 years are when this matters.
ISO 8601 is the “just write the date in a sensible order” format: 2026-04-25T14:23:11Z. Year, month, day, T separator, hour, minute, second, and a timezone designator. The Z at the end means UTC; everything else is an offset like -05:00 or +09:00.
ISO 8601 is the right text format for timestamps stored as strings. It is unambiguous (unlike “04/25/26” which means different things in different countries), it sorts lexicographically into chronological order, and every modern programming language can parse it without a third-party library.
Storage advice
TIMESTAMPTZ). For text logs and APIs, use ISO 8601 strings. Do not store Unix epochs as integers in user-facing systems unless the column is labeled clearly — they are unreadable on inspection.A Unix timestamp is timezone-agnostic. It is a count of seconds since a fixed UTC moment. The same timestamp decodes to different wall-clock times in different timezones — that is the timezone's job, not the timestamp's.
Where this gets people: a server in UTC and a user in PST looking at “the same moment” both see the same timestamp but different wall-clock displays. That is correct behavior. The bug is only when one of those is secretly converting incorrectly — usually because someone used a local-time function (like JavaScript's new Date(2026, 3, 25)) where they should have used a UTC-aware function.
Unix time deliberately ignores leap seconds. UTC has had 27 of them inserted since 1972 to keep atomic time in sync with Earth's rotation. Unix timestamps treat every minute as exactly 60 seconds, which means around the moment of a leap second, the Unix timestamp is briefly ambiguous. Most systems handle this by smearing the leap second across a longer window (Google does it across 24 hours; AWS does it differently). For 99.99% of use cases, leap seconds are a curiosity rather than a bug.
PDF utilities, image tools, developer helpers — all free, no signup.
Count words, characters, sentences, paragraphs, and reading time in real-time.
Generate lorem ipsum placeholder text by paragraphs, sentences, or words.
Convert HEIC/HEIF photos from iPhone to universal JPG format.
Crop images with preset aspect ratios or freeform selection.
Generate favicons at every size from any image.
Encode text or files to Base64, or decode Base64 back to text and files.