Epoch Time Converter
Convert a Unix timestamp to a readable date, or a date to epoch time. Seconds, milliseconds, microseconds and nanoseconds are detected for you.
JavaScript needed for live conversion. The results below show a static example for 1735689600.
Detected: seconds
Accepts ISO 8601 (2025-01-01T00:00:00Z), RFC 2822, “YYYY-MM-DD HH:mm:ss” in the selected zone, or “now”.
- UTC
- 2025-01-01T00:00:00Z
- Local time (UTC)
- Wednesday, January 1, 2025 at 12:00:00 AM UTC
- ISO 8601
- 2025-01-01T00:00:00Z
- RFC 2822
- Wed, 01 Jan 2025 00:00:00 +0000
- Relative
- 2 years ago
- Day of year · ISO week
- Day 1 of 365 · 2025-W01-3
- Seconds / ms / µs / ns
- 1735689600 s 1735689600000 ms 1735689600000000 µs 1735689600000000000 ns
- Julian Day
- JD 2460676.50000 · MJD 60676.00000
Runs in your browser. Nothing is sent.
Convert a Unix Timestamp to a Human-Readable Date
Paste any Unix timestamp into the box above and the results update as you type. You do not need to pick a unit first. This Unix timestamp converter counts the digits and labels the value, for example “Detected: milliseconds” for a 13-digit number. If the guess is wrong, pick the unit from the menu next to the input.
Each of the eight result rows has its own copy button:
- UTC and local time, with the IANA zone name, such as America/New_York.
- ISO 8601 and RFC 2822 strings, ready for APIs, logs and email headers.
- Relative time, such as “3 hours ago” or “in 2 days”.
- The day of the year and ISO week.
- The same instant in seconds, milliseconds, microseconds and nanoseconds.
- The Julian Day and Modified Julian Date.
That is the fastest way to turn epoch to human readable text. Need the live value instead? See the current epoch time, which ticks every second. For weekday names and format presets, use the dedicated timestamp to date converter.
How to convert a timestamp in three steps:
- Paste the timestamp. Paste a Unix timestamp into the converter. The unit is detected from the number of digits.
- Pick a time zone. Keep your local time zone or choose any IANA time zone.
- Copy the result. Copy the UTC, local, ISO 8601 or RFC 2822 date with one click.
Convert a Date to Epoch Time
Open the Date → Timestamp tab to go the other way. Type a date such as 2025-01-01 00:00:00, paste an ISO 8601 string with an offset, or choose a moment with the date picker. The converter returns the epoch value in every unit, plus the same eight result rows.
Date to epoch conversion depends on the time zone, and every date to timestamp result shows which zone was used. A date with no offset is read in the zone you select below the results. So 2025-01-01 00:00 in New York gives 1735707600, five hours later than the same clock time in UTC (1735689600). A string ending in Z or +05:00 carries its own offset and ignores the selector.
Daylight saving time can make a clock time skip or repeat. If you enter 02:30 on 8 March 2026 in New York, a time that never happened because clocks jumped forward, the converter moves it to 03:30 and tells you. When clocks fall back, the hour repeats and it uses the first one. To compare zones directly, try the UTC to local time converter, or parse and build ISO 8601 strings in detail.
Ambiguous dates like 03/04/2025 are never guessed. You pick MM/DD or DD/MM with one click, or switch to ISO format.
Batch Epoch Converter for Log Files and CSV Columns
The Batch tab converts every timestamp in a block of text at once. Paste up to 100,000 lines or open a .log, .txt or .csv file, and the tool finds each 10, 13, 16 or 19 digit number and adds its ISO 8601 date.
It is built for the jobs that send people to an epoch converter in the first place:
- nginx and Apache access logs with epoch query parameters
- CloudWatch and other log exports with millisecond
timestampfields - JSON log lines where
tsis in milliseconds or nanoseconds - CSV columns exported from a database or analytics tool
Choose Annotate inline to keep each original line with the date added, or Table for one row per timestamp. Copy everything or download a CSV. A counter shows how many timestamps were converted and how long it took. The work runs in a background thread in your browser, so large files never leave your machine.
Is Your Timestamp in Seconds, Milliseconds or Nanoseconds?
Count the digits. A present-day Unix timestamp has 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. Mixing them up is the most common timestamp bug: read milliseconds as seconds and you land tens of thousands of years in the future.
| Digits | Unit | Example (2025-01-01T00:00:00Z) | Typical source |
|---|---|---|---|
| 10 | seconds | 1735689600 | date +%s, Python int(time.time()), MySQL UNIX_TIMESTAMP() |
| 13 | milliseconds | 1735689600000 | JavaScript Date.now(), Java System.currentTimeMillis() |
| 16 | microseconds | 1735689600000000 | Tracing tools and high-precision database exports |
| 19 | nanoseconds | 1735689600000000000 | Python time.time_ns(), Go UnixNano() |
The detector uses ranges, not exact counts: up to 11 digits is seconds, 12 to 14 milliseconds, 15 to 17 microseconds and 18 to 20 nanoseconds. That covers dates far into the past and future. Microseconds and nanoseconds are handled with exact integer math, so no digit is lost to rounding.
If you work with JavaScript or Java, the converter for 13-digit millisecond timestamps is locked to that unit. For the full seconds vs milliseconds breakdown, including the bugs each mix-up causes, read the guide.
Get the Current Unix Time in Your Code
Every language can read the system clock as a Unix timestamp in one line. The tabs below show how to get the current Unix time and how to convert epoch time to a date in 11 languages and tools. Each snippet uses the value from the converter above, so you can paste it and get the same result.
Watch the unit: JavaScript and Java count milliseconds, while Python, Go, PHP, SQL and the shell count seconds. For depth, read the Python timestamp guide, the JavaScript timestamp guide, or learn to convert epoch to date in Excel. You can also browse all Unix timestamp guides.
import time
from datetime import datetime, timezone
now = int(time.time()) # current Unix time in seconds
dt = datetime.fromtimestamp(1735689600, tz=timezone.utc)
print(dt.isoformat()) const now = Math.floor(Date.now() / 1000); // Date.now() is in ms
const date = new Date(1735689600 * 1000);
console.log(date.toISOString()); import java.time.Instant;
long now = Instant.now().getEpochSecond();
Instant instant = Instant.ofEpochSecond(1735689600L);
System.out.println(instant); // ISO 8601 in UTC now := time.Now().Unix()
t := time.Unix(1735689600, 0).UTC()
fmt.Println(t.Format(time.RFC3339)) <?php
$now = time();
$dt = (new DateTimeImmutable('@1735689600'))->setTimezone(new DateTimeZone('UTC'));
echo $dt->format('Y-m-d H:i:s'); long now = DateTimeOffset.UtcNow.ToUnixTimeSeconds();
DateTimeOffset dto = DateTimeOffset.FromUnixTimeSeconds(1735689600);
Console.WriteLine(dto.ToString("o")); SELECT UNIX_TIMESTAMP(); -- current Unix time
SELECT FROM_UNIXTIME(1735689600); -- uses the session time zone SELECT EXTRACT(EPOCH FROM now()); -- current Unix time
SELECT to_timestamp(1735689600); -- returns timestamptz =1735689600/86400+DATE(1970,1,1) Excel epoch to date guide: formulas for seconds, ms and Sheets
date +%s # current Unix time
date -u -d @1735689600 # GNU/Linux
date -u -r 1735689600 # macOS and BSD [DateTimeOffset]::UtcNow.ToUnixTimeSeconds()
[DateTimeOffset]::FromUnixTimeSeconds(1735689600).UtcDateTime What Is Epoch Time? The Unix Epoch in One Minute
Epoch time, or Unix time, is the number of seconds that have passed since the Unix epoch: 00:00:00 UTC on Thursday, 1 January 1970. It ignores leap seconds, so every day is exactly 86,400 seconds long. Because it is one integer, computers can store, sort and subtract it without caring about time zones or calendars.
The starting date is a convention. It was a recent, round moment when Unix timekeeping was defined, and the POSIX standard later fixed it for every compatible system. Negative values count backward, so -86400 is 31 December 1969.
Unix time is not the same thing as UTC. UTC is a time scale that occasionally adds a leap second, giving a minute 61 seconds. Unix time pretends those seconds do not exist and keeps every day at 86,400. In practice that means you can do date math with plain arithmetic, and any Unix time converter gives the same answer everywhere.
Read a longer explanation of what epoch time is and why it starts in 1970, see how 32-bit systems hit the year 2038 problem, or compare timestamp formats such as ISO 8601 and RFC 2822. Every explainer is collected on the learn Unix time page.
How This Unix Epoch Converter Handles Time Zones
A timestamp has no time zone. The zone only comes in when you show it as a date. This Unix epoch converter uses the IANA time zone database that ships with your browser, the same data used by Linux, macOS, Java and most databases. It picks your zone automatically and lets you switch to any of the roughly 400 zone names, from America/New_York to Asia/Karachi.
Offsets and daylight saving rules come from that database, so historical dates use the rules that applied at the time. A summer date in London shows +01:00, a winter date Z. Your choice of zone and 12- or 24-hour clock is remembered in your browser for next time.
Leap seconds are the one thing no converter can show, because Unix time skips them by definition. Read how Unix time treats leap seconds if you need sub-second accuracy around the end of 2016.
Common Unix Timestamps and Time Spans
These are the values people search for most, plus the spans you need to convert epoch time by hand. Today's number on the day of the year tracker is a useful companion, and astronomical dates are easier with the Julian date converter.
| Unix timestamp | Date (UTC) | 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 | Digits 1 to 0 in order |
1700000000 | 2023-11-14T22:13:20Z | 1.7 billion seconds |
2000000000 | 2033-05-18T03:33:20Z | 2 billion seconds |
2147483647 | 2038-01-19T03:14:07Z | Largest signed 32-bit value |
-2147483648 | 1901-12-13T20:45:52Z | Smallest signed 32-bit value |
| Time span | Seconds |
|---|---|
| 1 minute | 60 |
| 1 hour | 3,600 |
| 1 day | 86,400 |
| 1 week | 604,800 |
| 30 days | 2,592,000 |
| 365 days | 31,536,000 |
| 365.25 days (average Julian year) | 31,557,600 |
Months and years vary in length, so add calendar months with a date library rather than a fixed number of seconds. The 365.25-day figure is an average, useful for rough estimates only.
Epoch Converter FAQ
What is epoch time and why does it start in 1970?
Epoch time, also called Unix time, is the number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. The date is a convention: it was a recent, round starting point when Unix timekeeping was defined, and later standards such as POSIX kept it. Every Unix-like system and most programming languages now share it.
How do I convert a Unix timestamp to a date?
Paste the number into the converter at the top of this page. It reads the digit count to tell seconds from milliseconds, microseconds or nanoseconds, then shows the date in UTC, your local time, ISO 8601 and RFC 2822. For example, 1735689600 converts to 2025-01-01T00:00:00Z. Every result row has its own copy button.
Is my timestamp in seconds or milliseconds?
Count the digits. A present-day timestamp in seconds has 10 digits, such as 1735689600. In milliseconds it has 13 digits, such as 1735689600000. Microseconds have 16 and nanoseconds 19. JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds, while date +%s, Python's int(time.time()) and MySQL's UNIX_TIMESTAMP() return seconds.
Is Unix time the same in every time zone?
Yes. A Unix timestamp counts seconds from one fixed instant in UTC, so the same moment has the same value in Tokyo, London and New York. Time zones only matter when you turn the number into a calendar date and clock time. That is why the converter shows UTC and your local time side by side.
What happens to Unix time in 2038?
Systems that store Unix time in a signed 32-bit integer can only count to 2,147,483,647, which is 03:14:07 UTC on 19 January 2038. One second later the value wraps to a negative number that reads as 13 December 1901. Systems that keep time in 64-bit values are not affected, and this converter is not limited to 32 bits.
Does this epoch converter send my timestamps anywhere?
No. Every conversion, including batch conversion of whole log files, runs in your browser with JavaScript. The timestamps you paste never leave your device, and conversions keep working if your connection drops after the page loads. The only things the site remembers, such as your time zone and preferred unit, are stored in your own browser.
Is a Unix timestamp the same thing as a timestamp?
A Unix timestamp is one kind of timestamp. The word timestamp covers any record of when something happened, including ISO 8601 strings like 2025-01-01T00:00:00Z, database DATETIME values and the dates printed in log lines. Unix timestamps are popular because a single integer is easy to store, sort and compare across systems.
Can I convert a whole column of timestamps at once?
Yes. Open the Batch tab, paste up to 100,000 lines or open a .log, .txt or .csv file, and select Convert all. The tool finds every 10, 13, 16 or 19 digit timestamp, adds the ISO 8601 date next to each one, and lets you copy the result or download it as a CSV file.
More tools
- Current Epoch TimeWatch the current Unix timestamp tick live and copy it in seconds or milliseconds.
- Milliseconds to Date ConverterRead 13-digit JavaScript and Java millisecond timestamps as dates.
- Discord Timestamp GeneratorBuild <t:…> codes that show event times in every reader's own zone.
- What Day of the Year Is It?Today's day number, days left in the year and the ISO week.
- Julian Date ConverterJulian Day, Modified Julian Date and YYDDD ordinal dates, both ways.