Alternative Timestamps Converter

Convert Unix timestamps (seconds, ms, µs, ns) to readable dates, with LDAP, WebKit, NTP and Cocoa epoch offsets explained

A timestamp converter that auto-detects Unix epoch values in seconds, milliseconds, microseconds and nanoseconds and shows them as UTC, local and ISO dates. It also documents the epoch offsets used by Windows LDAP/Active Directory, Chrome/WebKit, NTP and Apple Cocoa so you can convert those values by hand.

How to use Alternative Timestamps Converter

  1. Enter Timestamp. Paste any numerical timestamp value.
  2. Check the Precision. The tool detects whether the value is in seconds, milliseconds, microseconds or nanoseconds.
  3. View Results. Instantly view the date in UTC, local and ISO formats.

Features

  • Offline Processing: Computes operations instantly in your local browser client.
  • One-Click Copy: Instantly copy inputs or outputs to your clipboard.
  • Precision Outputs: Processes inputs immediately to provide clean, error-free results.

Why use this tool

  • Clear Output: View a timestamp as UTC, local time and ISO 8601 at once.
  • Auto-Parsing: Detects and processes microsecond and nanosecond precisions automatically.
  • Developer friendly: Easily copy code snippets and values in one click.

Frequently asked questions

How does this tool detect the timestamp format?

It looks at what you paste. Digit-only input of up to 10 digits is treated as Unix seconds, up to 13 as milliseconds, up to 16 as microseconds and longer as nanoseconds. Anything else is parsed as a date string, such as an ISO 8601 value, and the detected format is displayed.

How do I convert a 13-digit timestamp?

Paste it as is. A 13-digit number is treated as Unix milliseconds, so 1700000000000 gives 2023-11-14T22:13:20Z. The result is displayed in Unix seconds, milliseconds, ISO 8601, UTC and a timezone of your choice, including UTC, local, EST, PST and IST.

What is the difference between Unix, LDAP, Chrome, NTP and Cocoa timestamps?

They count from different starting dates. Unix counts seconds from 1970-01-01, NTP from 1900-01-01, Cocoa from 2001-01-01, and GPS from 1980-01-06. LDAP/Windows FILETIME counts 100-nanosecond ticks and Chrome counts microseconds, both from 1601-01-01.

How do I convert an LDAP or Chrome timestamp to Unix time?

Convert the unit and subtract the epoch offset. For Chrome, divide microseconds by 1,000,000 then subtract 11,644,473,600 seconds, the gap between 1601 and 1970. For LDAP, divide by 10,000,000 first. This tool then reads the resulting Unix value directly.

What is the offset for NTP and Cocoa timestamps?

Subtract 2,208,988,800 seconds from an NTP timestamp to get Unix seconds, since 1900 is that far before 1970. A Cocoa (Apple) timestamp counts from 2001-01-01, so add 978,307,200 seconds to convert it to Unix time.

What does a Unix microsecond or nanosecond timestamp look like?

Microsecond timestamps have 16 digits, such as 1700000000000000, and nanosecond ones have 19. The tool divides down to milliseconds because JavaScript dates only store millisecond precision, so any digits finer than a millisecond are dropped in the displayed date.

Is my data shared when using the Alternative Timestamps Converter?

No. Toolskyt operates under a zero-server policy. All calculations, data formatting, and file exports are executed locally on your machine.

Do I need to sign up or pay to use the Alternative Timestamps Converter?

No, this tool is 100% free. There are no limits, sign-ups, subscriptions, or hidden charges required.

Is it safe to paste API tokens or private JSON data here?

Yes, absolutely. The tool executes 100% inside your local browser memory space. No inputs are sent to any servers.

Related tools