The free online timestamp converter turns a Unix epoch number into a readable date and back, in UTC, local time and ISO 8601, with seconds and milliseconds detected on their own. Because it runs in the browser, nothing is uploaded.
Developer tools by OnlinePCApps since 2013
A log or a token holds a bare number like 1704067200, and a query needs that number for a date. The free online timestamp converter turns one into the other in the format the job needs.
A log line, a database row or a JWT token often stores a moment as a plain epoch number that means nothing at a glance. Converting it shows the real date in UTC and local time, so a record lands in context at once.
A database filter, an API parameter or a token expiry needs a date written as an epoch number. Picking the date here returns the exact Unix timestamp in seconds or milliseconds, ready to drop straight into the query.
The most common timestamp bug is treating milliseconds as seconds, which throws a date thousands of years out. Auto-detecting by the digit count names the unit, so a value in the wrong scale is spotted before it causes a problem.
Paste a Unix epoch number into the panel above, or pick a date and time. A number is read as a timestamp, and the seconds or milliseconds unit is worked out from the digit count on its own.
The moment shows in UTC, in local time, as an ISO 8601 string and as a relative phrase such as two hours ago. A time zone can be picked to see the same instant in another place.
Copy the format the job asks for, whether the epoch number, the ISO string or the readable date. A live current timestamp sits alongside, updating each second for a quick reference.
To convert a timestamp is to read the same instant as a number or a date. The tool does that on the device.
A Unix epoch number is turned into a readable date, and a picked date is turned back into a timestamp. The two directions share one panel, so a number becomes a moment or a moment becomes a number without a second tool.
A value is read as seconds or milliseconds from its digit count, ten for seconds and thirteen for milliseconds, so the unit is named rather than guessed. That catches the most common timestamp bug before a date lands thousands of years out.
The moment shows in UTC and in local time together, and a time zone can be picked to read the same instant elsewhere. The epoch number never changes with the zone, since it is the zone-free count that a date is drawn from.
An ISO 8601 string and a relative phrase such as two hours ago sit beside the readable date, and a live current timestamp updates each second. The ISO form is the one to store, unambiguous and sortable as text.
To convert a timestamp, to turn epoch to a date and to read Unix time all name the same tool. A search for timestamp converter or epoch converter reaches this page, and the value is left as it is.
A Unix timestamp is one number for a moment in time. These points decide how it reads.
| The case | Result | What happens and why |
|---|---|---|
| The epoch | 1970 UTC | Seconds since 1 January 1970 at midnight UTC, the Unix epoch. |
| Seconds | 10 digits | The classic unit, used by most server languages and databases. |
| Milliseconds | 13 digits | The unit JavaScript uses, a thousand times finer than seconds. |
| Auto-detect | by digits | The unit is read from the digit count, so seconds and ms are told apart. |
| Time zone | free | The number is zone-independent, and a zone only shapes the readable date. |
| ISO 8601 | the wire format | An unambiguous, sortable string such as 2024-01-01T00:00:00Z. |
| Before 1970 | negative | A date earlier than the epoch reads as a negative timestamp. |
| Year 2038 | 32-bit limit | A signed 32-bit timestamp overflows on 19 January 2038, a 64-bit one does not. |
| Where it runs | on the device | The conversion runs in the browser, so nothing is uploaded. |
How a Unix Timestamp Works
A Unix timestamp is a single number, the count of seconds since midnight UTC on 1 January 1970, the moment known as the Unix epoch. It is also called epoch time, POSIX time or Unix time. All of those mean the same thing. The strength of it is that one number names one instant everywhere on the planet, with no time zone baked in and no argument over whether a date is written day first or month first. A zone enters only when the number is turned into a readable date, which is why changing the zone moves the written date while the epoch number stays put. Two honest points cause most of the trouble. The first is the unit: a timestamp in seconds is about ten digits and one in milliseconds is thirteen, and JavaScript works in milliseconds while most servers work in seconds, so reading one as the other throws a date wildly out. The second is the Year 2038 problem, where a timestamp stored in a signed 32-bit integer runs out of room at 03:14:07 UTC on 19 January 2038, which a 64-bit integer fixes with room to spare. Unix time also ignores leap seconds, and a date before 1970 is a negative number. The references below define the standard.
Both convert a timestamp. The trade is between a quick visual lookup and a scriptable batch.
| Point of comparison | This tool Converted in the browser On the device | The command line A local terminal tool |
|---|---|---|
| Where the work runs | All in the browser | On the machine |
| Price and caps | Free with no file cap | Free tier often capped |
| A whole column of values | One value at a time | A column in one command |
| Part of a pipeline | A manual paste here | date in a build or cron |
| Every format at once | UTC, local, ISO, relative | One format per flag |
The date command wins for a whole column of values or a conversion inside a script or a cron job. This page wins for a quick lookup that shows UTC, local, ISO and relative at once, with a live clock and no install. Both keep the work local.
The conversion is date arithmetic run by the browser's own Date object, so the work is client-side and every value stays on the machine that opened it. Nothing is handed to a server to do the maths.
A timestamp is often pulled from a token, a private log or an internal record. The moment it marks can be telling on its own. Keeping the conversion local means that value is never sent to an outside server only to be read as a date.
Each of these converts a timestamp. They vary in reach, in effort and in where the value goes.
The date command, code, a spreadsheet and a database all convert a timestamp, yet each means a syntax to recall or a unit to line up. This page shows every format at once with a live clock, kept local with nothing to set up.
A little context saves a wrong date.
Ten digits is seconds and thirteen is milliseconds, and reading one as the other is the most common timestamp bug. If a date lands in 1970 or thousands of years out, the unit is almost always the reason.
A Unix timestamp is zone-free, and a readable date only gains a zone when it is written. Store and compare the epoch number or a UTC ISO string, and apply a local zone at the last moment for display.
A timestamp held in a signed 32-bit integer overflows on 19 January 2038. Where a date reaches near or past that point, store it in a 64-bit integer so the value has room, which is now the default on modern systems.
The browser converts one timestamp or a date at a time, which suits a quick lookup. A whole column of epoch values in a log, a spreadsheet or a database belongs on the date command or a short script, which converts the lot straight from disk in one pass.
Convert a full column of epoch values in a log or a sheet in one command, every value turned to a date in a single pass.
A conversion step runs inside a build, a cron job or a data pipeline, so a value is turned automatically with no manual paste.
Convert a value against a chosen zone or offset in bulk, matched to the region a report or an export is read in.
Free and online, with no sign-up and no upload. Turn a timestamp into a date in the browser, all on the device.