Unix Timestamp Converter

Convert Unix timestamps to human-readable dates and vice versa. Shows a live current timestamp.

Unix Timestamp Converter

Current Unix Timestamp (seconds)

1775900742

2026-04-11 09:45:42 UTC

Unix Timestamp

How to Use

Enter a Unix timestamp

Paste a 10-digit (seconds) or 13-digit (milliseconds) timestamp number to convert to a readable date.

View UTC and local time

See the timestamp's equivalent date in both UTC and your device's local timezone.

Convert a date to timestamp

Enter a date and time to get back its Unix timestamp in seconds or milliseconds.

Use the live ticker

See the current Unix timestamp ticking in real time for debugging or quick timestamp capture.

What is a Unix Timestamp?

A Unix timestamp (epoch time) is the number of seconds elapsed since January 1, 1970 00:00:00 UTC. It is a language-agnostic way to store and compare dates and is used ubiquitously in databases, APIs, and programming.

Real-World Examples & Use Cases

API Debugging and Development

REST APIs, JSON responses, and webhook payloads commonly include Unix timestamps in the data fields for event times, expiry dates, and last-modified markers. When debugging API responses in DevTools, Postman, or log viewers, developers need to convert these numeric epoch values to understand whether an event happened recently, whether a token has expired, or whether a timestamp makes logical sense in the flow. Converting 1705238400 to 'January 14, 2024 16:00 UTC' immediately clarifies the timeline.

Database Timestamp Interpretation

Relational databases (MySQL, PostgreSQL) and NoSQL stores (MongoDB, Redis) often store dates as Unix timestamps in integer columns. Database administrators and developers querying logs, analytics data, and event tables encounter epoch timestamps in query results. Translating these to readable dates helps interpret data correctly: was an order placed last week or last year? Did a cache entry expire before or after the incident? PostgreSQL's to_timestamp() function and MySQL's FROM_UNIXTIME() perform server-side conversion, but a browser tool is faster for quick checks.

Authentication Token Expiry Verification

JWT (JSON Web Token) authentication tokens include an 'exp' (expiration) claim as a Unix timestamp. Security engineers and developers debugging authentication errors decode the JWT payload and examine the exp value to determine when the token expires or expired. A 'Token Expired' error that references a numeric timestamp like 1705238000 becomes immediately understandable when converted: 'This token expired 6 hours ago.' Similarly, cookie expiry values, session tokens, and OAuth access token validity periods are often expressed as epoch timestamps.

Log File Analysis and Incident Investigation

Application logs, web server access logs, system audit logs, and security event logs often use Unix timestamps for compact, sortable, language-neutral event timing. During incident investigations, interpreting log entries requires converting timestamps to understand event sequences: what user action happened first, what happened after, and how long elapsed between events. Unix timestamps sort naturally as integers (earlier events = smaller numbers), making them ideal for log storage, but human-unreadable for analysis without conversion.

How It Works

Unix Epoch Time: Definition: Unix timestamp = seconds elapsed since January 1, 1970 00:00:00 UTC (The Unix epoch, or Unix time zero) Common scales: Seconds (most common): 10-digit numbers (e.g. 1705238400) Milliseconds (JavaScript): 13-digit numbers (e.g. 1705238400000) Microseconds: 16-digit numbers (used in high-precision logging) Conversion formulas: Timestamp to Date: new Date(timestamp × 1000) // if in seconds new Date(timestamp) // if in milliseconds .toISOString() → '2024-01-14T16:00:00.000Z' Date to Timestamp: new Date('2024-01-14T16:00:00Z').getTime() / 1000 (seconds) new Date('2024-01-14T16:00:00Z').getTime() (milliseconds) Current timestamp: Math.floor(Date.now() / 1000) // current Unix time in seconds Remarkable dates: Epoch zero: 0 = 1970-01-01 00:00:00 UTC Y2K38 problem: 2,147,483,647 = 2038-01-19 03:14:07 UTC (max value for signed 32-bit integer) Current: ~1.7 billion (Jan 2024)

Frequently Asked Questions

Why do some timestamps have 13 digits instead of 10?▼

10-digit Unix timestamps represent seconds since epoch (e.g. 1705238400). 13-digit timestamps represent milliseconds since epoch (e.g. 1705238400000 = same moment × 1000). JavaScript's Date.now() and Date.getTime() return milliseconds by default, which is why 13-digit timestamps are common in web applications. Many other systems (Unix shell, Python's time.time(), most databases) use seconds. Always check whether a system uses seconds or milliseconds before interpreting timestamps.

What is the Year 2038 problem?▼

Many systems store Unix timestamps as signed 32-bit integers (int32), which have a maximum value of 2,147,483,647. This value corresponds to January 19, 2038 at 03:14:07 UTC — after this moment, signed 32-bit timestamps overflow to a large negative number, potentially causing systems to interpret dates as 1901. Modern systems use 64-bit integers which won't overflow for another ~292 billion years, but legacy embedded systems, databases using 32-bit INT columns, and old C code remain vulnerable to this engineering issue.

Does Unix time account for leap seconds?▼

No. Unix timestamps treat every day as exactly 86,400 seconds. In reality, leap seconds are occasionally added to UTC to keep atomic time synchronized with Earth's rotation — there have been 27 leap seconds since 1972. Unix timestamps repeat the same integer value during a positive leap second (the 86,401st second shows the same timestamp as the 86,400th). This is a known simplification that is acceptable for most applications but relevant for very high-precision time systems.

How do I convert a Unix timestamp in Python and JavaScript?▼

Python: import datetime; datetime.datetime.utcfromtimestamp(1705238400) → datetime(2024, 1, 14, 16, 0). Or datetime.datetime.fromtimestamp(ts) for local time. JavaScript: new Date(1705238400 * 1000).toISOString() for seconds; new Date(1705238400000).toISOString() for milliseconds already in ms. Go: time.Unix(1705238400, 0). Java: Instant.ofEpochSecond(1705238400L).

What timezone is a Unix timestamp in?▼

Unix timestamps are always UTC (Coordinated Universal Time) by definition — they represent seconds since the UTC epoch. When you convert a timestamp to a human-readable date, the timezone offset (positive/negative hours from UTC) is applied to get the local representation. A timestamp has no inherent timezone — it represents the same absolute moment in time worldwide, displayed in different local times depending on where the viewer is located.

Related Tools

Explore other tools in this category.

Age Calculator

Calculate your exact age in years, months, and days based on your date of birth.

Age in Days & Hours

Find exactly how old you are in years, months, weeks, days, hours, and minutes.

Countdown Timer

Set a custom countdown with hours, minutes, and seconds. Pause, resume, and use quick presets.

Timezone Converter

Convert any date and time between world timezones. Includes a live clock mode and multi-zone comparison.

Date Difference Calculator

Find the exact chronological difference in years, months, and days between two historical or future dates.

Days Between Dates

Calculate the total absolute number of days between two dates.