Timestamp Toolbox

A log line says 1788277662. A JWT says "exp": 1788281262. Read them without opening another tab — from the toolbar, or straight from the right-click menu.

No account. No cloud. No telemetry. Zero network requests.

Add to Chrome Read the privacy policy

The popup, actual size. Everything converts as you type; the button also copies.

What you get

Three ways in, depending on where the timestamp already is.

The converter

Both directions at once. Paste a timestamp in seconds, milliseconds, microseconds or nanoseconds — Auto decides by digit count — or paste a date like 2024-05-01T08:00:00Z and read it back.

Under the result: UTC, ISO 8601 with the right offset, and seconds beside milliseconds. Click any line to copy just that value.

Right-click on the page

Select a number or a date anywhere and convert it in place. A small card shows local time, UTC, seconds and milliseconds; click a line to copy it.

The selection does not have to be clean — grab a whole log line and the timestamp inside it is found for you.

An LED clock

A full-page seven-segment clock, drawn entirely in CSS. Six colours, 12 or 24 hour, a bar tracking the current minute, and a key to keep the screen awake so it can sit on a second monitor.

Press T and the digits become the live Unix timestamp instead.

The clock, and the swap

Unlit segments stay faintly visible the way they do on real hardware, and lit ones fade out a beat slower than they light up.

Correct across time zones, including the awkward parts

The part most converters quietly get wrong.

Real IANA rules, no bundled database. Offsets come from the browser's own time zone data, so a date in 1995 uses the rules that were in force in 1995.
Daylight saving is handled the way date libraries handle it. A time that never happened because the clock jumped forward — 02:30 on a spring-forward morning in New York — folds forward to 03:30 instead of producing nonsense, and an hour that happens twice in autumn resolves to its first occurrence.
Half-hour and quarter-hour zones work. India, Nepal, the Chatham Islands.
Impossible dates are refused, not rounded. Ask for 31 February and you are told it does not exist, rather than being handed a number that quietly means 3 March.
Any zone, any format. Pick an IANA zone or follow the system; choose a preset date format or write your own with a live preview.

Sixteen languages, with local conventions

Not just translated strings — date habits follow the language too. English defaults to MM/DD/YYYY on a 12-hour clock, German and Russian to DD.MM.YYYY, Chinese, Japanese and Korean to YYYY-MM-DD. Weekday names, month names and phrases like "3 minutes ago" come from the browser's own locale data.

English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Deutsch · Français · Español · Português (Brasil) · Русский · हिन्दी · Tiếng Việt · Türkçe · Polski · Українська · Bahasa Indonesia

Privacy is the product

A timestamp converter has no reason to talk to a server, so this one does not.

No network requests at all. Every conversion happens in your browser. There is no API, no CDN, no font fetch, no update ping.
No analytics, no account, no identifiers. Nothing is collected, so nothing can be sold or leaked.
No access to your browsing. The extension holds no host permission and cannot read any site. When you use the right-click item, it draws the result card on that one tab, at that one moment, and that is the extent of it.
Your settings stay yours. Time zone, format and language live in Chrome's own sync storage, which follows your Google profile — never a server of ours.

The full policy is on the privacy page.

Why it exists

Converting a timestamp is a five-second job that somehow costs a minute: new tab, find the site, paste, read, copy, close, remember what you were doing. Most of the sites that do it are wrapped in ads, and a few of them get daylight saving wrong in ways you only notice much later, in production. This is the boring version that lives in the toolbar, keeps the awkward cases right, and asks for nothing.