All Unix timestamp tools

Every epoch tool on Epoch Bin, in one place and grouped by what you are actually doing — converting a value, working out why a date came out wrong, digging a timestamp out of something that is not a timestamp, or looking up the one-liner for the language you are already in.

Converters

Paste a value and read the date back — or go the other way. Start here if you have a number, a date string, or a whole column and just want the other side of it.

Unix Timestamp Converter

(Convert any timestamp or date — with a live clock)

Bulk Timestamp Converter

(Paste a whole column, copy it back converted)

Current Unix Time

(The live epoch timestamp, updating every second)

ISO 8601 to Unix

(Convert ISO 8601 / RFC 3339 timestamps to epoch)

Timezone Conversion

(UTC to local time, any zone, DST included)

Timestamp Calculator

(Add, subtract, diff and round epoch timestamps)

Debugging

The date came out, and it is wrong. These three cover the ways an epoch value lands somewhere it should not: the wrong unit, a value that coerced to zero, and a counter that overflowed.

Why Is My Date 1970?

(Diagnose null, zero, and ms/s epoch bugs)

Milliseconds or Seconds?

(Auto-detect a timestamp's unit by digit count)

Year 2038 Problem

(The 32-bit Unix timestamp overflow, explained)

Formats and IDs

A timestamp that is not stored as a timestamp — buried in a token claim, packed into the leading bytes of an identifier, or wrapped in a chat client's own tag syntax.

JWT Expiry Decoder

(Is that token expired? Decode exp, iat, nbf)

MongoDB ObjectId → Timestamp

(The creation time hidden in every ObjectId)

Discord Timestamp Decoder

(Snowflake IDs, timestamp tags, and Slack epoch ts)

Languages and sheets

The one-liner for the language, database or spreadsheet you are already in, with the naive-versus-aware and seconds-versus-milliseconds traps each one sets.

Python Epoch/Timestamp Converter

(datetime ⇄ epoch, with copyable Python code)

JavaScript Epoch/Timestamp Converter

(Date ⇄ epoch, with copyable JavaScript code)

SQL Epoch Converter

(FROM_UNIXTIME, to_timestamp, datetime() — ready to paste)

Excel Timestamp Converter

(Unix ⇄ Excel serial dates, with paste-ready formulas)

How these tools are grouped

The four groups above are not categories for their own sake — they are the four situations that bring people to an epoch tool at all. Converters are for when you have a value and want the other side of it, one row or a whole pasted column at a time. Debugging is for when the conversion already happened and the answer is wrong: a date stuck at January 1, 1970, a value that is seconds where milliseconds were expected, or a 32-bit counter about to run out in 2038. Formats and IDs cover the timestamps that are not stored as timestamps — the expiry claim inside a JWT, the four leading bytes of a MongoDB ObjectId, a Discord snowflake. Languages and sheets is reference material: the exact call in Python, JavaScript, SQL or Excel, with the trap each one sets.

A page belongs to exactly one group, and the group it belongs to is what its own footer links to. That is deliberate: a fifteen-card block on every page told a reader — and a crawler — that everything here was equally related to everything else. Each page now points at its three or four nearest siblings and back at this index, which is one hop from anywhere and two hops from any page to any other.

Frequently asked questions

Which timestamp tool do I need?

Start from what you are holding. A bare number and you want a date: the main converter. A date that came out wrong — 1970, 1901, or a couple of weeks after the epoch: the debugging group. A token, an ObjectId or a chat tag with a time hidden inside it: the format and ID decoders. A file of rows rather than one value: the bulk converter.

Do these tools send my timestamps to a server?

No. Every tool on this site converts in your browser, with no upload, no account and no server round trip. That matters most for the decoders: a JWT pasted into a web tool is a credential pasted into a web tool, and here it never leaves the tab.

Why are there separate pages instead of one big converter?

Because the questions are different, not just the inputs. Deciding whether a value is seconds or milliseconds, working out why a date rendered as 1970, and reading the creation time out of a MongoDB ObjectId each need their own explanation and their own default. One page that did all of them would answer none of them completely.

Is a Unix timestamp the same thing as epoch time?

Yes. Unix time, epoch time and POSIX time all name the same value: the count of seconds elapsed since 00:00:00 UTC on 1 January 1970. Tools and documentation use the three names interchangeably, which is why the pages here answer to all of them.