JPKCom DB

Time Converter — Examples

Time Converter walkthroughs: read timestamps in s and ms, turn a date into a timestamp, check your clock offset, and measure time spans across a DST change.

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

This page shows the Time Converter through concrete walkthroughs. The values used are examples. The localized rows (Full, Long …) are worded by your browser and may differ slightly between versions, and how the date fields display a value depends on your browser's locale. How the individual functions work in detail is covered in the manual.

Example 1: Decode a Unix timestamp

Goal: you find the bare value 1700000000 in a log and want to know which moment that is.

  1. In the card footer, set Time zone to Europe/Berlin and Language to British English (en-GB).
  2. Switch to the Convert tab.
  3. Enter 1700000000 in the Unix timestamp field. The badge next to the label shows s — detected as seconds.

Result: the date field jumps to 14 November 2023, 23:13:20, and the table shows the moment in every format, including:

Unix timestamp (s)          1700000000
Unix timestamp (ms)         1700000000000
ISO 8601 (Europe/Berlin)    2023-11-14T23:13:20+01:00
ISO 8601 (UTC)              2023-11-14T22:13:20Z
RFC 2822 (e-mail)           Tue, 14 Nov 2023 23:13:20 +0100
HTTP date (RFC 9110, UTC)   Tue, 14 Nov 2023 22:13:20 GMT
Full                        Tuesday, 14 November 2023 at 23:13:20 CET
ISO week · day of year      2023-W46-2 · day 318

The ISO 8601 (UTC) row shows at a glance that the same instant reads one hour earlier on a UTC clock — the timestamp itself doesn't depend on any time zone. You copy any row with the clipboard button at its end.

Example 2: Look at the start of the Unix epoch

Goal: understand what the value 0 stands for.

  1. Set Time zone to UTC (in the General group).
  2. In the Convert tab, enter 0 in the Unix timestamp field.

Result: you land at the beginning of Unix time: ISO 8601 (UTC) shows 1970-01-01T00:00:00Z, ISO week · day of year 1970-W01-4 · day 1 (a Thursday). There's no extra UTC row, because the selected zone already is UTC. Switch the zone to Europe/Berlin afterwards and the timestamp stays at 0 while the date reads 1970-01-01T01:00:00+01:00 — a neat illustration that Unix seconds always count from the same zero point. Negative values such as -86400 take you back before 1970, by the way.

Example 3: Turn a date into a Unix timestamp

Goal: an API call needs the timestamp for 1 June 2024, 12:00 noon German time.

  1. Set Time zone to Europe/Berlin.
  2. In the Convert tab, enter 1 June 2024, 12:00:00 in the Date & time (Europe/Berlin) field (how the field shows the date depends on your browser).

Result: the Unix timestamp field immediately shows 1717236000, and the table below shows 2024-06-01T12:00:00+02:00 (summer time) and 2024-06-01T10:00:00Z. If you need milliseconds, copy the Unix timestamp (ms) row (1717236000000). The ISO and localized rows let you double-check that you picked the right moment.

Example 4: Fetch the server time as a reference

Goal: check whether your computer's clock is right and get a timestamp from an independent clock.

  1. Switch to the Convert tab.
  2. Click the Server button next to the Unix timestamp field.

Result: the date and timestamp fields and the table jump to the time of the server clock (queried via /tools/time/mtime/); the Any date text field is cleared. Below the timestamp field you see how your device clock compares — for example "This device's clock matches the server (±25 ms)." or "This device's clock is 3.4 s behind the server." An offset of several seconds is a hint to check your system's time synchronization.

Example 5: How long until a deadline?

Goal: see the span between now and the turn of the year 2026/2027 — updating live.

  1. Set Time zone to Europe/Berlin and switch to the Difference tab.
  2. Under Start, enter the deadline: 1 January 2027, 00:00:00.
  3. Leave the now (live) checkbox next to End ticked.

Result: depending on today's date, the sentence above the table reads something like "in 3 months — 2 months, 15 days, 12 hours, 30 minutes", Direction shows "End is before start" (the deadline lies after now, after all), and every value counts down second by second as long as the tab is open. If the clock change at the end of October still lies between now and the deadline, Calendar and Elapsed differ by one hour — the tool points this out with the blue daylight saving notice ("moved back by 60 minutes"). For a question like "How long ago was that?", simply enter a date in the past under Start.

