Timestamp Converter

100% private

Unix epoch to a readable date and back — converted on your device, never on a server.

What have you got?

Timestamp → Date A number like 1785758382 Date → Timestamp A calendar date and time

Your timestamp

Right now —

Every conversion happens in this tab. No value you enter is sent anywhere, and there is no server to rate-limit you.

Show it in

The date

—

Advanced options

Read my number as

Only worth changing if your timestamp has an unusual number of digits — a very old date in milliseconds, say, or a value padded with zeros.

Clock format

Checking usage…

This moment around the world

About this date

The same value in your code

Step by step

How to convert a Unix timestamp to a date

Four steps, no account, no daily limit, and no advert sitting between you and the answer.

Pick your direction

Choose Timestamp → Date if you have a number out of a log or an API, or Date → Timestamp if you have a calendar date and need the epoch value.

Paste your value

Type or paste the timestamp. Commas and spaces are fine. The unit is worked out from how many digits it has, so you do not have to know whether it is in seconds or milliseconds.

Choose a time zone

Your own zone is selected already. Switch it to see the same instant as someone in another country would read it — useful when a log is in UTC and your users are not.

Take the result

Copy any single line with the button beside it, or press Copy the date & 5 formats for the whole set at once, ready to paste into a ticket or a message.

Private by design

Why nothing you type here is sent anywhere

A timestamp looks harmless until you notice what it usually comes attached to: a customer record you are debugging, an incident timeline, a security log, a database export you should probably not be pasting into a stranger’s website at all. Most converters post that value to a server to convert it. This one has no server to post it to, and you can prove that in about ten seconds.

Nothing is uploaded

The converter is downloaded to your browser once and then does all its arithmetic on your device. The value you type never enters a network request, so there is no copy of it for us to keep, lose, sell or be compelled to hand over.

Nothing is saved

We deliberately do not remember what you converted, not even in your own browser’s storage. Close the tab and it is genuinely gone — there is no history sitting on a shared machine for the next person to scroll through.

No account, no limits

No sign-up, no email capture, no advert between you and the answer, and no “too many requests, try again later”. A converter that runs on your own machine cannot run out of quota, however many timestamps you throw at it.

To be precise about what does leave your device — because “100% private” is easy to say and worth checking. Three things, none of them the value you typed:

1. The first time you convert something, this page sends one anonymous message to our counter saying “timestamp-converter was used”. Not your timestamp, not the date, not the time zone you picked, nothing identifying you. It exists so the usage number in the panel is a real one rather than something we invented.
2. Google Analytics records the page view and that the tool was used, the same as on every other page of this site. It is told which direction you converted in and whether the zone you chose was your own — as a yes or no, never the zone itself, because the zone would say roughly where you are. Block it and the converter works exactly the same.
3. When the page first loads, the fonts it is set in are fetched from Google Fonts, which means Google sees your IP address at that moment — the same as on every other page of this site. Once the page has loaded, that request never happens again, which is why the offline test below works.

Your timestamp is in none of them. It never enters a network request at all — and unlike a promise, that is something you can check. Turn off your wifi, reload this page and keep converting. It still works. No server-side converter can pass that test.

At a glance

Tool specifications

Input	A Unix timestamp in seconds, milliseconds, microseconds or nanoseconds — or a calendar date and time
Output	Full date in your zone and in UTC, ISO 8601, RFC 2822, relative time, and the value in all four units
Unit detection	Automatic, from the number of digits: up to 11 is read as seconds, 12–14 as milliseconds, 15–17 as microseconds, 18 or more as nanoseconds. Overridable
Time zones	Every IANA zone your browser knows, typically around 420, with your own selected by default
Dates before 1970	Supported. Negative timestamps convert normally — `-86400` is 31 December 1969
Daylight saving	Handled explicitly. Times that do not exist, and times that happen twice, are flagged rather than silently guessed
Range	About 273,790 years either side of 1970, which is the limit of the date type itself
Precision	Millisecond. Larger units are converted by shifting the decimal point, so a 19-digit nanosecond value keeps every digit
Rate limit	None. There is no server to rate-limit
Where processing happens	In your browser, on your device — nothing is uploaded
Saved anywhere	No. Not on a server, and not in your browser’s storage either
Works offline	Yes, once the page has loaded, including as an installed app
Sign-up	Not required, not offered
Price	Free

