Timestamp Converter

Timestamp to date

Timestamp unit

Choose the unit explicitly. Seconds accept up to 3 decimal places; milliseconds must be integers. Negative values represent dates before 1970.

UTC date (ISO 8601)
1970-01-01T00:00:00.000Z

Date to timestamp

Interpret date in

Enter YYYY-MM-DDTHH:mm:ss.SSS (years 0000–9999). A space may replace T; seconds and milliseconds are optional. Do not append a time-zone suffix: use the selector below.

Unix seconds
0
Unix milliseconds
0
UTC date (ISO 8601)
1970-01-01T00:00:00.000Z

UTC has no daylight saving. Local time uses your browser’s time zone. Nonexistent times during a DST jump are rejected; repeated times use the earlier occurrence. Unix time does not count leap seconds.

Processed locally in your browser. Your input is not uploaded or saved by this tool.

About this tool

This converter translates Unix timestamps into readable UTC and local dates, and turns a calendar date and time back into a timestamp. Developers, analysts and system administrators use it when reading logs, debugging APIs or inspecting database fields. A Unix timestamp is the number of seconds, or milliseconds, that have elapsed since 1970-01-01 00:00:00 UTC, ignoring leap seconds.

How it works

Unix time measures elapsed time since 1970-01-01 at 00:00:00 UTC. Paste a timestamp, select seconds or milliseconds, and the tool shows the matching UTC date and your local date. Use the Now button to load the current timestamp, which is handy for comparing a log entry with the present moment.

In the other panel, enter a date and time and choose whether it is UTC or your local time zone, and you get the timestamp in both seconds and milliseconds. Switching the timestamp unit keeps the same instant and rescales the number. Each copy button copies only its own value, so you can paste a clean number straight into code or a query.

Example

1704067200 seconds, or 1704067200000 milliseconds, corresponds to 2024-01-01T00:00:00.000Z. A value of -0.001 seconds is one millisecond before the Unix epoch: 1969-12-31T23:59:59.999Z. Negative values are valid and simply count backward from 1970.

Going the other way, entering 2025-06-15 at 12:30 with UTC selected gives 1749990600 seconds and 1749990600000 milliseconds. If you choose local time instead, the result shifts by your UTC offset; in a zone two hours ahead of UTC, the same wall-clock time is 1749983400 seconds.

Assumptions and limits

Conversions follow JavaScript date handling, which ignores leap seconds and supports millisecond precision, so microsecond or nanosecond timestamps must be scaled first. Local times use your device's time zone settings; other named time zones are not offered. The tool does not parse arbitrary date text formats or calculate differences between dates.

Frequently asked questions

How do I know whether a timestamp is in seconds or milliseconds?

Contemporary Unix timestamps commonly have 10 digits in seconds or 13 in milliseconds, but digit count is not a reliable rule for older or future dates. Check the source API or database and select its unit explicitly. Fractional seconds preserve millisecond precision here.

Does a Unix timestamp have a time zone?

No. It identifies an instant relative to the UTC epoch. Time zones only change how that instant is displayed, or how a calendar date is interpreted. Conversion runs in your browser; your input is not uploaded or saved.

What is the year 2038 problem?

Systems that store Unix time as a signed 32-bit integer of seconds overflow after 2038-01-19 03:14:07 UTC, which is timestamp 2147483647. After that moment the counter wraps to a negative number and the date jumps back to 1901. Systems that use 64-bit integers, or JavaScript millisecond values as this tool does, are not affected by that limit.

Do Unix timestamps include leap seconds?

No. Unix time treats every day as exactly 86,400 seconds, so leap seconds are not counted. For most applications this difference does not matter, but precise scientific timekeeping uses other time scales.

How do I get the current Unix timestamp in code?

In JavaScript, Date.now() returns milliseconds, and Math.floor(Date.now() / 1000) gives seconds. In Python, int(time.time()) returns seconds, and on Linux or macOS the shell command date +%s prints the same value. The Now button in this tool shows the current timestamp if you just need to read it.

Link with your values

Add these parameters to this page’s address to open it with the values filled in, for example to share a calculation or to link to it from an AI assistant. The result is calculated in the browser: the page HTML shows an example for the default values, and the tool sets the data-url-params attribute once the link’s values are applied.

ParameterValueIf omitted
timestamp_secondsUnix secondstext in the tool's notation, see the examplesrequired
timestamp_millisecondsUnix millisecondstext in the tool's notation, see the examplesrequired
datetimeDate and timetext in the tool's notation, see the examplesrequired
zoneInterpret date inone of: utc, localdefault utc

Examples

  • ?timestamp_seconds=1760000000
  • ?timestamp_milliseconds=1760000000123
  • ?timestamp_seconds=1791936000&datetime=2026-10-08T14:30Z

Write decimals with a point. Encode a space as %20, + as %2B, # as %23 and & as %26.

Result elements: [data-result-block="timestamp-date"][data-result-block="timestamp-value"]