How it works
- 1
Paste a Unix timestamp
Enter a Unix timestamp in seconds (e.g. 1735689600) or milliseconds (e.g. 1735689600000) — auto-detected. Select a timezone for the local output.
- 2
Or convert a date to a timestamp
Switch to the 'Date → Timestamp' tab. Enter any ISO 8601, RFC 2822, or natural date string and get back the Unix seconds and milliseconds.
- 3
View the live current timestamp
The 'Now' tab shows a live ticker of the current Unix timestamp in seconds and milliseconds — useful for quick copying.
Notable timestamps
🛡️ Verify zero uploads — open DevTools → Network tab
Open your browser's DevTools (F12), go to the Network tab, and use this tool. You will see zero outbound requests — all processing runs inside your browser sandbox via WebAssembly or pure JavaScript. Nothing you paste or upload is ever sent anywhere.
Use cases
Debugging API responses
APIs return timestamps as Unix integers. Paste the value here to instantly see the human-readable date — no mental math required.
Working with database records
Check when a record was created by converting the stored timestamp, or convert a target date to a timestamp for WHERE clause comparisons.
Cross-timezone date handling
See exactly what a UTC timestamp looks like in any timezone — useful when debugging events that span multiple regions.
Frequently Asked Questions
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'). It is a timezone-independent way to represent a specific moment in time, used universally in databases, APIs, and programming languages.
How do I know if a timestamp is in seconds or milliseconds?
A 10-digit number is almost certainly seconds (e.g. 1735689600 = Jan 1, 2025). A 13-digit number is milliseconds (e.g. 1735689600000). This tool auto-detects the unit based on the magnitude of the input.
What is the Y2K38 problem?
On January 19, 2038 at 03:14:07 UTC, 32-bit signed integers (max value 2,147,483,647) will overflow when used to store Unix timestamps. Systems using int32 for timestamps will break. Modern systems use int64 or int64-equivalent types, which won't overflow for ~292 billion years.
How do I get the current Unix timestamp in JavaScript?
Use Math.floor(Date.now() / 1000) for seconds, or Date.now() for milliseconds. The Code Snippets tab has copy-paste examples for JavaScript, Python, Go, Rust, and SQL.
Want unlimited access + saved history?
Pro is $6/month · 30-day money-back guarantee.