toolgarden.xyz
中文

Timestamp Converter

Free online Unix timestamp and date converter with second, millisecond, microsecond precision and multiple time zones

Current time

seconds

1786934356

milliseconds

1786934356749

Timestamp ↔ Date

Result

Enter a timestamp or date

Batch conversion

About this tool

A timestamp represents one absolute instant as a number, usually in seconds or milliseconds. It carries no display time zone. The same value appears as different wall-clock times in Shanghai and London while still pointing to the same instant.

This tool converts between Unix timestamps and readable date-time values while making the unit and local result visible. When handling API logs, database fields, or signature parameters, identify the expected unit first so milliseconds are not accidentally interpreted as seconds.

How to use it

  1. Choose a direction

    Select timestamp to date or date to timestamp according to the source value.

  2. Confirm unit and time zone

    Check whether the number uses seconds or milliseconds and how the date input should be interpreted.

  3. Verify the result

    Compare the ISO and local representations, including date, time, and unit, with the source system.

Input and output example

Digit count sets the precision. Read the same number at the wrong precision and you are tens of thousands of years out.

Timestamps
1767225600
1767225600000
1767225600000000
Parsed (UTC)
10 digits → seconds       2026-01-01 00:00:00
13 digits → milliseconds  2026-01-01 00:00:00
16 digits → microseconds  2026-01-01 00:00:00

Supported range and limits

Precision
Seconds, milliseconds and microseconds, detected automatically from the digit count
Directions
Timestamp to date and date to timestamp, with batch input
Time zones
Choose the output zone. One timestamp renders as different local times, but the value itself carries no zone
Unix epoch
Zero is 1970-01-01 00:00:00 UTC; earlier moments are negative
Year 2038
A signed 32-bit second timestamp overflows on 2038-01-19. Modern systems use 64-bit, but watch for it in legacy data
Classic mistake
Reading a millisecond timestamp as seconds lands you 50,000 years out; the reverse lands you near 1970

When you would use it

  • Investigating logs

    Turn stored timestamps into readable times and reconstruct the real order of service events.

  • Preparing an API parameter

    Convert a chosen date-time into the integer unit required by a server endpoint.

  • Checking event order across time zones

    Convert log timestamps into one zone before sorting, so a difference between server and local time does not reverse the apparent sequence.

What to know before you start

  • Ten digits commonly means seconds and thirteen commonly means milliseconds, but the source documentation is authoritative.
  • Unix time is measured from a UTC baseline; that is different from a local date string with no time-zone context.
  • An input without an offset may be interpreted in the browser time zone. Prefer ISO 8601 with `Z` or an explicit offset for cross-region work.

Related concepts

Unix epoch
1970-01-01 00:00:00 UTC, the starting instant used by Unix timestamps.
ISO 8601
A common exchange format that can state UTC with `Z` or include a numeric time-zone offset.

Frequently asked questions

Does it support seconds and milliseconds?
Yes. It handles Unix timestamps at second, millisecond and microsecond precision and converts to and from dates.
Can I convert across time zones?
Yes. Multiple time zones are supported, so the same timestamp can be shown in your local time or a chosen zone.
Can I convert timestamps in bulk?
Yes. Paste multiple lines of timestamps to convert them all to dates at once, which is handy for log data.
Why did I get 1970, or a date 50,000 years out?
Wrong precision. Reading a millisecond timestamp as seconds lands you 50,000 years ahead; reading seconds as milliseconds lands you near 1970. Judge by digit count: 10 is seconds, 13 is milliseconds, 16 is microseconds.
Does a timestamp carry a time zone?
No. A Unix timestamp is absolute time elapsed since 1970-01-01 00:00:00 UTC, and one value names the same instant everywhere on earth. Different displayed dates only reflect a different local zone applied at render time.

Related tools