Current Unix Timestamp
Epoch time right now, ticking once per second, next to the local hour in seven major time zones. Hover any hour to convert it across all of them; click to pin it, then copy the timestamp or a per-zone ISO 8601 string.
| Zone | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | Copy |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| UTC | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | |
| Los Angeles | 17 -1d | 18 -1d | 19 -1d | 20 -1d | 21 -1d | 22 -1d | 23 -1d | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | |
| New York | 20 -1d | 21 -1d | 22 -1d | 23 -1d | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | |
| London | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 00 +1d | |
| Berlin | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 00 +1d | 01 +1d | |
| Kolkata | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 00 +1d | 01 +1d | 02 +1d | 03 +1d | 04 +1d | |
| Tokyo | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 00 +1d | 01 +1d | 02 +1d | 03 +1d | 04 +1d | 05 +1d | 06 +1d | 07 +1d | 08 +1d | |
09–17 working hours 07–09 shoulder 23–06 night Hover an hour to convert it · click to pin it, then copy any row
| Milliseconds | 1792655004493 |
|---|---|
| Microseconds | 1792655004493000 |
| Nanoseconds | 1792655004493000000 |
| ISO 8601 (UTC) | 2026-10-22T07:43:24.493Z |
| UTC / GMT | Thursday, 22 October 2026 at 07:43:24 UTC |
| Your local time | detected in your browser |
| RFC 2822 | Thu, 22 Oct 2026 07:43:24 +0000 |
| Day of year / ISO week | Day 295 · ISO week 43 of 2026 |
What this number counts
It is the number of seconds elapsed since 00:00:00 UTC on 1 January 1970, excluding leap seconds. Nothing in it encodes a time zone, a calendar or a locale — those are applied only when the value is rendered. That is precisely why it is the format almost every system uses internally.
Getting the current timestamp in code
| Language | Seconds | Milliseconds |
|---|---|---|
| JavaScript | Math.floor(Date.now()/1000) | Date.now() |
| Python | int(time.time()) | int(time.time()*1000) |
| PHP | time() | (int)(microtime(true)*1000) |
| Go | time.Now().Unix() | time.Now().UnixMilli() |
| Java | Instant.now().getEpochSecond() | System.currentTimeMillis() |
| Ruby | Time.now.to_i | (Time.now.to_f*1000).to_i |
| Rust | SystemTime::now()…as_secs() | …as_millis() |
| Bash | date +%s | date +%s%3N |
| SQL (Postgres) | EXTRACT(EPOCH FROM now()) | … * 1000 |
Fuller examples, including parsing and formatting, are on the code pages.
A warning about client clocks
This page reads Date.now() from your browser, which reads your
operating system clock. That clock can be wrong — by seconds from ordinary
drift, or by hours if the zone or date was set by hand. Never trust a
client-supplied timestamp for anything security-relevant such as token
expiry, rate limiting or audit logs. Stamp those on the server, and treat any
client timestamp as an unverified claim.
Related tools
Frequently asked questions
What is the Unix timestamp right now?
The large number at the top of this page is the current epoch time in seconds, updating every second. The rows beneath it show the same instant in milliseconds, microseconds and nanoseconds, plus ISO 8601 and UTC form.
Is this clock accurate?
It reads your own device clock, so it is exactly as accurate as your machine is. If your system clock has drifted, this page drifts with it. For anything requiring real accuracy, sync against NTP rather than trusting a browser.
How do I get the current timestamp in my code?
In JavaScript, Math.floor(Date.now() / 1000). In Python, int(time.time()). In PHP, time(). In Go, time.Now().Unix(). Full examples for 21 languages are on the code pages.
Why does the timestamp not reset at midnight?
Unix time is a single continuously increasing counter, not a clock that wraps. It has been incrementing once per second since 1970 and has no concept of days, months or time zones — those only appear when the value is formatted for a human.
Why is the Unix timestamp the same in every time zone?
Because it counts seconds from a single fixed instant in UTC, not from a local midnight. At any given moment the epoch value in Tokyo, London and Los Angeles is identical — only the rendering differs. That is why the grid above shows one timestamp and seven different wall clocks: one instant, seven ways of writing it down.
Is EST the same as New York time?
Only in winter. New York observes Eastern Standard Time (UTC−05:00) from early November to mid-March, and Eastern Daylight Time (UTC−04:00) for the rest of the year. A tool that prints a hardcoded "EST" is wrong for roughly eight months out of twelve, so the grid above derives each abbreviation from the zone's real rules for the instant being shown.
What is the current Unix timestamp in IST?
The same number as everywhere else — the epoch has no time zone. What differs is the local clock: India Standard Time is UTC+05:30, one of the few zones on a half-hour offset, so 00:00 UTC is 05:30 in Kolkata. Use the copy button on the India row to get the ISO 8601 form with the +05:30 offset already attached.