Unix Timestamp Converter
Convert Unix epoch seconds into a UTC and local date, or a date into a timestamp, with reference values for 2026 and a note on seconds versus milliseconds.
Results
UTC date
- Local string
- Tue Sep 08 2026 16:00:00 GMT+0000 (Coordinated Universal Time)
You might also need
Educational estimates · not financial advice · free, no signup
Formula / how it works
Date = 1970-01-01T00:00:00Z + timestamp seconds. Timestamp = seconds between the date and the epoch. One day is 86,400 seconds; one hour is 3,600.
Detailed guide
What it is, how to use it, how to read the numbers, common mistakes, a worked example, formulas, and FAQs.
What this calculator is
Unix time counts seconds since the epoch, 1 January 1970 at 00:00:00 UTC. It shows up in server logs, APIs, JWT tokens, file metadata and databases. This tool converts both ways: a timestamp in seconds into a UTC date and your local time, or a date into its timestamp. Always check units. A ten-digit number is seconds; a thirteen-digit number is milliseconds and must be divided by 1,000 first. The UTC value is unambiguous, whereas the local string depends on your device's time zone, so two people can see different local times for the same timestamp.
When to use / who it helps
- You see a number in a log and want to know the date.
- You need a timestamp for an API parameter.
- You are checking expiry times in tokens.
- You are comparing times across systems in different time zones.
- You are debugging date bugs.
How to use
Steps
- Choose the mode: timestamp to date, or date to timestamp.
- Enter the timestamp in seconds, or choose the date.
- Read the UTC result.
- Read the local string for your time zone.
- If your number has 13 digits, divide by 1,000.
- Use the UTC form when sharing times with others.
How to interpret results
- The UTC time is the reference.
- The local time depends on your device's setting.
- Ten digits means seconds; thirteen means milliseconds.
- Adding 86,400 moves forward one day.
- Negative values are dates before 1970.
Common mistakes & gotchas
- Entering milliseconds as seconds.
- Reading the local time as UTC.
- Forgetting daylight saving shifts for local time.
- Using a two-digit-year date format.
- Assuming a date at midnight is the same instant in all zones.
Worked example
Worked example — reference timestamps
- 1,767,225,600 is 2026-01-01T00:00:00Z.
- 1,788,883,200 is 2026-09-08T16:00:00Z, which is 8 September 2026 at 21:30 in India Standard Time (UTC+5:30).
- 1,800,000,000 is 2027-01-15T08:00:00Z.
- Check: 1,800,000,000 − 1,767,225,600 = 32,774,400 seconds, which is 379.33 days.
Result: 1,767,225,600 is 1 January 2026 00:00 UTC.
To load the form's own demo values, tap Try example above the Calculate button.
How to calculate / formula
Date = 1970-01-01T00:00:00Z + timestamp seconds. Timestamp = seconds between the date and the epoch. One day is 86,400 seconds; one hour is 3,600.
Frequently asked questions
What is the Unix epoch?
1 January 1970 at 00:00:00 UTC.
How do I know if it is seconds or milliseconds?
Ten digits is seconds; thirteen is milliseconds.
Why is the local time different from UTC?
Your device applies your time zone offset.
Does Unix time include leap seconds?
No.
What is 86,400?
The number of seconds in a day.
What is the 2038 problem?
Signed 32-bit timestamps overflow on 19 January 2038.