Convert integer Unix timestamps to UTC, local, and ISO dates, or turn a browser-local date and time into epoch seconds and milliseconds. Essential for developers debugging APIs, parsing JWT claims, analyzing logs, and correlating events across systems that use different time representations.
Date and time tools
Interpret 13-or-more-digit input as milliseconds and shorter integer input as seconds, then verify the instant in UTC because datetime-local fields contain no time-zone offset.
Complete a verifiable Unix Epoch Seconds and Milliseconds Converter workflow in this browser.
Step 1
A numeric timestamp is parsed as an integer; an input string with 13 or more characters is treated as milliseconds and a shorter one as seconds. The reverse field accepts a browser-local date and time.
Step 2
Use the timestamp or date-to-epoch tab and Set Current Time. There is no explicit unit selector, named time zone, offset field, fractional timestamp, or leap-second mode.
Step 3
The workspace creates an ECMAScript Date, multiplies second values by 1,000, and refreshes its live current-time display once per second.
Step 4
Input 0 and require ISO 1970-01-01T00:00:00.000Z; also compare the UTC line rather than a locale-formatted line.
Step 5
Pass an absolute timestamp to Timezone Converter for a named-zone comparison, or use Date Difference for calendar-date spans.
Consequence: The converter treats strings of 13 or more characters as milliseconds and shorter strings as seconds. Small millisecond offsets near 1970 or very large second values can therefore be scaled by 1,000 in the wrong direction.
Fix: Confirm and record the unit before conversion; normalize production data to an explicit seconds or milliseconds field instead of relying on magnitude.
Consequence: Local wording and zone depend on the device and browser locale, so another system can parse it differently or lose the original instant.
Fix: Store the epoch value with its unit or the ISO output ending in Z; use the local line only for human display.
Consequence: datetime-local carries no zone or offset, so the browser interprets it in that device’s current local time zone and daylight-saving rules.
Fix: For portable instants, start with an ISO value containing Z or an explicit offset and use a time-zone-aware workflow.
Pass an absolute timestamp to Timezone Converter for a named-zone comparison, or use Date Difference for calendar-date spans.
Zero seconds from the Unix epoch identifies midnight UTC on 1 January 1970; the local line may show a different civil date or time.
A numeric timestamp is parsed as an integer; an input string with 13 or more characters is treated as milliseconds and a shorter one as seconds. The reverse field accepts a browser-local date and time.
datetime-local carries no zone or offset, so the browser interprets it in that device’s current local time zone and daylight-saving rules.
No. It uses the browser Date model and the device zone; named-zone conversion, historical zone selection, leap seconds, and calendar arithmetic are outside this workspace.
Input 0 and require ISO 1970-01-01T00:00:00.000Z; also compare the UTC line rather than a locale-formatted line.
Timestamps and dates are parsed only by this browser and are not uploaded. The live clock uses the device clock and offline use works after static assets are cached.
Pass an absolute timestamp to Timezone Converter for a named-zone comparison, or use Date Difference for calendar-date spans.
Timestamps and dates are parsed only by this browser and are not uploaded. The live clock uses the device clock and offline use works after static assets are cached.
