Time Tools

Convert Unix timestamps (seconds, milliseconds, microseconds) to readable dates — GMT, your timezone, ISO 8601, and more. All locally in your browser.

Right now

Unix seconds

1779047606

Unix milliseconds

1779047606934

Convert timestamp

Numeric unit

Uses your browser timezone (Europe/Berlin) to build the Unix value.

GMT / UTC
Sunday, May 17, 2026 at 7:53:26 PM UTC
Your timezone (Europe/Berlin)
Sunday, May 17, 2026 at 9:53:26 PM GMT+2

All formats

  • Unix timestamp (seconds)

    1779047606

  • Unix timestamp (milliseconds)

    1779047606934

  • GMT / UTC

    Greenwich Mean Time — same instant as UTC

    Sunday, May 17, 2026 at 7:53:26 PM UTC

  • Your timezone (Europe/Berlin)

    Wall clock in your browser timezone

    Sunday, May 17, 2026 at 9:53:26 PM GMT+2

  • Relative to now

    0 seconds ago

  • ISO 8601 (UTC)

    2026-05-17T19:53:26.934Z

  • ISO 8601 with local offset

    2026-05-17T21:53:26+02:00

  • RFC 2822

    Sun, 17 May 2026 19:53:26 GMT

  • Unix timestamp (microseconds)

    1779047606934000

  • Day of week (UTC)

    Sunday

  • ISO week

    ISO 8601 week date

    2026-W20

  • Day of year (UTC)

    137

  • Unix seconds (hex)

    0x6A0A1CB6

  • SQL datetime (UTC)

    2026-05-17 19:53:26

  • JavaScript Date

    new Date(1779047606934)

  • Milliseconds since Unix epoch

    1779047606934 ms

Timestamp & timezone reference

Unix epoch

Unix time counts seconds since 1 January 1970 00:00:00 UTC (the epoch). APIs often use milliseconds (13 digits) or microseconds (16 digits). This tool auto-detects unit from digit length.

UTC vs local

UTC (Coordinated Universal Time) is the global baseline. Your local timezone applies an offset (e.g. UTC+05:30 for India). ISO 8601 strings may end with Z (UTC) or +05:30 (offset).

Cities & IANA timezones

Search picks a city from a catalog of 14,000+ places; each row includes an IANA zone (e.g. Asia/Kolkata) resolved from coordinates. Zones handle historical and future DST rules — prefer city search over fixed offsets when scheduling.

Leap seconds & Y2038

JavaScript dates use millisecond precision and ignore leap seconds. 32-bit signed Unix seconds overflow on 19 January 2038; use 64-bit or milliseconds in new systems.

Common formats

  • ISO 86012024-06-01T14:30:00.000Z
  • RFC 2822 — email/HTTP date headers
  • SQLYYYY-MM-DD HH:MM:SS (often UTC in servers)

Privacy

Conversions run entirely in your browser. Nothing is sent to our servers.