Free Online Unix Timestamp Converter
Translate Unix timestamps to readable dates and back
Try these next
Why use Unix Timestamp Converter
- Bidirectional -- paste a timestamp to get a date, or pick a date to get a timestamp, in a single interface.
- Full IANA timezone support lets you see what a UTC timestamp means in Tokyo, London, New York, or anywhere else.
- Auto-detects 13-digit millisecond timestamps (the format JavaScript and most modern APIs return) and handles them correctly.
- Live clock shows the current epoch so you can grab a precise 'now' value with one click.
- Uses the same Intl.DateTimeFormat API your production code uses, so the output is consistent with what JavaScript produces.
How it works
Unix timestamps represent time as an integer count of seconds elapsed since the Unix epoch: January 1, 1970, at 00:00:00 UTC. The converter uses JavaScript's Date object, which internally stores time as milliseconds since epoch. To convert a timestamp to a date, the tool multiplies seconds by 1000 to get milliseconds, constructs a Date, then formats it using the Intl.DateTimeFormat API with the selected IANA timezone identifier. For date-to-timestamp conversion, the Date is constructed from the picker values in the selected timezone, and getTime() returns the millisecond count, which is divided by 1000 and floored to produce the integer seconds value. The live clock calls Date.now() on a one-second setInterval, divides by 1000, and floors the result to display the continuously incrementing current timestamp.
About this tool
Unix timestamps are everywhere -- server logs, JWT expiry fields, database columns, analytics payloads, cron configs -- but 1713043200 doesn't mean anything to a human at a glance. Paste a timestamp here and get the date in your chosen timezone. Pick a date and copy the integer. A live clock updates every second so you can grab the current epoch with one click. The converter supports all IANA timezones and auto-detects 13-digit inputs as millisecond timestamps (the format Date.now() and most REST APIs return), dividing by 1,000 transparently. Internally it uses JavaScript's Date object and the Intl.DateTimeFormat API with your selected timezone identifier, so the output is byte-for-byte what your Node.js or browser code would produce. This is faster than running `date -d @1713043200` in a terminal, and it handles timezone math without the mental overhead of UTC offsets.
How to use Unix Timestamp Converter
- Paste a timestamp. Drop a 10-digit (seconds) or 13-digit (milliseconds) Unix timestamp into the input. The corresponding date appears below.
- Or pick a date. Use the date and time pickers to select a moment. The corresponding Unix timestamp populates the output field.
- Set the timezone. Switch the timezone dropdown to see the same moment in any IANA timezone. The underlying epoch value stays the same.
- Grab 'now'. Click Now to load the current timestamp. The live clock updates every second, so you can copy a precise value any time.
- Copy the result. Click the copy icon next to the timestamp or the formatted date to put it on your clipboard.
Use cases
- You're debugging a production incident and the server logs are full of raw epoch timestamps. Paste one here, map it to a UTC time, correlate it with the deploy timeline.
- A CSV export from an analytics platform has a column of 13-digit millisecond timestamps. Confirm the date range before importing into your BI dashboard.
- You need the Unix timestamp for exactly midnight UTC on January 1 to hardcode a cron job's start date. Pick the date, copy the integer.
- A push notification was supposed to fire at 9 AM Tokyo time. Paste the scheduled_at value from the API response and check whether the timezone math is right.
- The JWT your identity provider issues has an exp claim that looks wrong. Paste the value here, see the date, and decide if the token lifetime is what you configured.
- You're writing a migration script and need timestamps for the first day of each quarter. Pick dates, copy epoch values, paste them into your seed file.
Frequently Asked Questions
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970, at 00:00:00 UTC. For example, the timestamp 1700000000 represents November 14, 2023, at 10:13:20 PM UTC. Unix timestamps are used extensively in programming, databases, and APIs because they are timezone-independent and easy to compare mathematically.
The standard Unix timestamp is in seconds. However, many programming languages and APIs use milliseconds (JavaScript's Date.now() returns milliseconds, for example). This tool works with seconds by default and shows the millisecond equivalent below. If you paste a 13-digit number, it is likely in milliseconds -divide by 1000 to get seconds.
Systems that store Unix timestamps as 32-bit signed integers will overflow on January 19, 2038, at 03:14:07 UTC (timestamp 2147483647). After this point, the timestamp wraps to a negative number, which would be interpreted as a date in 1901. Most modern systems use 64-bit integers, which won't overflow for 292 billion years. This tool handles timestamps beyond 2038 correctly.
They don't. Unix timestamps are always in UTC -they represent an absolute point in time regardless of timezone. The timezone only affects how the timestamp is displayed as a human-readable date. Timestamp 1700000000 is the same moment everywhere in the world; it just looks different when formatted in Eastern Time vs Tokyo Time.
Enter a date using the date picker on this page and the corresponding Unix timestamp appears instantly. Programmatically: in JavaScript, use Math.floor(new Date('2024-01-01').getTime() / 1000). In Python, use int(datetime(2024, 1, 1).timestamp()). In Bash, use date -d '2024-01-01' +%s.
In JavaScript: Math.floor(Date.now() / 1000). In Python: import time; int(time.time()). In Bash: date +%s. In PHP: time(). In SQL (PostgreSQL): EXTRACT(EPOCH FROM now())::int. All return the current time as seconds since January 1, 1970 UTC.
A standard Unix timestamp is 10 digits (seconds since epoch). A millisecond timestamp is 13 digits -JavaScript's Date.now() and many modern APIs return milliseconds. If you paste a 13-digit number, divide by 1000 to get the second-based timestamp. The converter detects 13-digit inputs automatically and treats them as milliseconds.
On systems using a 32-bit signed integer for timestamps, the maximum is January 19, 2038 (timestamp 2,147,483,647). Modern systems use 64-bit integers, which support dates up to approximately 292 billion years in the future. This tool uses JavaScript's Date object, which supports timestamps from roughly 271,821 BCE to 275,760 CE.
Related Tools
Discover more free utilities to enhance your productivity.