Seconds
Increases once per second. Present-day values are generally about 10 digits and are widely used.
Current Unix time
Current Unix
timestamp
See this instant as Unix seconds, milliseconds, microseconds and nanoseconds alongside UTC, Korea Standard Time and your device time. Pause the clock when you need a stable value to copy.
Unix time right now
Seconds update once per second and milliseconds change more quickly. Pause before copying the unit you need.
Live numbersBased on device clock
Unix seconds
—Unix milliseconds
—Unix microseconds
—Unix nanoseconds
—The same instant as datesUTC · KST · device
UTC
Korea Standard Time
Current device time zone
Microseconds and nanoseconds are the millisecond clock value multiplied by 1,000 and 1,000,000. The extra digits do not make the device clock more precise.
How to read the current timestamp
Unix time expresses elapsed time from a fixed reference instead of a calendar label. The value is identical for the same instant in every region.
Milliseconds
Splits each second into 1,000 parts. Present-day values are generally 13 digits.
Time zone is a display
The Unix number stays fixed while UTC, Korea or another region changes the visible clock and date.
Unit relationship One second equals 1,000 milliseconds, 1,000,000 microseconds or 1,000,000,000 nanoseconds.
If another clock shows a different value
This page calculates from your device, so check the device setting when the difference is more than a few seconds.
1. Automatic time setting
Confirm that automatic date and time synchronization is enabled on the phone or computer.
2. Seconds versus milliseconds
A 10-digit and 13-digit value differ by a factor of 1,000. Convert both to the same unit before comparing.
3. Return from sleep
If the device was asleep or the tab was hidden, return to the page and confirm that a fresh value appears.
The Unix time basis and leap-second treatment are described in the POSIX time rationale. Browser clock behavior is documented in MDN Date.now().
When a current timestamp is useful
Use the current value to mark an event or compare the order of records.
| Task | Suggested format | Why | Check |
|---|---|---|---|
| Record the current time simply | Seconds | Short and widely supported | Cannot distinguish events within one second |
| Order closely spaced events | Milliseconds | 1,000 divisions per second | Confirm the receiving unit |
| Share a human-readable date | ISO 8601 | Can include the time-zone offset | Include Z or an explicit offset |
| Compare a Korean schedule | KST date | Immediately readable on a Korean calendar | Keep the original Unix number for verification |
Current Unix time questions
Answers about the live value, units and practical accuracy.
When does the current Unix timestamp start counting?
It counts elapsed time after 1970-01-01 00:00:00 UTC. A seconds value counts seconds; a milliseconds value counts thousandths of a second.
Should I copy seconds or milliseconds?
Use the unit required by the destination. Around the present date, seconds are usually 10 digits and milliseconds 13 digits, but the destination specification is authoritative.
Can this clock differ from another clock?
Yes. It follows your device clock, so an incorrect device setting produces the same error here. Check automatic date and time settings when accuracy matters.
Why do microseconds and nanoseconds end in zeros?
The live value comes from a millisecond-resolution device clock. Converting that value into smaller units adds digits but does not increase the clock's true precision.
Continue from the current value
Convert the copied number to a date or create a timestamp for another calendar time.
Interpret a number
Timestamp → date
Convert a current or historic value to UTC, KST and local dates.
Show the date →Calculate a dateDate → timestamp
Create seconds and milliseconds for a chosen date.
Create a number →Match unitsSeconds ↔ milliseconds
Compare exact Unix units for one instant.
Convert units →