Unix Timestamp Converter
Turn epoch timestamps from logs, databases, APIs and JWTs into readable dates in UTC, your local time or any timezone, convert a date back to Unix seconds or milliseconds, and convert a whole column of timestamps at once. Seconds, milliseconds, microseconds and nanoseconds are detected automatically.
Private by design: anything you enter is processed in your browser only. It is never uploaded to or logged on our servers. Conversions use your device's clock and timezone database.
Current Unix Time
Updates live from your device clock
Timestamp → Date
Date → Timestamp
Batch Convert
One timestamp per line. Units are auto-detected per line.
About Unix timestamps
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. Because it is a single number with no timezone attached, it is the most common way for databases, log files, APIs and programming languages to store a moment in time. Negative values represent dates before 1970.
Different systems use different precisions. Classic Unix tools and most APIs use seconds (10 digits today), JavaScript's Date.now() and Java use milliseconds (13 digits), while Python's time.time_ns(), Go and many tracing systems use microseconds (16 digits) or nanoseconds (19 digits). This converter detects the unit from the size of the number; switch the unit selector if you are working with very old or far-future values where the guess could be ambiguous.
The results show the same instant in UTC, your local timezone and any IANA timezone you pick, along with ISO 8601 and RFC 2822 strings that can be pasted straight into code, HTTP headers or emails. The ISO week number follows ISO 8601: weeks start on Monday and week 1 is the week containing the first Thursday of the year.
A well-known limit is the Year 2038 problem: signed 32-bit integers overflow at 2147483647 (19 January 2038, 03:14:07 UTC). Modern systems store timestamps as 64-bit integers to avoid it. All conversions here run entirely in your browser — nothing is sent to a server.
Related tools: the exp, iat and nbf claims in a JSON Web Token are Unix timestamps in seconds, and the JWT decoder shows them alongside the rest of the token. To add days or count business days between two dates, use the date calculator, and to work out when a scheduled job will next run, use the cron expression builder.
Reference Guide
Get the current Unix time in seconds:
| Language | Code |
|---|---|
| JavaScript | Math.floor(Date.now() / 1000) (Date.now() alone is milliseconds) |
| Python | int(time.time()) |
| PHP | time() |
| Go | time.Now().Unix() |
| Java | Instant.now().getEpochSecond() |
| C# | DateTimeOffset.UtcNow.ToUnixTimeSeconds() |
| Ruby | Time.now.to_i |
| Bash | date +%s |
| MySQL | SELECT UNIX_TIMESTAMP(); |
| PostgreSQL | SELECT EXTRACT(EPOCH FROM now()); (includes fractional seconds) |
| SQLite | SELECT strftime('%s', 'now'); |
Convert a timestamp back to a date:
| Language | Code |
|---|---|
| JavaScript | new Date(1700000000 * 1000).toISOString() |
| Python | datetime.fromtimestamp(1700000000, tz=timezone.utc) |
| PHP | gmdate('c', 1700000000) |
| Go | time.Unix(1700000000, 0).UTC() |
| Java | Instant.ofEpochSecond(1700000000) |
| Bash (GNU / Linux) | date -u -d @1700000000 |
| Bash (macOS / BSD) | date -u -r 1700000000 |
| MySQL | SELECT FROM_UNIXTIME(1700000000); (in the session time zone) |
| PostgreSQL | SELECT to_timestamp(1700000000); |
| SQLite | SELECT datetime(1700000000, 'unixepoch'); |
Guess the unit from the number of digits (for dates between 2001 and 2286):
| Digits | Unit | Example for 2023-11-14T22:13:20Z | Typical source |
|---|---|---|---|
| 10 | Seconds | 1700000000 | Unix tools, PHP, most REST APIs, JWT claims |
| 13 | Milliseconds | 1700000000000 | JavaScript Date.now(), Java System.currentTimeMillis() |
| 16 | Microseconds | 1700000000000000 | BigQuery UNIX_MICROS(), Zipkin span timestamps |
| 19 | Nanoseconds | 1700000000000000000 | Go UnixNano(), Python time.time_ns() |
Notable timestamps:
| Timestamp | UTC date | Why it matters |
|---|---|---|
0 | 1970-01-01T00:00:00Z | The Unix epoch |
1000000000 | 2001-09-09T01:46:40Z | First 10-digit timestamp |
1234567890 | 2009-02-13T23:31:30Z | Celebrated by developers worldwide |
2000000000 | 2033-05-18T03:33:20Z | Next round billion |
2147483647 | 2038-01-19T03:14:07Z | 231−1, the largest signed 32-bit value (Year 2038 problem) |
-2147483648 | 1901-12-13T20:45:52Z | Smallest signed 32-bit value |
4294967295 | 2106-02-07T06:28:15Z | 232−1, the limit for unsigned 32-bit timestamps |
Example input
1700000000 → 2023-11-14T22:13:20.000Z (Tuesday) Batch: 0 1000000000 1700000000 1700000000123 2147483647
This sample loads automatically when you open the tool. Use Load Sample to bring it back.
Frequently Asked Questions
A Unix timestamp (epoch time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is a time-zone-independent way to store a moment in time.
Current timestamps in seconds have 10 digits, while milliseconds have 13 digits (microseconds 16, nanoseconds 19). The converter detects the unit automatically from the length.
Systems that store Unix time as a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. Modern systems use 64-bit integers, which push the limit billions of years into the future.
Related Tools
All Text Processing Tools →URL Encoder & Decoder Online
Encode and decode URLs online. Convert special characters to...
Text Case Converter Online
Convert text between UPPERCASE, lowercase, Title Case, camel...
Lorem Ipsum Generator
Generate Lorem Ipsum placeholder text for designs and mockup...
PDF Password Setter
Add password protection to your PDF files for secure sharing...
Remove PDF Password
Unlock a password-protected PDF when you know the current pa...
OCR PDF
Convert scanned PDFs into searchable documents using OCR tex...