Choose the direction
Convert a numeric Unix value into a date, or enter a wall-clock date and generate Unix seconds and milliseconds.
Convert Unix seconds or milliseconds into readable dates—or turn a local, UTC, or custom-offset date into an exact Unix timestamp.
Your timestamps and dates stay on this device. Xepoca uses the browser's Date and Intl APIs and does not upload conversion values to a server.
Converter
Input unit
Quick examples
Conversion result
Auto-detected seconds because the value is below the modern millisecond range.
Timestamp auto-detection is a convenience heuristic. Select the unit manually for unusual far-future values.
Unix seconds
1786219979
Unix milliseconds
1786219979000
ISO 8601
2026-08-08T20:12:59.000Z
UTC string
Sat, 08 Aug 2026 20:12:59 GMT
RFC 2822
Sat, 08 Aug 2026 20:12:59 +0000
Your local time
Saturday, August 8, 2026 at 08:12:59.000 PM Coordinated Universal Time
Relative
1 second ago
Weekday
Saturday
Day of year
220
ISO week
32
Timezone comparison
Timezone rules come from your browser's Intl database.
UTC
Aug 08, 2026, 08:12:59 PM UTC
UTC
Amman
Aug 08, 2026, 11:12:59 PM GMT+3
Asia/Amman
Dubai
Aug 09, 2026, 12:12:59 AM GMT+4
Asia/Dubai
London
Aug 08, 2026, 09:12:59 PM GMT+1
Europe/London
Berlin
Aug 08, 2026, 10:12:59 PM GMT+2
Europe/Berlin
New York
Aug 08, 2026, 04:12:59 PM EDT
America/New_York
Los Angeles
Aug 08, 2026, 01:12:59 PM PDT
America/Los_Angeles
India
Aug 09, 2026, 01:42:59 AM GMT+5:30
Asia/Kolkata
Singapore
Aug 09, 2026, 04:12:59 AM GMT+8
Asia/Singapore
Tokyo
Aug 09, 2026, 05:12:59 AM GMT+9
Asia/Tokyo
Sydney
Aug 09, 2026, 06:12:59 AM GMT+10
Australia/Sydney
UTC year
2026
Leap year
No
Days in UTC month
31
Browser UTC offset now
UTC+00:00
Convert a numeric Unix value into a date, or enter a wall-clock date and generate Unix seconds and milliseconds.
Use automatic seconds/milliseconds detection, or interpret reverse conversions as local time, UTC, or a fixed UTC offset.
Use ISO 8601 for APIs, Unix values for systems, RFC output for messages, or timezone comparisons for debugging.
Unix time measures elapsed time from 00:00:00 UTC on January 1, 1970. The number identifies an instant independently of the viewer's time zone. Negative values represent instants before the epoch.
Many server APIs use whole seconds, while JavaScript's Date object uses milliseconds. A modern seconds timestamp is usually about ten digits; the equivalent millisecond value is commonly thirteen digits.
Compact and common in authentication claims, backend APIs, logs, and databases. The time zone is implicit: Unix time always represents UTC.
Native to JavaScript Date.now() and useful when sub-second ordering or browser event timing matters.
Readable, sortable, explicit, and widely supported. The trailing Z in this tool's output means UTC.
Useful for human-readable message and mail contexts that expect an English weekday, month, time, and numeric offset.
The Unix epoch is 00:00:00 UTC on January 1, 1970. Unix timestamps count elapsed seconds or milliseconds from that instant, with negative values representing earlier dates.
The converter treats absolute values of 100 billion or more as milliseconds and smaller values as seconds. That works well for modern dates, but very distant dates can be ambiguous, so the manual selector remains available.
They represent the same instant using different calendar offsets. UTC is the global reference; local output applies the browser's current regional time-zone rules.
Yes. A decimal seconds timestamp can represent milliseconds or finer fractions. JavaScript Date stores millisecond precision, so smaller fractions are rounded by the platform.
Conversion happens in your browser and values are not uploaded by the tool. Timestamps can still reveal activity or record timing, so follow your organization's data-handling rules.