Timestamp settings
Unix Time Clock (Epoch Timestamp)
Show the device-derived current Unix timestamp in seconds and milliseconds with matching UTC and local time, copy, freeze, and fullscreen controls.
How the live epoch values are produced
Unix time counts elapsed seconds from 1970-01-01 00:00:00 UTC. This route reads the device clock through a browser Date object. The millisecond value is Date.getTime. The seconds value truncates that millisecond value after dividing by 1,000. The page refreshes its device-clock reading every 50 milliseconds while Live is on.
Example: a browser Date value of 1,700,000,000,000 milliseconds produces 1,700,000,000 seconds and the UTC instant 2023-11-14 22:13:20 UTC. The Local row formats the same instant in the device's time zone. A Unix value does not contain that local time zone.
Freeze keeps the current values on screen. Snap now reads the device clock again. The route accepts no pasted input and performs no unit detection; use the Unix Timestamp Converter for that job. This page does not contact an official time server. Device-clock error, rendering delay, background throttling, and sleep can affect what you see.
Sources: The Open Group explanation of seconds since the Epoch; ECMAScript Date objects.
Read the live Unix values
Seconds shows whole seconds since 1970-01-01 00:00:00 UTC. Milliseconds shows the same instant at one-thousandth-second scale. Freeze holds the displayed sample. Snap now replaces it with a fresh device-clock value.
A seconds value of 1,700,000,000 corresponds to a milliseconds value of 1,700,000,000,000. The page also renders UTC and local date forms for the sampled instant. Copy seconds and Copy milliseconds keep the units explicit.
Live display limits
This clock reads the device clock and is not a network time source. Whole seconds are truncated from the millisecond value. Browser rendering can skip visible increments, especially in a background tab, without changing the meaning of the next sampled timestamp.
Need to convert a pasted epoch value into a readable date? Use the Unix timestamp converter for seconds, milliseconds, UTC, local time, and ISO output.
The Unix timestamp units guide explains the scale difference and why more digits do not prove a more accurate device clock.
Accuracy and limitations
Current Unix and epoch values are generated from the device's current system time. If the device clock is incorrect, the current values shown here will inherit that offset.
Seconds and milliseconds represent different units and should not be used interchangeably. The main display is labeled in seconds, while the supporting value is labeled in milliseconds.
Maintained by Suhas Sunder. See how iLoveTimers is made.
Last reviewed .