Current Millis: Show the Current Unix Timestamp in Milliseconds
Current millis is whatever Date.now() returns in JavaScript right at this instant - a 13-digit integer counting milliseconds since the Unix epoch on 1 January 1970 UTC.
Last reviewed: 2026-09-16
FreetoolOnline editorial team| Property | Value |
|---|---|
| What "current millis" means | The integer Date.now() returns in JavaScript |
| Length at the time of writing | 13 digits (will stay 13 digits until the year 2286) |
| Where to read it without any tool | Browser devtools console: type Date.now() and press Enter |
| To convert millis back to a human date | Milliseconds to Date Converter |
| Privacy | The value lives entirely in your browser; nothing uploads |
How to read the current millis right now
The fastest path is the browser devtools console - press F12 (Cmd+Option+J on macOS), switch to the Console tab, type Date.now(), and press Enter. The console prints a 13-digit number; that integer IS the current millis at the moment you pressed the key. The value is computed locally by your browser using the operating system clock, so no network request fires and no service sees the number. Refresh the console output by hitting the up-arrow key and re-running the same command; the new number will be a few hundred to a few thousand units higher depending on how long you waited. If a live updating display is more convenient, the Current Time in Milliseconds tool on this site shows the epoch timestamp updating in the browser - no console needed.
If a console is not available - many corporate-locked browsers hide the F12 shortcut - the Milliseconds to Date Converter on this site opens with the current millisecond timestamp pre-filled in the input field. Reload the page and the prefill refreshes to the new "now". Copy the input field's value to your clipboard and you have the current millis without typing a single command.
How to convert a millis value back to a readable date
Paste any 13-digit Unix millisecond integer into the Milliseconds to Date Converter and the answer line below the input updates in place with the date expressed in your browser's local timezone plus the UTC equivalent. The conversion runs in the browser; the integer never leaves the page. Trailing letters or whitespace (a log line that writes the value as 1713538800000ms or wrapped in quotes) survives the paste because the page coerces the input to a Number before constructing the Date. Source: tool-converttimeinmillisecondtodate framing menu M3.
Sanity-check: is your value really in milliseconds?
A 10-digit value is almost always Unix seconds, not milliseconds, and the off-by-1000 bug is the single most common mistake developers hit when working with epoch numbers. Pasting a 10-digit value into the milliseconds converter yields a 1970-era date as the sanity-check output - the 1970 result IS the signal that the value should have been multiplied by 1000 first. The tool deliberately does not silently multiply on your behalf because the same 10-digit shape is also valid for sequence IDs and Snowflake-style identifiers; auto-multiplication would hide a real bug. Source: tool-converttimeinmillisecondtodate framing menu M2.
Privacy: where the number lives
The current millis is read from the same operating-system clock your browser uses to render the page. No JavaScript on this guide or on the implementing tool sends the value to a server; the only network calls after page load are static-asset fetches from CloudFront for the page styles and the date.format.js library. A privacy-flagged epoch (from a session log, an internal webhook, a confidential database row) can be pasted into the converter without leaving the device. Source: tool-converttimeinmillisecondtodate framing menu M4.
Getting the current millis value in different runtimes
Every major runtime exposes a millisecond-precision clock, but the exact call differs by language. Use the table below to copy the correct one-liner for your environment, then paste the resulting 13-digit number into the Milliseconds to Date Converter to read the matching calendar date.
| Runtime | One-liner | Notes |
|---|---|---|
| JavaScript / Node.js | Date.now() | Returns a 13-digit integer directly. +new Date() is an older equivalent. |
| Python 3 | import time; int(time.time() * 1000) | time.time() returns float seconds; multiply by 1000 and truncate. |
| Java / Kotlin | System.currentTimeMillis() | Returns a long. Java 8+: Instant.now().toEpochMilli() is the modern form. |
| PHP | (int)round(microtime(true) * 1000) | microtime(true) returns float seconds; multiply and round before casting. |
| Bash / Linux | date +%s%3N | Prints a 13-digit string. Requires GNU date; macOS date does not support %3N. |
| C# | DateTimeOffset.UtcNow.ToUnixTimeMilliseconds() | Available since .NET 4.6. Returns a long directly. |
Once you have the 13-digit number, paste it into the converter - the input field takes focus on load so you can paste-and-Enter without clicking the box first. The conversion runs in your browser; the value never leaves the device. Source: tool-converttimeinmillisecondtodate framing menu M3 + M4.
For a closer look at how to tell whether a long integer is in milliseconds or seconds - and why the off-by-1000 error is so common - see is this long number milliseconds or seconds. For the unit itself including conversions and the epoch baseline, read time in milliseconds - the unit, conversions, and epoch value.
Frequently Asked Questions
Does this page show a live, auto-updating millisecond counter?
No. This guide reads the value through the browser console or the converter's pre-filled input field, both a single snapshot at the moment you check. For a display that keeps counting on its own, use the Current Time in Milliseconds tool on this site instead.
Is Date.now() the same thing as performance.now()?
No. Date.now() returns the Unix epoch in milliseconds - a real calendar timestamp. performance.now() returns a high-resolution timer relative to when the current page started loading, not a calendar date at all. Treating the two as interchangeable produces a timestamp that is off by decades.
Does this guide cover time zones or daylight saving time?
No. It stays scoped to the raw 13-digit integer itself. For the local-time-vs-UTC display rules once a value is converted, see milliseconds to date: UTC vs local time; for epoch fundamentals more broadly, see Unix timestamps explained.
Do the per-runtime one-liners in the table above run automatically on this page?
No, they are copy-reference snippets only. Each one reads the clock of whatever environment you paste it into - your own terminal, script, or IDE - not a clock on this page, and different runtimes' clocks are not synchronized to each other or to this site.
Can this tool convert seconds, microseconds, or nanoseconds instead of milliseconds?
No. The guide and its converter are scoped strictly to 13-digit Unix milliseconds. A 10-digit value is flagged as likely seconds (see the sanity-check section above) rather than silently rescaled, and sub-millisecond precision such as microseconds or nanoseconds is out of scope entirely.