Unix Timestamp Converter
Convert Unix epoch timestamps to human readable dates and back, for developers and debugging. No signup. Ideal for logs, APIs, databases and working with time data.
Result
Share on Social Media:
A Unix timestamp is a single number — the seconds since 1 January 1970 — and this converter turns it into a readable date and back again, free, with no account. Paste a timestamp to see its UTC, local and ISO 8601 date, or pick a date to get its timestamp in seconds and milliseconds. Everything runs in your browser: nothing is uploaded or stored.
On this page
- How to Convert a Unix Timestamp Step by Step
- What a Unix Timestamp Is and Why It Exists
- Unix Time Versus Human Readable Dates
- Who Uses a Unix Timestamp Converter
- Pro Tips for Working With Unix Time
- Common Unix Timestamp Mistakes to Avoid
- Related Tools You May Need Next
- Frequently Asked Questions
How to Convert a Unix Timestamp Step by Step
- To turn a timestamp into a date: type the timestamp in seconds into the "Unix timestamp (seconds)" box and click "Timestamp → Date". The tool shows the same instant three ways: UTC, your local time, and ISO 8601.
- To turn a date into a timestamp: pick the date and time in the "Date & time" field and click "Date → Timestamp". The tool shows the Unix timestamp in seconds and the same instant in milliseconds.
- There is no direction switch to set. The button you click chooses the direction — one button converts timestamp to date, the other converts date to timestamp.
- Check the time zone. The UTC and ISO rows are the same for everyone, everywhere. The Local row shows the instant in your own time zone, so it can be a different hour — or even a different date — from the UTC row.
- Use the result. Copy the value into your log search, API call, database query or code, having translated between the machine number and the human date.

What a Unix Timestamp Is and Why It Exists
A Unix timestamp, also called epoch time, is a way of representing a moment in time as a single number: the count of seconds that have elapsed since a fixed reference point, the first of January 1970 at 00:00:00 in coordinated universal time. That reference moment is called the Unix epoch. So a timestamp is simply how many seconds have passed since that instant, and each number identifies one moment and one moment only.
The reason this representation exists is that a single number is far easier for computers to store, compare and calculate with than a human date made of years, months, days, hours, minutes and seconds. Comparing two timestamps is just comparing two numbers, and finding the time between them is a subtraction. That simplicity is why Unix time is used pervasively in programming, in logs, databases, APIs and file systems, as the machine-friendly way to record when something happened.
Worked example — enter 1735689600 and click "Timestamp → Date":
| Row | Value |
|---|---|
| UTC | Wed, 01 Jan 2025 00:00:00 GMT |
| Local | The same instant in your time zone (06:00 in Asia/Dhaka, 00:00 in UTC) |
| ISO 8601 | 2025-01-01T00:00:00.000Z |
The other direction works the same way. Pick 1 January 2025 at 00:00 in a browser set to UTC and click "Date → Timestamp" to get 1735689600 seconds and 1735689600000 milliseconds. The same wall-clock entry in a browser set to Asia/Dhaka gives 1735668000, because the date picker reads the date as local time — a useful reminder that a timestamp is absolute but a wall-clock reading is not.
Two edge cases worth knowing: 0 is the epoch itself, 1 January 1970 at 00:00:00 UTC, and negative timestamps work too — -1 is 31 December 1969 at 23:59:59 UTC, one second before the epoch.
Seconds, not milliseconds: this tool only accepts seconds. A 13-digit millisecond value such as 1735689600000 is treated as seconds and lands in the year 56971. If your value has 13 digits, drop the last three before converting.
Unix Time Versus Human Readable Dates
| Aspect | Unix timestamp | Human date | ISO 8601 |
|---|---|---|---|
| Form | A single number of seconds | Year, month, day, hour, minute, second | Text such as 2025-01-01T00:00:00.000Z |
| Readable at a glance | No — 1735689600 means nothing to the eye | Yes | Yes, once you know the format |
| Time zone | Absolute — the same instant everywhere | Depends on the zone it is shown in | Ends in Z for UTC, unambiguous |
| Comparing two moments | Compare two numbers | Compare six fields, with month and day lengths to handle | Sorts as plain text |
| Best for | Storing and calculating in code | Showing to people | Pasting into code, JSON and APIs |
The milliseconds row bridges the two worlds: JavaScript's Date works in milliseconds, so the same instant that is 1735689600 seconds is 1735689600000 milliseconds. If you are working in JavaScript, take the milliseconds row; if you are working in a database, a log file or a Unix command, take the seconds row.
Who Uses a Unix Timestamp Converter
Developers debugging logs and APIs. A developer sees 1735689600 in a log line or an API response and converts it to find out exactly when the event happened, in their own time zone as well as UTC.
Data engineers working with epoch columns. An engineer whose database stores times as epoch seconds converts values to check date ranges, spot bad rows, and write queries against human dates.
QA testers reproducing time bugs. A tester converts a reported timestamp to a date to reproduce a time-dependent bug, or converts a chosen date to a timestamp to feed into a test case.
Support staff reading timestamps in tickets. Support reads the epoch value attached to a customer's report and converts it to a readable date to understand when the problem actually occurred.
Students learning how computers store time. A student converts dates back and forth to build an intuition for epoch time, the most common way computers record when something happened.
Pro Tips for Working With Unix Time
Count the digits first. Ten digits means seconds, thirteen means milliseconds. This tool takes seconds only, so drop the last three digits of a 13-digit value before pasting it in.
Compare using the UTC row. When you share a time with someone in another time zone, quote the UTC or ISO row. The Local row is correct for you and wrong for them.
Use the ISO row in code and JSON. 2025-01-01T00:00:00.000Z is unambiguous, sorts as text, and is accepted by almost every date parser — safer than a locale-formatted string.
Remember the date picker is local time and minute-precision. It has no seconds field and no time-zone setting, so the timestamp you get is for that wall-clock time in your zone, rounded to the minute.
Use the milliseconds row for JavaScript. JavaScript Date works in milliseconds, so 1735689600000 is the value to pass to new Date() — the seconds value would land in January 1970.
Subtract to find a gap. The difference between two timestamps is the gap in seconds: 86400 is one day, 3600 is one hour, 60 is one minute.
Common Unix Timestamp Mistakes to Avoid
Pasting milliseconds as seconds. A 13-digit value is treated as seconds and produces a year in the tens of thousands. Check the digit count before you convert.
Reading the Local row as UTC. The Local row is your time zone's rendering of the instant. If you need the universal time, read the UTC or ISO row.
Assuming the date picker is UTC. The picker reads your date as local time. The same wall-clock entry gives a different timestamp in Dhaka than it does in London — that is correct behaviour, not a bug.
Typing a decimal and expecting the fraction to survive. The tool reads the input as a whole number, so 1735689600.5 becomes 1735689600. Fractions of a second are dropped, not rounded.
Looking for a direction switch or a "now" button. There is neither. The direction is the button you click, and there is no button that fills in the current time — type today's timestamp yourself or use the date picker.
Forgetting there are no copy buttons. The result rows are plain text. Select the value you need and copy it by hand rather than hunting for a copy icon that is not there.
Related Tools You May Need Next
Date Difference Calculator. Find the gap between two dates.
Time Converter. Convert between hours, minutes, days and other time units.
Timezone Converter. Move a time between zones.
Countdown Timer. Count down to a moment.
Number Generator. Generate random numbers for testing.

