Live UTC clock
Current timestamp now in UTC
Copy the live Unix timestamp, current epoch time, unix time, or current time millis from one page. The seconds value rolls forward each second, and the millisecond value refreshes several times per second for JavaScript, APIs, SQL, logs, and monitoring checks.
Current timestamp answers right now
If you searched for current timestamp, timestamp now, unix timestamp, unix time, epoch time, current epoch time, or current time millis, the intent is usually immediate: get the live value, understand whether it should be seconds or milliseconds, and verify the readable UTC time before pasting it into code. This section answers that directly with live values instead of static examples.
timestamp now, current epoch time
Current timestamp
——————————
This is the live 10-digit Unix timestamp right now in UTC. It is the format most APIs, SQL checks, cache expirations, and logs expect.
timestamp in milliseconds
Current time millis
—————————————
This is the live 13-digit Unix millisecond value. Use it for Date.now(), frontend telemetry, browser events, and analytics SDKs.
unix timestamp, epoch time, unix time
Unix time / unix epoch
——————————
These terms all point to the same current UTC-based counter since January 1, 1970. The wording changes, but the live value is the same 10-digit number.
human-readable answer
Current UTC time
Loading current UTC time...
Use the readable UTC time when you need to confirm what the live Unix timestamp means before pasting it into an API request or log search.
Which live format matches your search?
| Query wording | Return this format | Live value | Usually used for |
|---|---|---|---|
| current timestamp / timestamp now | 10-digit Unix seconds | —————————— | APIs, SQL, shell scripts, cache expiry, logs |
| current epoch time / unix timestamp / unix time / unix epoch | The same 10-digit Unix seconds | —————————— | Backend code, monitoring, docs, server-side checks |
| current time millis | 13-digit Unix milliseconds | ————————————— | Date.now(), frontend events, telemetry, SDKs |
| what time is that timestamp | Readable UTC date + ISO 8601 | Loading current UTC time... | Debugging, incident review, payload inspection |
The important distinction is not current timestamp vs unix time. Those phrases mean the same live UTC instant. The real split is 10-digit seconds vs 13-digit milliseconds. If you are unsure, most backend APIs and SQL tools want seconds, while browser code and analytics scripts usually want milliseconds.
Need a timestamp for today, not just right now?
Some searches hitting this page are really asking about current date timestamp, timestamp today, or today unix time. That is slightly different from timestamp now. Unix time always points to an exact instant, so the right answer depends on whether you need the live second right now or the UTC boundary for today.
| Use case | UTC moment | Seconds | Milliseconds | Best when |
|---|---|---|---|---|
| Current timestamp right now | Loading current UTC time... | —————————— | ————————————— | Live API requests, cache expiry, webhook signing, and log correlation |
| Start of today in UTC | Loading current UTC date... | —————————— | ————————————— | Daily rollups, SQL WHERE clauses, and reporting windows |
| End of today in UTC | Loading current UTC date... | —————————— | ————————————— | End-of-day filters, cron cutoffs, and UTC-safe date boundaries |
If your query is really about now, copy the live values at the top of the page. If it is about today, use a UTC boundary like midnight or 23:59:59 so SQL, analytics, and cron jobs stay consistent across timezones.
Current time in milliseconds, current UTC timestamp, and current Linux time
Google is already testing this page for exact variants like current time in milliseconds, current time ms, current utc timestamp, current unix timestamp, and current linux time. The table below maps each phrasing to the correct live number, the correct command, and the context where that answer is actually useful.
| Query cluster | Copy this live value | Direct answer | Command or code | Use it for |
|---|---|---|---|---|
| current unix timestamp / current timestamp / timestamp now | —————————— | Copy the 10-digit Unix seconds value. | Math.floor(Date.now() / 1000); // —————————— | REST APIs, SQL filters, cache expiry checks, and server logs |
| current time in milliseconds / current time ms / current millis | ————————————— | Copy the 13-digit Unix millisecond value. | Date.now(); // ————————————— | Frontend events, telemetry, analytics SDKs, and browser code |
| current utc timestamp / current utc seconds | —————————— | It is the same Unix seconds value, displayed as the current UTC time. | int(time.time()) # —————————— | UTC-safe backend jobs, payload validation, and cross-timezone debugging |
| current linux time / current unix time on Linux | —————————— | Use the same live Unix seconds value from the shell. | date +%s # —————————— | Terminal checks, shell scripts, cron jobs, and incident response |
A UTC timestamp is not a different timestamp
The raw Unix number is already UTC-based. Only the readable formatting changes when you switch between UTC and a local timezone.
Seconds vs milliseconds is the real decision
Most backend systems want 10-digit seconds. Browser runtimes, Date.now(), and telemetry pipelines usually want 13-digit milliseconds.
Linux date +%s returns seconds, not milliseconds
If you need current time in milliseconds on Linux, use the live ms value on this page or a runtime like Node or Python instead of assuming the shell command is already ms.
Copy the readable UTC time when you need human verification
When debugging a payload or a log line, confirm the Unix number against the UTC time shown on this page before sending it downstream.
If you want a page tuned to one narrower intent, jump to current timestamp, current time in milliseconds, current epoch time now UTC, or current epoch time now in milliseconds.
Get it in your code
JavaScript
Math.floor(Date.now() / 1000)
Python
import time; int(time.time())
Go
time.Now().Unix()
Rust
SystemTime::now() .duration_since(UNIX_EPOCH) .unwrap().as_secs()
Java
Instant.now().getEpochSecond()
Bash / Terminal
date +%s
Need more languages? See all 21 language examples →
Current timestamp, unix timestamp, epoch time, and current time millis
Searchers use several phrases for the same live clock. On this page, current timestamp, timestamp now, unix timestamp, unix time, and epoch time all point to the same UTC-based number of seconds since January 1, 1970 00:00:00 UTC. When the query says current time millis, the searcher usually needs the 13-digit millisecond form instead of the 10-digit seconds form.
| Search query | What it usually means | Live value | Best fit |
|---|---|---|---|
| current timestamp | 10-digit Unix seconds | —————————— | API requests, SQL tests, cache expiry, and logs |
| timestamp now | The same live Unix seconds value | —————————— | Fast copy-paste during debugging |
| unix timestamp / unix time | Another name for current epoch seconds | —————————— | Server code, CLI tools, monitoring, and docs |
| epoch time / current epoch time | The UTC-based counter since 1970 | —————————— | Backend systems and cross-timezone comparisons |
| current time millis | 13-digit Unix milliseconds | ————————————— | JavaScript Date.now(), browsers, and event telemetry |
Current timestamp in seconds
Use the 10-digit value when you need the current Unix timestamp for backend APIs, databases, logs, or shell commands. Example: 1767225600 is the Unix timestamp for 2026-01-01 00:00:00 UTC.
Current time millis
Use the 13-digit value when the system expects milliseconds, such as Date.now(), frontend event timestamps, Android, or analytics SDKs. The same 2026 moment in milliseconds is 1767225600000.
Live examples you can paste right now
If you searched for current timestamp or unix time, you usually need a value you can paste into code, a query, or a debugging session without extra conversion. These examples use the live values from this page instead of static placeholders.
JavaScript milliseconds
Date.now(); // —————————————
Unix seconds for APIs
Math.floor(Date.now() / 1000); // ——————————
PostgreSQL
SELECT to_timestamp(——————————);
ISO 8601 UTC
Loading live ISO timestamp...
When to convert the timestamp to a date
Unix time is great for machines because it is compact, sortable, and timezone-neutral. Humans usually need a readable date. If you are checking whether a timestamp is valid, comparing local time to UTC, or reading a log entry, convert the raw number to a date instead of trying to decode it mentally.
Use the full converter to turn Unix seconds or milliseconds into a readable UTC or local date, or jump to focused pages for current timestamp, current time in milliseconds, unix timestamp to date, and JavaScript timestamp examples.
If your real search is epoch converter, epoch to date, or date to epoch
This current timestamp now page is best when you need the live Unix value right away. If the job has shifted into epoch converter, epoch to date, epoch time to date, or date to epoch, open the homepage tools below to paste a raw Unix number, auto-detect seconds versus milliseconds, or generate a fresh epoch value from a calendar time.
Frequently Asked Questions
What is the current Unix timestamp?
The current Unix timestamp is the number of seconds elapsed since January 1, 1970 at 00:00:00 UTC (the Unix epoch). It's a single integer that increments by 1 every second, everywhere in the world simultaneously.
What is the difference between seconds and milliseconds timestamps?
A 10-digit number (e.g., 1708560000) is seconds — used by Unix, databases, and most REST APIs. A 13-digit number (e.g., 1708560000000) is milliseconds — used by JavaScript's Date.now() and Java's System.currentTimeMillis().
Is the current UTC timestamp different from the current Unix timestamp?
No. A Unix timestamp is already UTC-based. The raw integer stays the same everywhere; only the human-readable formatting changes when you display it in UTC or a local timezone.
How do I get the current Unix timestamp on Linux?
Use date +%s in the shell for the current Unix timestamp in seconds. If you need milliseconds, use Date.now(), Python, Node, or the live 13-digit millisecond value on this page.
Why is Unix time always UTC?
Unix time counts seconds from a fixed UTC point in history. There's no timezone embedded — it's just a number. Timezones only apply when you format the timestamp into a human-readable date string.
What is the Y2K38 problem?
32-bit systems overflow on January 19, 2038. Modern 64-bit systems are unaffected — a 64-bit timestamp can represent dates up to the year 292 billion. All major languages and databases now default to 64-bit timestamps.