Unix Timestamp ⇄ Date & Time
ConvertEverything runs locally in your browser — nothing is uploaded
The bar at the top shows the current timestamp, live — click it to drop it into the box below. Under that, one panel per direction: a timestamp into a readable date, or a moment into a timestamp, either picked from the native calendar or pasted as text. Seconds, milliseconds, microseconds and nanoseconds are told apart by length (10 digits seconds, 13 milliseconds, 16 microseconds, 19 nanoseconds) and can be pinned manually, or read as Windows FILETIME / Cocoa epoch. Input accepts decimals, pre-1970 negatives and scientific notation, and 19-digit nanoseconds are computed with BigInt so not one digit is lost; ISO 8601 goes all the way to nanoseconds. The 20 zones people reach for most sit at the top of the list and the rest of the IANA set is searchable, and offsets are taken at the instant being converted, so daylight saving and countries that have changed their rules are both handled. Every result row copies on its own — no select-all-then-trim.
Features
- Live current timestamp (seconds and milliseconds side by side), pausable and clickable to fill the input
- One panel per direction: timestamp → date-time, and date-time → timestamp
- Pick a date-time with the native calendar, or paste text such as 2026-09-18 15:30:45
- Seconds / milliseconds / microseconds / nanoseconds detected by length, or set by hand (10 digits s, 13 ms, 16 µs, 19 ns)
- ⚠️ 19-digit nanoseconds lose nothing: BigInt throughout, so `1700000000123456789` round-trips digit for digit (Number would round it)
- Accepts decimals (`1700000000.123`), pre-1970 negatives and scientific notation (`1.7e9`); fractions round to the nearest nanosecond
- A whole-number output toggle: on writes integers only, off keeps the fractional tail
- Windows FILETIME in both directions (100 ns ticks since 1601), plus the Mac HFS+ / Cocoa epoch (seconds since 2001)
- ISO 8601 output to nanoseconds (`2026-10-05T12:34:56.123456789Z`) — the parts past the millisecond are assembled as strings, since Date stops at milliseconds
- The 20 most-used zones pinned to the top, with the other 400+ IANA zones searchable by id, city or localized name, each row showing that zone’s current offset
- Non-whole-hour offsets such as India +05:30, Nepal +05:45 and Adelaide +10:30 — the zones an hour-only implementation quietly gets wrong by half an hour
- Offsets are taken at the instant being converted, so DST and historical rule changes never shift a result by an hour
- Times skipped by DST raise an error, times that happen twice list both — nothing is silently nudged
- Each result row shows seconds, milliseconds, the selected zone, UTC, ISO 8601 and RFC 2822, and copies on its own
- Batch mode: one entry per line, timestamps and date-times mixed freely, and one bad line does not spoil the rest
- Batch output copies as TSV or downloads as CSV
How to use
- Want the current timestamp? Click the number at the top — it drops into the input
- Timestamp to date: paste it into the first panel and set the unit and zone
- Date to timestamp: pick one with the calendar, or paste the text
- Click Copy on any row to take just that value
- Converting a lot at once? Switch to Batch and paste one entry per line
FAQ
- How are time zones computed, and are they right?
- They come from the browser’s built-in IANA time zone database, so daylight saving start and end dates — and countries that changed their rules, such as Moscow going to permanent UTC+4 in 2011 and back to UTC+3 in 2014 — are resolved for the instant being converted rather than looked up from a fixed offset table. The 20 most-used zones are pinned to the top and the other 400+ are searchable by id, city or localized name — Berlin, Lisbon and Ho Chi Minh City used to be unpickable. The common ones take fewer keystrokes; the obscure ones are still reachable.
- What if I do not know which zone the data is in?
- Convert in UTC. Picking the wrong zone shifts every result by whole hours, and the shift is invisible — you still get a perfectly well-formed date. When you are unsure which zone a server log was written in, convert in UTC and apply the offset yourself rather than guessing at a zone that is probably right.
- What happens during a daylight saving change?
- On the day DST starts, some clock times do not exist in that zone (02:30 on 2026-03-08 in New York, for instance). The tool reports that plainly and names the skipped span rather than quietly nudging the time to 01:30 or 03:30 — a nudged timestamp looks normal but is an hour out. On the day DST ends, some clock times happen twice (01:30 on 2026-11-01 in New York), and both timestamps are listed, with the earlier one used by default.
- Why was my date format rejected?
- Only a fixed set of formats is accepted (2026-09-18, 2026-09-18 15:30, 2026-09-18T15:30:45), because JavaScript’s new Date(string) is parsed differently across engines — the same input can give different dates and never raises an error. Anything ambiguous, such as 09/18/2026, is refused rather than guessed at. Impossible dates such as 30 February are rejected too, never rolled over.
- What is the year 2038 problem?
- Systems that store seconds in a signed 32-bit integer overflow on 2038-01-19 03:14:07 UTC. This tool works in milliseconds internally and covers roughly ±273,000 years, so dates past 2038 convert fine.
- What is a 19-digit number? Will it be rejected as a snowflake ID?
- 19 digits are now read as nanoseconds (10 digits seconds, 13 milliseconds, 16 microseconds, 19 nanoseconds). That band used to be refused, but a 19-digit value really can be a nanosecond timestamp, so it is recognised by length. ⚠️ Nanoseconds are computed with BigInt: 19 digits exceed 2^53, and `Number` silently turns `1700000000123456789` into `1700000000123456800` (off by 11) while looking like an ordinary number. So the nanosecond value survives the round trip digit for digit, and the ISO string is assembled to nanoseconds. If it really is a snowflake ID, reading it as nanoseconds lands on a date around 2023 — that is what its value means, not a guess by the tool.
- Why add microseconds, nanoseconds and FILETIME?
- Because they are genuinely in use: microseconds appear in Python’s `time.time()` and in some logs, nanoseconds are what Linux `CLOCK_REALTIME` and Go’s `time.UnixNano()` report, and Windows FILETIME is a 100-nanosecond count since 1601-01-01 UTC (11,644,473,600 seconds before the Unix epoch) found all over the registry and event logs. The four bands convert in one step and FILETIME goes both ways. Fractions round to the nearest nanosecond; ticking whole-number output writes the integer part only (truncating rather than rounding).
- Is anything uploaded?
- No. Every conversion runs in your browser’s memory, the page makes no network requests, and it keeps working offline.
Related tools
Date Calculator
ConvertCount the days, weeks or months between two dates, or shift a date by any of those. Dates can be picked from a calendar or pasted in — nothing is uploaded.
Cron Parser
ConvertExplain a cron expression field by field and list the next and previous run times, saying plainly when a schedule can never fire.
JWT Decoder & Verifier
EncodingDecode a JWT and verify an HS256, HS384 or HS512 signature with your secret, reading exp and nbf as dates. All local to your browser.
Number Base Converter
ConvertConvert numbers between binary, octal, decimal, hex, base 36 and base 64, with long IDs converted digit for digit. Runs in your browser.
Color Converter
ConvertConvert between HEX, RGB, HSL, HWB, CMYK, Lab and OKLCH, with colour temperature, inverse, complement, nearest ANSI colour and WCAG contrast.
CSS Units
ConvertConvert a CSS length between px, rem, em, vw, vh and more. Root font size and viewport are adjustable, and each row says what it assumed.