Timestamp / Epoch Converter

    Timestamp / Epoch Converter

    Convert Unix epoch ↔ human dates across every major time zone

    Live current time
    Epoch (s):1777106446
    Epoch (ms):1777106446857
    ISO:2026-04-25T08:40:46.857Z
    Conversions
    Unix seconds1777106446
    Unix milliseconds1777106446000
    ISO 8601 (UTC)2026-04-25T08:40:46.000Z
    RFC 2822Sat, 25 Apr 2026 08:40:46 GMT
    Local time4/25/2026, 8:40:46 AM
    Relativejust now
    In every major time zone
    UTC25 Apr 2026, 08:40:46
    America/Los_Angeles25 Apr 2026, 01:40:46
    America/New_York25 Apr 2026, 04:40:46
    America/Chicago25 Apr 2026, 03:40:46
    America/Sao_Paulo25 Apr 2026, 05:40:46
    Europe/London25 Apr 2026, 09:40:46
    Europe/Paris25 Apr 2026, 10:40:46
    Europe/Berlin25 Apr 2026, 10:40:46
    Asia/Dubai25 Apr 2026, 12:40:46
    Asia/Kolkata25 Apr 2026, 14:10:46
    Asia/Shanghai25 Apr 2026, 16:40:46
    Asia/Tokyo25 Apr 2026, 17:40:46
    Australia/Sydney25 Apr 2026, 18:40:46

    About the Timestamp / Epoch Converter

    A Unix timestamp is the number of seconds (or milliseconds) since January 1, 1970 UTC — the dominant way computers encode time. Converting to a human-readable date is a daily task when reading logs, debugging APIs, or correlating database rows across services. This converter does both directions and shows the same instant across every major time zone so you can reason about global events quickly.

    Features

    How it works

    1. Pick Epoch → Date or Date → Epoch.
    2. Enter a timestamp (seconds or milliseconds) or pick a date and time.
    3. See every common format rendered — ISO, RFC, local, relative.
    4. Scroll down for the same instant in 13 world time zones.

    Use cases

    Frequently asked questions

    Seconds vs. milliseconds — which does my system use?

    +

    Unix and most databases use seconds (10 digits). JavaScript Date.now() and most APIs built after 2010 use milliseconds (13 digits). If your timestamp is 10 digits long, use seconds.

    Is there a year-2038 problem here?

    +

    Not for this tool — JavaScript uses 64-bit doubles for Date, so we handle timestamps up to year 275,760. Your backend might still have the 32-bit int overflow problem (Jan 19, 2038).

    What does 'relative time' show?

    +

    Human-friendly age: '3 hours ago', '2 days from now'. Useful for eyeballing whether a token is expired or a scheduled event is near.

    Does the time zone panel handle DST correctly?

    +

    Yes. Each zone's render uses Intl.DateTimeFormat with formatToParts, which computes the correct offset at the target instant — not just the current offset.

    Where does the current time come from?

    +

    Your system clock. If it's wrong, the 'current time' block and 'relative' outputs will be wrong too.