Time Converter — Tips & Tricks

Back to overview: Time Converter · Open the live tool: www.jpkc.com/tools/time/

The Time Converter is quick to operate — but time, time zones, and timestamps hide a few classic traps. This page collects what matters in practice. The technical groundwork is in the manual.

Seconds or milliseconds? The digit count decides

The old trap — 13-digit JavaScript milliseconds read as seconds and landing you thousands of years in the future — is one the tool clears out of the way itself: it detects the unit from the number of digits (up to 11 digits seconds, 12–14 milliseconds, 15–17 microseconds, 18 and more nanoseconds) and shows it in the badge next to Unix timestamp. Still, glance at the badge before you reuse a result:

If one digit goes missing while copying or one too many gets added, the unit usually stays the same: 10-digit seconds become 9 or 11 digits — still s — and 13-digit milliseconds become 12 or 14 digits — still ms. The result is then off by a factor of 10 without the badge changing. Only the implausible date gives the mistake away, such as a year around 1975 or around 2500 — so check the year in the ISO row. The badge switches class only when two or more digits differ.
Seconds values with 12 or more digits — that would be after roughly the year 5138 — are inevitably read as milliseconds.
What the tool outputs is always clearly labeled: Unix timestamp (s) and Unix timestamp (ms) are separate rows in the table, and when the tool fills the field itself, it writes seconds.

The Etc/GMT signs are the wrong way round

A genuine classic: the Etc/GMT zones follow the POSIX convention and therefore carry the opposite sign to the familiar UTC notation. Etc/GMT+1 is actually UTC−1 (one hour behind Greenwich), and Etc/GMT-5 is UTC+5. So choosing "GMT+1" for Central Europe gets you exactly the opposite. The Time Converter helps by labeling every entry with its real offset — Etc/GMT+1 (UTC-01:00). Trust the brackets, not the name. For Central Europe you're better off with Europe/Berlin anyway (see the next tip).

Pick city zones, not fixed offsets

The Time zone list contains every IANA time zone your browser knows — use it. A city zone such as Europe/Berlin or America/New_York knows the place's daylight saving rules and their history; a fixed offset (Etc/GMT-1) or a rigid UTC+01:00 doesn't, and is an hour off in summer. The Fixed offset (Etc) group only makes sense when a system genuinely runs on a fixed offset with no clock changes. If your city isn't in the list, take the zone of a city with the same rules — IANA names zones after a representative city, not after every city.

The time zone applies to your input too

The selected time zone doesn't just control the display; it also determines how your input is read: 12:00 in the date field or 2026-07-01 12:00 in Any date text means noon in the zone in the card footer — not in your computer's zone. That's exactly what you want when you work out a deployment window in a foreign zone, for example. But before you copy a timestamp, take a quick look at the field label (Date & time (Zone)). Text with an offset (Z, +02:00) and HTTP dates, on the other hand, apply regardless of the selected zone. And free text in other formats without a zone — such as July 1, 2026 12:00 — is read by your browser's date parser in your device's zone; for the selected zone, write it as ISO 8601 (2026-07-01 12:00).

Daylight saving time: gaps and repeated times

Twice a year there are clock times that aren't unambiguous. In Central Europe:

On the last Sunday in March the clock jumps from 02:00 to 03:00 — 02:30 doesn't exist. The tool reports this as an error ("the clocks skip it") instead of quietly adding an hour.
On the last Sunday in October the hour from 02:00 to 03:00 runs twice. In the Convert tab the tool takes the first occurrence (still summer time, +02:00) and tells you in the yellow note. If you need the second one, enter the moment as ISO text with an offset: 2026-10-25T02:30:00+01:00.

The Difference tab has no separate notice for a repeated time — there, too, the first occurrence counts.

Difference: reading Calendar, Elapsed, and the totals

The Difference tab gives you two different answers — and both are right:

Calendar is the gap on the wall clock ("1 day" from Saturday noon to Sunday noon) — the right view for deadlines, subscriptions, and calendar appointments.
Elapsed is the time that actually passed ("23 hours" if the clocks went forward in between) — the right view for run times, timeouts, token lifetimes, or max-age.

When the blue daylight saving notice appears, the two differ. The rows Weeks, Days, Hours, Minutes, and Seconds, on the other hand, are not a breakdown but each the entire elapsed span in one unit: "Days 320.4" and "Hours 7,689.5" describe the same period. The values are always positive — whether End lies before or after Start is shown in the Direction row.

Month ends: when is "one month" up?

Calendar counts months the way a calendar does and clamps to the last day of the month: from 31 January to 28 February (in a common year) is 1 month, even though only 28 days have passed. The Months (calendar) row gives the number of full calendar months. If you count deadlines in days, go by Days; if you count in months, go by Calendar.

Time zone and language apply to all tabs

Language and Time zone sit in the card footer and apply to Current, Convert, and Difference at once. The tool remembers both in your browser, so they're set again on your next visit; Mine switches back to your device's zone. When you change the zone, the tabs deliberately behave differently:

Convert keeps the moment: the timestamp stays the same, while date and time jump to the new zone. Ideal for "translating" an appointment.
Difference keeps the clock times you entered and reads them in the new zone — so the elapsed time can change, for instance when a clock change lies between Start and End in the new zone but not in the old one.

The language changes only the formatting (Full to Short, zone name, durations, numbers), never the moment.

Pause the live clock to copy

In the Current tab the clock ticks on every second. Most of the time you don't even need to stop it, because the clipboard button at the end of each row copies the value shown at that very moment. If you want several values from the same instant — timestamp and ISO form for a ticket, say — click Pause first and Resume afterwards.

Server time as an independent reference

If you doubt your local machine clock, click Server in the Convert tab. The tool takes over the server time and at the same time tells you by how many seconds your device clock runs ahead or behind. That's a quick cross-check when time-based one-time passwords, token expiry times, or TLS certificates claim to be "not yet valid". For your own scripts, the endpoints /tools/time/time/ (seconds) and /tools/time/mtime/ (microtime in the format 0.49530000 1792064051) are available directly as plain text:

curl -s https://www.jpkc.com/tools/time/time/

Paste logs and headers directly

There's no need to retype dates: copy an ISO string from an API response, a Date or Last-Modified header, or a bare timestamp straight into Any date text. Below the field the tool shows how it read the text ("Read as …") — so you notice right away how a string without an offset was interpreted: "Read as ISO 8601 in Europe/Berlin" means the selected zone, while "Read as RFC 2822 / HTTP date" for text without a zone means your device's zone.

Combine with other JPKCom tools

Cron generator — when you don't just want to convert a single moment but formulate a recurring schedule; convert the next run back into a readable date or into another time zone here.
UUID generator — time-based UUIDs (v1, v6, v7) carry a timestamp inside them; use the Time Converter to place it.
Hash generator — for time-stamped records whose integrity you want to secure with a checksum.

The full function reference is in the manual, concrete walkthroughs in the examples. You can try everything in the tool.