Unix Timestamp Converter
Convert between Unix timestamps and human dates in every format and timezone. Live clock, batch convert, date arithmetic, relative time, ISO, RFC, custom formats. 100% private.
Recent conversions
How to Use the Unix Timestamp Converter
- Pick a mode — Timestamp → Date, Date → Timestamp, Date Arithmetic or Batch Convert.
- Choose a timezone — every IANA timezone is supported (Asia/Karachi, America/New_York, Europe/London, UTC and more).
- Enter your value — paste a timestamp (seconds, ms, μs or ns auto-detected) or any human date string.
- Get instant results — ISO 8601, RFC 2822, UTC, local, custom format, relative time, day of week, quarter, week number and more.
- Do date math — add/subtract years, months, weeks, days, hours, minutes or seconds. Compute differences between any two dates.
- Batch convert — paste a list of timestamps and download all conversions as CSV.
- Copy any field — every result has a 📋 button. History and Share link work too.
What is a Unix Timestamp?
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It's the universal language databases, APIs, log files and programming languages use to represent moments in time — exact, unambiguous and timezone-free.
Our converter handles every common unit you'll encounter: seconds (the standard), milliseconds (JavaScript's Date.now()), microseconds (Python's time.time_ns()/1000) and nanoseconds (Go, Rust and modern observability systems). It auto-detects which unit you pasted, converts in every IANA timezone, supports custom YYYY-MM-DD HH:mm:ss-style format tokens, and updates a live clock so you always have now ready to copy.
Common Use Cases
UNIX_TIMESTAMP(), EXTRACT(EPOCH FROM ...) values to human dates.exp, OAuth, AWS signatures).Why Choose Our Timestamp Converter
Frequently Asked Questions
What is the Unix epoch?
The Unix epoch is the instant 00:00:00 UTC on 1 January 1970. A Unix timestamp is the number of seconds since that moment (not counting leap seconds). It's the de facto standard for representing time in computing.
Why are some timestamps 10 digits and others 13?
10-digit timestamps are in seconds (the original Unix standard). 13-digit timestamps are in milliseconds — the format JavaScript's Date.now() and many modern APIs use. We auto-detect which you pasted, but you can also force a unit explicitly.
What format tokens does the custom format support?
YYYY (year), MM (month 01-12), MMM (Jan), MMMM (January), DD (day), dddd (Monday), HH (24-hour), hh (12-hour), mm (minute), ss (second), SSS (millisecond), A (AM/PM), Z (timezone offset). Example: dddd, MMMM D, YYYY h:mm A → "Friday, January 15, 2026 10:30 AM".
How does the timezone work?
We use the browser's native Intl.DateTimeFormat with the IANA timezone you pick, so DST transitions, historical timezone changes and offsets are handled correctly. Unix timestamps themselves are timezone-free — the chosen zone only affects how dates are displayed.
What's the Excel serial date?
Microsoft Excel and Google Sheets represent dates as the number of days since 30 December 1899 (with the famous 1900 leap year bug). We compute the equivalent Excel serial so you can paste it directly into a spreadsheet cell formatted as a date.
Can it handle dates before 1970?
Yes — Unix timestamps for dates before the epoch are negative numbers (e.g. -2208988800 is 1 January 1900 UTC). Our converter handles those correctly.
What's the Year 2038 problem?
32-bit signed Unix timestamps overflow at 03:14:07 UTC on 19 January 2038 (the "Y2K38" bug). Our converter uses JavaScript's 64-bit numbers, so it handles dates well beyond 2038 — but if you're working with a legacy 32-bit system, that's its cutoff.
Which other tools pair well with this?
Try our JSON Formatter (decode timestamps in API responses), Text Diff Checker, Age Calculator and SQL Formatter.