Unix Timestamp Converter
Convert Unix epoch time to dates and back, in any time zone. Runs in your browser.
About this unix timestamp converter
This Unix timestamp converter turns epoch time into a readable date and a date back into epoch time. It detects seconds, milliseconds, microseconds and nanoseconds by size, and shows the result in any time zone.
Paste a number like 1700000000 and you get ISO 8601 in UTC and in your chosen zone, RFC 2822, a plain-language date, relative time, the day of the year and the ISO week. Every line has its own copy button. Going the other way, type 2026-10-30 14:30 or an RFC 2822 date, and the tool reads it in the zone you picked. A live clock at the top shows the current epoch in seconds and milliseconds.
Have a whole column of values from a log or a database export? Batch mode converts one per line and copies the results as tab-separated text that pastes straight into a spreadsheet.
Features
Automatic unit detection
Values under 100 billion are read as seconds, then milliseconds, microseconds and nanoseconds by size. The detected unit is shown, and you can override it.
Every common format at once
ISO 8601 in UTC and with offset, RFC 2822, a full local date, UTC, relative time, weekday, day of year and ISO week number, plus the value in all four units.
Any IANA time zone
Pick from the full list your browser knows, such as Asia/Dhaka or America/New_York. The current abbreviation and UTC offset are shown next to it.
Nanosecond precision kept
A 19-digit nanosecond timestamp keeps all nine fraction digits in the ISO output. Most converters round to milliseconds.
Daylight saving handled
When you convert a local time that does not exist (the spring-forward gap) or happens twice (the autumn fall-back), the tool says so and picks a sensible instant.
Batch conversion
Mix timestamps in any unit with written dates, up to 5,000 lines. Results appear in a table and copy as TSV.
How to use the unix timestamp converter
- 1Paste a timestamp. Seconds, milliseconds, microseconds or nanoseconds are detected.
- 2Pick a time zone and read the date in ISO 8601, RFC 2822 and plain words.
- 3Use Date → Timestamp for the reverse, or Batch for a whole list.
When to use it
Reading logs and database rows
Turn created_at values like 1761815700 into real dates, in the server's zone or your own.
Checking token and cookie expiry
The exp claim in a JWT is a Unix timestamp in seconds. The JWT decoder shows it as a date already, and this page helps with any other expiry field.
Writing test fixtures
Pick a date and copy its value in seconds or milliseconds, depending on what your API expects.
Comparing incident times across teams
Convert one instant into each team's zone. For meeting planning across several cities, the time zone converter is a better fit.
What is a Unix timestamp?
A Unix timestamp counts the seconds since 1 January 1970 at 00:00:00 UTC, a moment called the Unix epoch. It is the same number everywhere in the world, so it carries no time zone. Time zones only matter when you turn it into a calendar date.
POSIX time ignores leap seconds. Every day is exactly 86,400 seconds, which keeps the math simple. Negative values are dates before 1970: -86400 is 31 December 1969.
Some useful values: 1,000,000,000 was 9 September 2001 at 01:46:40 UTC. 1,700,000,000 was 14 November 2023 at 22:13:20 UTC. 2,000,000,000 will be 18 May 2033 at 03:33:20 UTC.
Is a Unix timestamp in seconds or milliseconds?
It depends on the system. Count the digits of a current timestamp:
- 10 digits: seconds. Unix tools, PHP time(), Go's Unix(), most databases and JWT claims.
- 13 digits: milliseconds. JavaScript Date.now(), Java System.currentTimeMillis().
- 16 digits: microseconds. Python's time.time_ns() // 1000 and some database columns.
- 19 digits: nanoseconds. Go's UnixNano(), many tracing and logging tools.
What is the Year 2038 problem?
Older systems store Unix time as a signed 32-bit integer. Its largest value, 2,147,483,647, is reached on 19 January 2038 at 03:14:07 UTC. One second later the counter overflows and wraps to December 1901.
Most modern operating systems and languages use 64-bit time now, but embedded devices, old file formats and some database columns still use 32 bits. This tool adds a note when a timestamp falls past that limit.
ISO 8601, RFC 3339 and RFC 2822: which date format should you use?
ISO 8601 writes dates largest unit first, like 2026-10-30T14:30:00Z. It sorts correctly as text and is the safest choice for APIs and logs. RFC 3339 is a strict profile of ISO 8601 used by most internet standards, and every ISO line this tool prints is valid RFC 3339.
RFC 2822, updated by RFC 5322, is the email date format: Fri, 30 Oct 2026 14:30:00 +0000. You will meet it in email headers and in older RSS feeds.
Why use Mavros
| Mavros | Typical upload sites | |
|---|---|---|
| Unit detection | Seconds, ms, µs and ns detected and shown | Seconds or ms only, picked by hand |
| Time zones | Any IANA zone, plus local and UTC | Local and UTC only |
| Formats | ISO 8601, RFC 2822, local, UTC, relative, ISO week | One or two date strings |
| Sub-millisecond precision | Kept to the nanosecond | Rounded to milliseconds |
| DST gaps and overlaps | Detected and explained | Silently shifted |
| Batch | Same page, mixed inputs, copy as TSV | Separate page or missing |
Tips
- A 13-digit value read as seconds lands tens of thousands of years in the future. If a date looks absurd, check the unit.
- Always store and send UTC. Convert to a local zone only when showing a date to a person.
- In Python, datetime.fromtimestamp(ts, tz=timezone.utc) avoids silently using the server's local zone.
- In SQL, PostgreSQL's to_timestamp(1700000000) and MySQL's FROM_UNIXTIME(1700000000) turn seconds into dates.
- To find out how long ago something happened in days or months, use the date difference calculator with the two dates.
- Building a cron schedule? The cron expression parser lists the next run times in any zone.
Questions
How do I convert a Unix timestamp to a date?
Paste it into the Timestamp box. The tool detects the unit and shows the date in UTC, your local time and any zone you pick. In code, JavaScript uses new Date(seconds * 1000).
How do I get the current Unix timestamp?
It is shown live at the top of this page. In code: Math.floor(Date.now() / 1000) in JavaScript, int(time.time()) in Python, date +%s in a Unix shell.
Are Unix timestamps always UTC?
Yes. A Unix timestamp counts seconds from midnight UTC on 1 January 1970, so it is the same everywhere. Only the readable date you convert it to depends on a time zone.
Why is my converted date in 1970?
The value was probably read in the wrong unit, or it is 0 or empty. A seconds value read as milliseconds lands in January 1970. Check the detected unit and change it if needed.
Can it handle dates before 1970?
Yes. Enter a negative timestamp, such as -86400 for 31 December 1969, or type an older date in the Date tab. JavaScript dates cover about 271,821 BC to 275,760 AD.
Does Unix time count leap seconds?
No. POSIX time treats every day as exactly 86,400 seconds. During a leap second the clock repeats or smears a second, so Unix time and atomic time differ by the accumulated leap seconds.
What happens to times that fall in a daylight saving gap?
A local time that does not exist, like 02:30 on the night clocks spring forward, is moved past the gap with a note. A time that happens twice in autumn uses the earlier instant.
Is anything sent to a server?
No. Every conversion uses your browser's clock and its Intl time zone data. Nothing is uploaded, and the page works offline once loaded.