Unix Timestamp Converter - Free, Local

Convert a Unix epoch timestamp to a human-readable date, or the other way around, in both your local time zone and UTC.

How it works

Unix time counts seconds (or milliseconds, depending on the system) elapsed since 00:00:00 UTC on 1 January 1970, the epoch - a compact, time-zone-independent way to store a moment in time.

The tool auto-detects whether a pasted number is in seconds or milliseconds based on its magnitude, since both are common depending on the system that produced it.

Converting a date to a timestamp interprets the date and time you enter in your browser's local time zone, then shows the resulting epoch value alongside the equivalent UTC time for comparison.

Worked examples

Reading a timestamp from a JWT or log file

Paste the raw number to see it as a readable date - useful for checking a token's exp claim or a log entry's timestamp.

Getting the current timestamp

Use the 'now' button to grab the current Unix time in both seconds and milliseconds.

Converting a specific date to a timestamp for a script

Enter a date and time to get the equivalent epoch value to hard-code into a script or query.

Frequently asked questions

Is my input sent anywhere?

No, all conversion happens locally in your browser tab.

How does it know if my number is seconds or milliseconds?

By magnitude - a value around 10 digits is almost certainly seconds, while a 13-digit value is almost certainly milliseconds. Both current-era values are unambiguous by length.

What time zone are dates shown in?

Both your browser's local time zone and UTC are shown side by side, since which one you need depends on the context.

Can this handle dates before 1970?

Yes, Unix time can be negative for dates before the epoch, and this tool handles that correctly.

What is a Unix timestamp?

The number of seconds elapsed since 1 January 1970 UTC. It's a single number with no time zone attached, which is why it's the usual way to store a moment in time.

Why is the epoch 1 January 1970?

It was an arbitrary but convenient starting point chosen for early Unix systems, and it stuck. There's no deeper significance to the date.

What is the year 2038 problem?

Systems that store timestamps in a signed 32-bit integer run out of room in January 2038 and wrap around to a negative number. Modern systems use 64-bit values and aren't affected.

Can I convert a date back into a timestamp?

Yes, conversion works in both directions - enter a date and get the epoch value, or enter the number and get the date.

Updated Jul 31, 2026