Unix Timestamp Converter
Convert between Unix timestamps and human-readable dates. Supports seconds, milliseconds, microseconds, nanoseconds, timezone selection, and batch processing.
Display Format
What is a Unix Timestamp?
A Unix timestamp represents the number of seconds (or milliseconds) that have elapsed since January 1, 1970, 00:00:00 UTC (the Unix epoch). It provides a universal way to represent a specific point in time, independent of timezones. All conversions in this tool are performed locally in your browser — no data is uploaded to any server.
How to Use This Tool
- View the live Unix timestamp at the top of the page, updating every second.
- Switch between "Timestamp → Date" and "Date → Timestamp" modes.
- Enter a timestamp or date, select the unit and timezone.
- View the results in multiple formats: UTC, local, ISO 8601, and more.
- Use batch mode to convert multiple timestamps at once.
Seconds vs Milliseconds Timestamps
Seconds timestamps are typically 10 digits (e.g., 1704067200), while milliseconds timestamps are 13 digits (e.g., 1704067200000). JavaScript’s Date.now() returns milliseconds. Most APIs and databases use seconds. This tool auto-detects the unit, but you can also select it manually.
Timestamps and Timezones
A Unix timestamp represents a fixed point in time — it does not contain timezone information. The timezone only affects how the date and time are displayed. For example, timestamp 1704067200 is always the same moment, but it shows as 00:00:00 UTC and 08:00:00 in Asia/Shanghai.
⚠ During DST transitions, some local times may not exist or may repeat. The displayed UTC offset helps you verify the correct time.
The Year 2038 Problem
Systems using 32-bit signed integers for timestamps will overflow on January 19, 2038 (timestamp 2147483647). After this date, the timestamp wraps to a negative number, causing dates to appear as 1901. Modern systems using 64-bit integers or JavaScript’s Number type are not affected.
Get Timestamp in Code
Math.floor(Date.now() / 1000)
import time int(time.time())
time();
System.currentTimeMillis() / 1000
time.Now().Unix()
new DateTimeOffset(DateTime.UtcNow).ToUnixTimeSeconds()
Time.now.to_i
Limitations
- This tool runs entirely in your browser; no data is sent to any server.
- Nanosecond timestamps (19 digits) may lose precision in JavaScript due to Number limitations.
- Some timezones may have ambiguous times during DST transitions.
- Very large timestamps may exceed JavaScript’s safe integer range.
Frequently Asked Questions
What is a Unix timestamp?
A Unix timestamp is the number of seconds (or milliseconds) since January 1, 1970, 00:00:00 UTC. It provides a universal way to represent time.
How do I know if my timestamp is in seconds or milliseconds?
Seconds timestamps are ~10 digits, milliseconds are ~13 digits. This tool auto-detects, but you can also select the unit manually.
Does the timestamp include timezone information?
No. A Unix timestamp represents a fixed moment in time. Timezone only affects how the date and time are displayed.
What is the Year 2038 problem?
32-bit systems will overflow on January 19, 2038. Modern 64-bit systems and JavaScript are not affected.
Can I convert negative timestamps?
Yes. Negative timestamps represent dates before January 1, 1970 (the Unix epoch).
Why do different browsers show different results?
This tool uses strict parsing to avoid browser-dependent behavior. Results should be consistent across browsers.
How do I handle DST transitions?
During DST changes, some local times may not exist or may repeat. Check the UTC offset to verify the correct time.
Is my data saved?
No. All conversions happen locally in your browser. History is stored only in your browser’s local storage.