Current Unix Timestamp
Epoch time right now, in seconds, counting up once a second and ready to copy.
One timestamp or date per line, up to 500.
Paste the code into a Discord message; everyone sees it in their own time zone and language.
Convert this timestamp in your own code.
The Current Unix Timestamp
Half the reason to open a timestamp tool is to get the number for right now: a value for a test fixture, a cache key, a token expiry, a "posted at" field, a quick comparison against a log line. The toolbar of the Timestamp Converter keeps it in view and updates it every second, and this page also feeds it into the converter so the matching date is on screen at the same time.
The counter is the number of seconds since 1 January 1970 at 00:00:00 <abbr title="Coordinated Universal Time">UTC, the moment known as the Unix epoch. It carries no time zone and no formatting, which is precisely why software stores time this way: one integer that can be sorted, compared and subtracted without a calendar in the loop. The Copy button next to it puts the value on the clipboard and says Copied so you know it took.
Reference points around today's value
A current timestamp is hard to sanity-check by eye, so it helps to know the landmarks it sits between.
| Value | Moment in UTC | Why it is worth knowing |
|---|---|---|
0 | 1 January 1970, 00:00:00 | The epoch itself; a date of 1970 usually means an empty or null value |
1000000000 | 9 September 2001 | The first ten-digit timestamp |
2147483647 | 19 January 2038 | The largest value a signed 32-bit field can hold |
9999999999 | 20 November 2286 | The last ten-digit timestamp |
Anything between the second and third rows is a plausible present-day value, which makes the digit count a reliable first check: ten digits is seconds, thirteen is milliseconds. The 2038 row is the one with a deadline attached, since a system still keeping time in a signed 32-bit field overflows on that date and starts reporting times in 1901.
Reading the same instant as a date
With the current value in the converter you get four lines at once: the instant in whichever zone is selected at the top right, the same instant in UTC, the ISO 8601 form that most APIs expect, and a relative line that reads "now" and drifts to "1 minute ago" if you leave the page open. Switching the zone re-renders all of it, which is the fastest way to answer "what time is it there" without doing the arithmetic. Clicking Use Current refreshes the field with the present moment, so the date always belongs to the number above it.
The same value in code
- JavaScript:
Math.floor(Date.now() / 1000), sinceDate.now()itself gives milliseconds. - PHP:
time(). Python:int(time.time()). - MySQL:
UNIX_TIMESTAMP(NOW()). PostgreSQL:EXTRACT(EPOCH FROM now())::bigint. - Go:
time.Now().Unix(). Java:Instant.now().getEpochSecond(). C#:DateTimeOffset.UtcNow.ToUnixTimeSeconds(). - Shell:
date +%s.
The Code tab under the converter prints these in context, so you can copy the whole snippet rather than retyping an expression. Each one also shows the conversion in the other direction for the value currently in the timestamp field.
Related pages
To read a number that is not the current one, use Timestamp to Date, or milliseconds to date when it has thirteen digits. To go from a calendar date to a number, Date to Timestamp applies the zone you choose to the time you type. And for a "starting now" message in a chat server, Discord timestamps wraps this same seconds value in markup that every reader sees in their own clock.