Updated October 28, 2026 · ToolKnit
Use the Timestamp Converter to paste a value, select its unit and compare UTC, ISO 8601 and local time. The tool page is for conversion; this guide explains how to diagnose a wrong result. Conversion stays in your browser.
Seconds and milliseconds: the same instant, different numbers
Unix time counts seconds since 1970-01-01 00:00:00 UTC, excluding leap seconds. JavaScript Date.now() returns milliseconds since the same epoch. Multiply seconds by 1,000 to get milliseconds. A modern 10-digit value often means seconds and a 13-digit value often means milliseconds, but digit count is only a clue: old dates, future dates and leading zeros break that shortcut.
For example, 1715356800 seconds and 1715356800000 milliseconds both mean 2024-05-10T16:00:00.000Z. The trailing Z means UTC. An offset in a local display changes the representation, not the instant.
Worked examples you can reproduce
| Input | Unit | ISO 8601 (UTC) |
|---|---|---|
| 0 | Seconds | 1970-01-01T00:00:00.000Z |
| -1 | Seconds | 1969-12-31T23:59:59.000Z |
| 1000000000 | Seconds | 2001-09-09T01:46:40.000Z |
| 1000000000 | Milliseconds | 1970-01-12T13:46:40.000Z |
| 1.234 | Seconds | 1970-01-01T00:00:01.234Z |
| 2147483647 | Seconds | 2038-01-19T03:14:07.000Z |
The two rows containing one billion show why an automatic guess cannot establish the source unit. ToolKnit Auto treats absolute values of at least one trillion as milliseconds and smaller values as seconds. Select the unit explicitly whenever you know the API or database format.
Try the values, then verify them in JavaScript or Python
These links fill a fixed public example and its explicit unit. They do not put your log text or a private timestamp into a URL.
JavaScript
new Date(1715356800 * 1000).toISOString();
// "2024-05-10T16:00:00.000Z"
new Date(1715356800000).toISOString();
// Same instant; Date takes milliseconds.JavaScript Date takes milliseconds. Date.now() also returns milliseconds; use Math.floor(Date.now() / 1000) when the receiving API requires whole Unix seconds.
Python
from datetime import datetime, timezone
datetime.fromtimestamp(1715356800, timezone.utc).isoformat()
# '2024-05-10T16:00:00+00:00'Python fromtimestamp takes seconds. Passing timezone.utc avoids dependence on the computer’s local zone. The +00:00 offset and JavaScript’s Z both denote UTC.
2024-05-10T16:00:00Z and 2024-05-11T00:00:00+08:00 describe the same instant. The tool’s Local Time field uses your device zone, which may be different. UTC output is the stable value to compare across computers.
Convert a calendar date back without shifting it
- In Date → Timestamp, select UTC or Device local time before entering the date.
- Enter the date and time. An empty time means midnight in the selected zone.
- Copy either seconds or milliseconds to match the receiving system.
- Paste that result back into Timestamp → Date with the explicit unit and compare the ISO value.
For a UTC check, enter 1970-01-01 and 00:00:00: the result must be zero. The same wall-clock values in a non-UTC local zone refer to a different instant. The Now button fills the fields in the selected zone; its clock comes from your device, not a server time service.
Daylight-saving gaps and repeated local times
A local clock can jump over a time or repeat it. With a device set to America/New_York, 2024-03-10 02:30 did not occur and is rejected. On 2024-11-03, 01:30 occurred twice; JavaScript chooses the earlier occurrence, which is 05:30 UTC. Use a known UTC instant to distinguish repeated times. This tool does not offer an arbitrary IANA time-zone selector. For comparing current city times, use World Clock.
Why the converter rejects a value
- Trailing text, commas or scientific notation: paste a complete numeric value such as 1715356800, not a log label or 1.7e9.
- Too much precision: seconds support up to three decimal places; milliseconds must be whole numbers. Microsecond and nanosecond timestamps need conversion at the source without discarding precision unintentionally.
- Invalid calendar date: February 29 requires a leap year; missing local DST times are not silently normalized.
- Date range: JavaScript Date accepts at most ±8,640,000,000,000,000 milliseconds. The calendar input is limited to years 0001–9999. Neither range is an unlimited 64-bit integer clock.
For JSON logs, first use the JSON Formatter to identify the exact field, then convert only its number. Use Text Diff to compare two log snippets; it does not interpret their times.
Does the Year 2038 problem affect this tool?
Signed 32-bit Unix seconds reach their maximum at 2038-01-19 03:14:07 UTC. This browser converter is not limited to that 32-bit integer, but the system receiving your result may be. Successful conversion here does not prove an older database or embedded device can store it.
What does relative time mean?
Relative time compares the input with the device clock at conversion. Month and year labels are approximations, not calendar arithmetic. Unix time and JavaScript Date do not represent leap seconds as separate instants, and this input does not accept a seconds field of 60. For elapsed timing rather than calendar conversion, use the Stopwatch.
Ready to check a value? Open the Timestamp Converter and start with an explicit unit and UTC comparison.