Time Converter
Unix timestamps are the standard way computers represent time — the number of seconds or milliseconds since January 1, 1970 00:00:00 UTC. Whether you're reading server logs, debugging API responses, or querying database time fields, you encounter this format constantly. This tool converts between timestamps and readable dates instantly.
Supports second-level (10-digit) and millisecond-level (13-digit) timestamps with automatic format detection. Two-way conversion — timestamp to date and date to timestamp — on a single screen. Double-click any result to copy.
Timestamp → Date
Date → Timestamp
📖 Timestamp Converter Guide
What Is a Unix Timestamp?
A Unix timestamp is the number of seconds (or milliseconds) elapsed since January 1, 1970 00:00:00 UTC — the Unix Epoch. This epoch was chosen because Unix originated in that era. Timestamps are cross-platform and language-agnostic: the same integer represents the same exact moment whether you're in Go, Python, JavaScript, or a database. That's why they're the backbone of server logs, API signatures, database time columns, and caching systems.Seconds vs Milliseconds
- Second-level (10 digits): Precise to the second, e.g. 1715678901. Used by traditional Unix systems and most backend languages (Go time.Unix, Python time.time()). The most common format in server logs and databases.
- Millisecond-level (13 digits): Precise to the millisecond, e.g. 1715678901000. Used by JavaScript Date.now() and browser APIs. It is the second-level value × 1000.
- Quick identification: 10 digits ≈ seconds (years ~2001-2286). 13 digits ≈ milliseconds (years ~2001-2286). Values above 10^12 are likely microsecond or nanosecond — divide by 1000 before using.
How to Use
- Timestamp → Date: Paste a 10 or 13-digit timestamp — the tool auto-detects the format and converts it to a readable date in ISO 8601, RFC 2822, and custom formats. Double-click any result to copy.
- Date → Timestamp: Fill in year/month/day/hour/minute/second fields. Second and millisecond timestamps are generated in real time. Click "Now" to fill the current system time.
- "Now" button: Both panels have one — the left fills the current millisecond timestamp, the right fills the current date/time fields.
Real-World Examples
- Incident response: Your ops teammate says "we had a traffic spike yesterday at 3pm." You convert 2026-05-12 15:00:00 to a timestamp, then filter your log platform by timestamp range — isolating the exact few minutes that matter.
- JWT token inspection: JWT exp claims are often second-level timestamps. Paste exp: 1747180800 into the tool to instantly see when the token expires — no mental math required.
- Database exports for non-engineering teams: Your database stores create_time as 1715678901, but your operations team needs human-readable dates. Convert to 2024-05-14 10:35:01 before exporting the report.
Common Pitfalls
- Year 2038 Problem: 32-bit signed integers max out at 2,147,483,647 seconds — January 19, 2038 03:14:07 UTC. After that, overflow occurs. 64-bit systems have eliminated this, and all modern servers/browsers are safe.
- Timezone confusion: Unix timestamps are timezone-agnostic — the same timestamp means the same moment in Beijing, New York, and London. Converted dates use your local timezone by default. If your team uses UTC, account for the offset.
- Second vs millisecond mix-up: Feeding a millisecond timestamp as seconds gives you a date in the year 50000+. If the year looks absurd, check the unit.
- Invalid dates: February 30 or April 31 will not produce a valid timestamp. The tool ignores invalid inputs.
Command-Line Alternatives
# Current timestamp (seconds)
date +%s
# Current timestamp (milliseconds)
date +%s%3N
# Timestamp to date
date -r 1715678901 "+%Y-%m-%d %H:%M:%S"
# Python one-liner
python3 -c "import time; print(time.time())"
# JavaScript (browser console)
Math.floor(Date.now() / 1000) // seconds
Date.now() // milliseconds