Example 6: Measure the duration between two points

Goal: find out how much time lies between a project start and a release.

  1. In the Difference tab, enter 15 January 2024, 09:00:00 under Start.
  2. Untick now (live) next to End and enter 30 November 2024, 18:30:00.

Result (time zone Europe/Berlin, language en-GB):

Calendar             10 months, 15 days, 9 hours, 30 minutes
Elapsed              320 days, 9 hours, 30 minutes
Direction            End is after start
Months (calendar)    10
Weeks                45.77
Days                 320.4
Hours                7,689.5
Minutes              461,370
Seconds              27,682,200

Calendar breaks the span down into months, days, and hours the way you'd count them on a calendar; the rows Weeks to Seconds each give the entire span in one unit. There's no daylight saving notice here: both moments fall in winter time, so the March and October changes cancel each other out.

Example 7: Milliseconds and microseconds from logs

Goal: place timestamps from JavaScript (Date.now()) or a tracing log without converting them first.

  1. In the Convert tab, paste the millisecond value 1700000000000 into the Unix timestamp field. The badge switches to ms, and the table shows the same moment as in Example 1.
  2. Now paste the 16-digit value 1700000000123456.

Result: the badge shows µs, and the ISO rows carry the milliseconds: 2023-11-14T23:13:20.123+01:00 and 2023-11-14T22:13:20.123Z, while Unix timestamp (ms) reads 1700000000123. A 19-digit nanosecond value (from Go or Prometheus, for instance) is detected the same way (ns). No more dividing by 1000.

Example 8: A time span across a clock change

Goal: understand why "one day" isn't always 24 hours.

  1. Set Time zone to Europe/Berlin, open the Difference tab, and untick now (live).
  2. Enter 28 March 2026, 12:00:00 as Start and 29 March 2026, 12:00:00 as End.

Result: Calendar shows 1 day, but Elapsed only 23 hours; Hours reads 23, Days 0.96. Above the table you see the notice: "A daylight saving time change lies in between: the wall clock moved forward by 60 minutes, so calendar and elapsed time differ." For billing by calendar day you go by Calendar; for run times, timeouts, or token lifetimes by Elapsed.

Try entering 29 March 2026, 02:30:00 in the Convert tab instead, and the tool reports: "This time does not exist in Europe/Berlin — the clocks skip it (daylight saving time starts)."

Example 9: Paste an HTTP header or an ISO string

Goal: translate a date from a response header into your local time.

  1. Set Time zone to Europe/Berlin.
  2. In the Convert tab, paste the header value Wed, 01 Jul 2026 10:00:00 GMT into the Any date text field.

Result: below the field it says "Read as RFC 2822 / HTTP date", the date field shows 1 July 2026, 12:00:00, and the table shows 2026-07-01T12:00:00+02:00 with the timestamp 1782900000. An ISO string with an offset such as 2026-07-01T12:00:00+02:00 works the same way ("Read as ISO 8601 with offset"). An ISO string without an offset — 2026-07-01 12:00 — is read as a time in the selected zone instead ("Read as ISO 8601 in Europe/Berlin").

Example 10: Carry a time over into another time zone

Goal: a call is scheduled for 12:00 noon New York time — what time is that in Berlin?

  1. Set Time zone to America/New_York (listed as America/New York).
  2. In the Convert tab, enter 1 July 2026, 12:00:00 in the Date & time (America/New_York) field. The timestamp reads 1782921600, ISO 8601 (America/New_York) 2026-07-01T12:00:00-04:00.
  3. Switch Time zone to Europe/Berlin.

Result: when you change the zone, the Convert tab keeps the moment: the timestamp stays at 1782921600, the date field jumps to 18:00:00, and the ISO row to 2026-07-01T18:00:00+02:00. Click Mine afterwards to return to your device's time zone.

There's more on the individual functions in the manual, strategic notes and pitfalls in the tips & tricks. To get started right away, head to the tool.