Pikkola Time Studio, tool No. 41

One instant, every way to write it.

A clock that counts the seconds as they pass, and a converter that reads a number or a date in either direction. It writes the same moment as ISO 8601, as RFC 2822, as UTC, in your own zone and as a phrase like 3 hours ago, and it does the same for a whole list at once.

4
tabs
0
requests sent
EN · KO · JA
three languages

The four tabs

Read the clock, or read a number

Every tab shares the same arithmetic and the same chosen instant. Nothing here needs a sign in, and nothing leaves the tab.

The clock

The epoch counts up whether or not anyone watches. Pause it to read a value, and copy any precision from the list below.

running

seconds

1795157487 .412907631
The same instant, four precisions
Seconds 1795157487
Milliseconds 1795157487412
Microseconds 1795157487412907
Nanoseconds 1795157487412907631

The last six digits come from the browser's high resolution clock, which is precise but not guaranteed to match a time server to the microsecond.

Written five waysAsia/Seoul
ISO 8601 2026-11-20T06:51:27Z
ISO, in zone 2026-11-20T15:51:27+09:00
RFC 2822 Fri, 20 Nov 2026 15:51:27 +0900
Local 2026-11-20 15:51:27
Relative now doy 324

Local follows this device's own time zone. Set another zone on the Convert tab and this line follows it there.

Reading a timestamp

Three habits that save a wrong hour

A timestamp is a count, a date is a reading, and the two are mistaken for each other more often than they are computed wrong.

01

Count the digits before you trust them

Ten digits are seconds and thirteen are milliseconds, and the same number read in the wrong unit is thirty thousand years off. Sixteen digits are microseconds and nineteen nanoseconds. The page names the unit it picked, so the guess is never silent, and the selector overrides it in one click.

02

An instant is not a wall clock

The number is the same in Seoul, in London and on a server in Oregon. The hour is not: a zone adds a rule, and the rule changes with daylight saving and with the year. Convert to UTC first, then apply the zone, and a value near midnight stops looking like an off by one error.

03

Local time with no offset is a guess

A date written as 2026-11-20 15:51 names a wall clock and nothing else. The same text is two different instants in two zones, which is why an API expects Z or an offset. When the text carries neither, this page reads it in this device's zone and says so.

The same instant, one row per format
Format Written Where it turns up
Unix 1795157487 Logs, databases, token claims, cache keys
ISO 8601 2026-11-20T06:51:27Z APIs, JSON payloads, filenames, git
RFC 2822 Fri, 20 Nov 2026 15:51:27 +0900 Mail headers, feeds, older HTTP headers
RFC 3339 2026-11-20T15:51:27+09:00 The profile of ISO 8601 most APIs mean
SQL 2026-11-20 06:51:27 PostgreSQL, MySQL, SQLite timestamps
Local 2026-11-20 15:51:27 What the person in front of the screen sees

Questions

What exactly is a Unix timestamp?

The number of seconds since 1970-01-01T00:00:00 UTC, not counting leap seconds. The start is the UNIX epoch, and the count ignores the leap seconds added since 1972, which is why it is called POSIX time and why it converts without a table of leap seconds.

Why does my timestamp have 13 digits instead of 10?

Ten digits are seconds and thirteen are milliseconds, which is what JavaScript's Date.now() returns by default. Sixteen digits are microseconds and nineteen are nanoseconds. This page counts the digits and picks the unit, and names the unit above the result so it can be overridden.

What is epoch 0 in my own time zone?

In Seoul, 1970-01-01 09:00:00, because the offset was nine hours ahead of UTC. The instant is the same everywhere; only the wall clock differs. Set the zone selector on the Convert tab to see any zone.

Why is the date one day off from what I expected?

Usually a zone, not arithmetic. A timestamp is an instant with no zone, so it is displayed in one, and a value near midnight lands on a different calendar day in a different zone. Compare the UTC line with the local line to see where the shift happens.

Are leap seconds counted?

No. Unix time follows POSIX, which holds every day at 86,400 seconds. A leap second is absorbed by the system clock instead of appearing in the number, so a conversion never needs a leap second table and never disagrees with the value a server logs.

Does anything get uploaded?

No. Every figure is computed in this tab, the content policy forbids network requests, and there is no server that could receive a timestamp. Only the language, the theme and the last values you typed are kept in this browser.