Unix Timestamp Converter

Unix timestamp is the number of seconds (or milliseconds) since 1 January 1970 00:00:00 UTC (the Unix epoch).

Convert 15 January 2025 12:00:00 UTC to Unix timestamp:

1. Epoch: 1 January 1970 00:00:00 UTC
2. Difference: 55 years, 14 days, 12 hours
3. Total seconds: approximately 1,736,942,400

Result: 1736942400 (seconds) or 1736942400000 (milliseconds)

Convert timestamp 1736942400 to date:

1. Add 1,736,942,400 seconds to 1 January 1970
2. Result: 15 January 2025 12:00:00 UTC

1. Enter a date and time, or enter a Unix timestamp
2. Click "Convert" to see the conversion

| Date | Unix Timestamp (seconds) | |------|--------------------------| | 1 Jan 2000 | 946684800 | | 1 Jan 2010 | 1262304000 | | 1 Jan 2020 | 1577836800 | | 1 Jan 2025 | 1735689600 | | 1 Jan 2030 | 1893456000 | | 19 Jan 2038 | 2147483647 (32-bit overflow) |

Unix timestamps can be expressed in:

• Seconds: Standard Unix timestamp (10 digits)
• Milliseconds: Timestamp × 1000 (13 digits)
• Nanoseconds: Timestamp × 1,000,000,000 (19 digits)

Unix timestamps are always in UTC. When converting to local time, apply your time zone offset.

• Database timestamps
• API request/response times
• System logging
• File modification times
• Performance measurements

What is the 2038 problem? 32-bit systems will overflow on 19 January 2038 when the timestamp exceeds 2,147,483,647 seconds.

Can I have negative timestamps? Yes, timestamps before 1 January 1970 are negative.

Is the timestamp unique? Yes, each second has a unique Unix timestamp (ignoring leap seconds).

How do I convert in JavaScript? Use Date.now() for milliseconds, Math.floor(Date.now() / 1000) for seconds.

What about leap seconds? Unix timestamps ignore leap seconds, so they are not perfectly accurate for scientific timekeeping.