Developer

Timestamp Converter

Turn Unix seconds, Unix milliseconds, or ISO 8601 strings into aligned formats: UTC ISO, local time, epoch values, and your browser’s IANA time zone. Parsing runs locally — nothing is uploaded.

Ad placement — top banner

No file loaded

Drop a text file here First line is parsed — useful for logs or CSV exports
Numeric timestamps

Auto treats integers with 13 or more digits (absolute value) as milliseconds; shorter integers default to seconds. Switch to Milliseconds if you paste a 10-digit millisecond value (rare).

Results
Ad placement — mid rectangle

What is Unix time?

Unix time counts seconds (or milliseconds) since the UTC epoch 1970-01-01T00:00:00.000Z. APIs, databases, and JWT exp claims often use integer seconds or milliseconds. JavaScript Date stores time as milliseconds since the same epoch, which is why this tool can convert between numeric and human-readable forms without a server.

UTC vs your local time zone

UTC is the universal baseline. Your browser’s local display depends on the system time zone and daylight saving rules. This tool shows both ISO strings in UTC and a formatted string in your local zone, plus the IANA name (for example America/New_York) reported by Intl APIs.

What this tool does

DroidXP’s Timestamp Converter parses the first non-empty line of your input. You can paste Unix integers (with optional negative values for times before 1970), ISO 8601 strings, or many date strings accepted by Date.parse. It fills UTC ISO, local toString(), Unix seconds (truncated), Unix milliseconds, a locale long label, and your UTC offset for that instant.

  • Auto mode guesses seconds vs milliseconds for plain integers; override with Seconds or Milliseconds when you know the unit.
  • Per-field copy buttons plus Copy all for tickets and docs.
  • Optional file drop for one-line log lines.

How to use this tool

  1. Step 1: Paste a timestamp or ISO string (or drop a small text file).
  2. Step 2: If the value is numeric, pick Auto or the correct unit.
  3. Step 3: Read UTC and local values; copy the fields you need.
  4. Step 4: Use Use current time to capture “now” as ISO for debugging.

Limits

JavaScript Date has a finite range (roughly ±270,000 years from the epoch). Very large integers may produce Invalid Date. For sub-millisecond precision or calendar math across historical calendar reforms, use specialized libraries or server-side tools.

Frequently Asked Questions

Does DroidXP upload my timestamps?

No. Conversion uses your browser’s Date object only. For sensitive logs, still follow your organization’s policies on using web tools.

Why is my Unix integer off by 1000×?

APIs mix seconds (10 digits today) and milliseconds (13 digits). Use Auto for typical values, or switch to Seconds or Milliseconds explicitly when you know which format your log produced.

Why does my local time differ from UTC?

UTC is fixed; local applies your system time zone and DST. The same instant is shown in both — only the representation changes.

Why do I see “Invalid Date” or a parse error?

The string may not be valid for Date.parse, or a numeric value may be out of range. Check for typos, missing Z or offset in ISO strings, or wrong units on integers.

Which ISO 8601 formats work?

Forms like 2024-01-15T12:00:00.000Z or with a numeric offset 2024-01-15T12:00:00+01:00 are common. Browser support varies slightly for edge cases; prefer ISO strings from your own systems for reliable round-trips.

Why only the first line of a file?

Log files often contain one timestamp per line. The tool focuses on the first non-empty line so you can drop a snippet without editing. For many lines, run the file through a script or split it first.

Does this match my server’s time zone?

No. Results use your device’s clock and time zone. Compare with UTC or server logs when debugging distributed systems.

Ad placement — sidebar 300×600