Frequently Asked Questions
What is a Unix timestamp?
A Unix timestamp is the number of seconds since 1 January 1970 at 00:00:00 UTC, the Unix epoch. Each number identifies one moment in time, and the count grows by one every second.
How do I convert a Unix timestamp to a date?
Type the timestamp in seconds into the "Unix timestamp (seconds)" box and click "Timestamp → Date". You get three rows: UTC, your local time, and ISO 8601. For example, 1735689600 is 1 January 2025 at 00:00:00 UTC.
How do I convert a date to a Unix timestamp?
Pick the date and time in the "Date & time" field and click "Date → Timestamp". The tool shows the timestamp in seconds and the same instant in milliseconds. Note the picker reads the date as your local time, and it has minute precision only.
What is the difference between the UTC, Local and ISO rows?
All three describe the same instant. UTC is the universal time, Local is that instant shown in your time zone, and ISO 8601 is the standard text form (2025-01-01T00:00:00.000Z) used in code and data. The instant never changes — only its display does.
Is 1735689600 a date I can check?
Yes — it is 1 January 2025 at 00:00:00 UTC, which is 06:00 the same morning in Bangladesh. It is the placeholder shown in the timestamp box, and a good test value.
Can I convert a millisecond timestamp?
Not directly. This tool treats every input as seconds, so a 13-digit millisecond value gives a date tens of thousands of years in the future. Drop the last three digits first, then convert the remaining 10-digit seconds value.
What does the milliseconds row mean?
It is the same instant expressed in milliseconds instead of seconds — 1735689600 seconds is 1735689600000 milliseconds. JavaScript's Date works in milliseconds, so use that row when you are writing JavaScript.
Can I convert a date before 1970?
Yes. Negative timestamps work: -1 is 31 December 1969 at 23:59:59 UTC, one second before the epoch. Enter the negative number the same way as any other timestamp.
Why does the same timestamp show a different local time for different people?
Because a timestamp is one absolute instant, and each time zone displays that instant on its own clock. 1735689600 is midnight in London and 06:00 in Dhaka — the same moment, shown differently. The UTC row is the one everyone shares.
Is the Unix timestamp converter free?
Yes, it is completely free with no account and no usage limit. It runs entirely in your browser, so your timestamps and dates are never uploaded or stored.