Questions

Epoch time, answered

Is my timestamp uploaded or stored anywhere?

No. The conversion runs entirely inside your browser using code downloaded to your device, so the value you type is never placed in a network request and never reaches us. We also do not save it to your browser’s storage, so it does not linger on a shared computer. The simplest proof: disconnect from the internet and keep converting — it still works.

What is a Unix timestamp, in plain terms?

It is the number of seconds that have passed since midnight UTC on 1 January 1970, a moment known as the epoch. Computers store time this way because a single counting number is far easier to compare, sort and do arithmetic on than a date with months, time zones and leap years in it. The trade-off is that it means nothing to a human, which is what this page is for.

Is my number in seconds or milliseconds?

Count the digits. A present-day timestamp in seconds has 10 digits, in milliseconds 13, in microseconds 16 and in nanoseconds 19. This tool counts them for you and says which unit it used. The usual giveaway that you have guessed wrong: a value read as seconds when it was really milliseconds lands somewhere around the year 56000, and one read the other way lands in January 1970.

Why does my timestamp show a time a few hours out?

Almost always a time zone difference rather than a wrong timestamp. A Unix timestamp has no time zone at all — it is a single instant, and the same instant is 09:09 in London and 14:39 in India. Servers and databases usually record in UTC, so a log line will look several hours off from your local clock. Switch the zone selector to UTC and the number should match what your server reported.

Can it handle dates before 1970?

Yes. Dates before the epoch are simply negative numbers — -86400 is one day before it, 31 December 1969 — and they convert here exactly like any other value. Quite a few converters reject a leading minus sign or return an error, which is worth knowing if you are working with historical records or with software that stores birth dates as timestamps.

What happens with daylight saving changes?

Two awkward things can happen when you convert a date into a timestamp, and this tool tells you about both. When clocks go forward, an hour is skipped, so a time like 02:30 may simply not exist on that date — we say so and show which instant we used instead. When clocks go back, an hour repeats, so 01:30 happens twice and there are two valid timestamps — we use the first and show you the second. Most converters quietly pick one and say nothing.

What is the year 2038 problem?

Older software stores timestamps in a signed 32-bit number, which runs out at 03:14:07 UTC on 19 January 2038. One second later it overflows and wraps round to December 1901. Modern systems use 64-bit values and are fine for longer than the universe is likely to need, but the limit still turns up in legacy databases, embedded devices and file formats. This page uses your browser’s own date type, so it is unaffected and converts 2038 dates normally.

Do I need to sign up, and is there a usage limit?

No account, no email, no paid tier and no cap. Because the conversion happens on your machine rather than ours, there is nothing for us to meter — you could convert a timestamp a second all day and it would cost us nothing. Nopturnia funds itself through affiliate links on its product buying guides, not through these tools.

Keep it handy

Save it, share it, or tell us what’s missing

Come back to it

Bookmark the page, or pin it to your saved tools so it sits at the top of the tools list on this device.

A date look wrong?

If a conversion disagrees with your database, a time zone is missing, or you need a format that isn’t here, tell us. The form opens with the tool already filled in, so you only have to describe what happened.

Give feedback on this tool

More free tools

Other things you can do here

Every one of these runs the same way — on your device, with nothing uploaded.

New PDF to Image Turn any PDF page into a PNG or JPG you can drop into a slide, a doc or a chat. Documents New tool New Character & Word Counter Live word, character and reading-time counts as you type or paste. Text New tool

Coming soon Unit Converter Length, weight, temperature, area, speed — every everyday unit, converted instantly. Converters In the works

Coming soon General Utility Converter Base64, URL encoding, hex, binary and hashes — the developer odds and ends. Converters In the works

Coming soon PDF to Word Pull the text out of a PDF into an editable Word document, without an upload. Documents In the works

Coming soon Reduce Any File Size Squeeze a PDF or image down until it fits that stubborn upload limit. Documents In the works

See all tools