Real Epoch Converter logo realepochconverter

Epoch Converter. Unix time, converted instantly.

The free online epoch time converter. Unix epoch time to human-readable dates and back, with a live ticking clock, UTC or local time, batch pasting, and code snippets for your stack.

unix time · ticking
0 seconds 000

—

0x0

converter

One timestamp, every format.

Convert epoch time to dates and back. Precision auto-detected, timezone your choice.

Dates below render in the timezone above. Press / to focus the field.

Deep-link any timestamp with ?ts=1722750000

all converters

One site, every timestamp format.

20 converters + 1 programming guides.

unix time

Epoch Converter Unix Timestamp to Date Date to Epoch Milliseconds to Epoch

special formats

Snowflake ID LDAP / Active Directory GPS Time NTP Timestamp .NET DateTime Ticks Mac HFS+ Timestamp Excel Date (OADate) UUID v1 / v7 & ULID Chrome / WebKit Time Cocoa Core Data Timezone Converter Time Zone Difference UTC Offset Lookup Nanosecond / Microsecond Year 2038 Countdown Common Timestamps

programming

Programming Guides
batch converter

Many timestamps, one paste.

Drop in a whole list. One per line, or separated by commas or spaces. Every row converts, ready to copy or export.

0 timestamps

code snippets

Same moment, in your stack.

Generate the current Unix timestamp in JavaScript, Python, PHP, SQL, Go, Java, C#, Rust, C++, or PowerShell. Copy and ship.

Snippets stay in sync with the live clock above.

Built for developers.

Precision
Paste a number. The converter figures out whether it's seconds, milliseconds, or microseconds. No guessing. Lock it manually if you need to.
Timezone
450+ IANA timezones. Live UTC offset display. Switch between UTC and local with one click. Your preference sticks between visits.
Batch mode
Paste a list of timestamps. Get a table back. Export as TSV or CSV for your spreadsheet. One-click copy per row.
Code snippets
Javascript, Python, PHP, SQL, Go, Java, C#, Rust, C++, and PowerShell. All snippets update in real time with the live clock.
Privacy
Everything runs in your browser. No data leaves your machine. No sign-up. No paywall.

20 converters (4 core Unix, 16 specialist formats) and 1 programming guides.

day of the year live · UTC

What day of the year is it today?

Today is day 269 of 2026 — Sep 26, Sat in UTC. 96 days remain in 2026.

current day number

269

of 365 in 2026

days remaining

096

until 2026 ends

today · UTC

Sep 26, 2026

Sat · day 269

Day numbers use the ISO 8601 ordinal date convention: January 1 is day 1, and each subsequent day adds one. The count does not depend on your timezone — it is the day number for the UTC date. Use the links below to see the full list for any year, or jump to the current day number page for the live value with the remaining-day count and the week number.

Today's day number All days in 2026 Current week number
week number live · ISO 8601

What week of the year is it?

This week is ISO week 39 of the ISO week-year 2026. Week 39 starts on Sep 21, 2026 (Mon) and ends on Sep 27, 2026 (Sun) — that is the Monday-to-Sunday week used across most of the world and by ISO 8601.

current week number

39

of 2026 · ISO week

this week's range

Sep 21, 2026 (Mon)

—

Sep 27, 2026 (Sun)

ISO week numbers are the world-wide compatible standard: every week has exactly seven days, week 1 is the week containing the first Thursday of the year, and weeks always start on Monday. Some regional calendars use Sunday as the first day of the week — this site uses ISO weeks so the numbering stays consistent for an international audience. For the full year's week list, including the start and end dates of every week, follow the links below.

Today's week number All weeks in 2026 Day of the year
about the tool

What Is an Epoch Converter?

An epoch time converter (also called an epoch converter or epoch unix time converter) is a utility that translates between Unix time and human-readable dates and times. Unix time, also known as the Unix timestamp, POSIX time, or epoch time, counts the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC, the moment known as the Unix epoch. Because a timestamp is a single number that identifies an exact instant anywhere on the planet, it is the standard way that computers, databases, and logs record moments in time.

A Unix Epoch Converter That Works Both Ways

This page is a full Unix epoch converter: it converts timestamps to dates and dates back to timestamps. Paste any timestamp into the converter and you instantly see the equivalent date and time in your local timezone, in UTC, and in ISO 8601 format. Switch to date-to-epoch mode, type any date string, or pick a moment with the built-in date picker, and the tool returns the matching Unix timestamp in seconds, milliseconds, or microseconds. In other words, it is an epoch timestamp converter that combines a timestamp-to-epoch and a date epoch converter in one tool. However you need to convert epoch time, the direction is covered.

UTC Epoch Converter and Local Epoch Converter in One

A Unix timestamp is absolute. It marks the same instant everywhere on Earth. How that instant reads, however, changes with your timezone. This tool works as both a UTC epoch converter and a local epoch converter: choose UTC for server logs and API payloads, or pick your local timezone (or any of the hundreds of IANA timezones) and every result renders in the context you need. The live clock at the top of the page ticks in both local and UTC time, and your timezone preference is remembered between visits.

Seconds, Milliseconds, and Microseconds: Auto-Detected

Not every epoch time counts seconds. Many web APIs return epoch time in milliseconds, and high-precision systems work in microseconds. This epoch time converter detects the unit automatically: paste 1722750000, 1722750000123, or 1722750000123456 and it knows the difference. You can also lock the unit manually for ambiguous values. No more guessing whether that number is seconds or milliseconds.

A Linux Epoch Converter for Developers

Developers who live in the terminal spend a lot of time reading Unix timestamps in file listings, logs, and database rows. This tool doubles as a Linux epoch converter for that work: paste a timestamp from stat, dmesg, or a MySQL and Postgres dump and read the date instantly. It also generates copy-ready code snippets in ten languages: JavaScript, Python, PHP, SQL, Go, Java, C#, Rust, C++, and PowerShell, so you can produce the current epoch time in your own stack. Whether you need to convert time to epoch for a query or decode a timestamp from a log, the answer is one paste away.

Batch Convert Many Timestamps at Once

Need to convert a whole list? The batch converter accepts one timestamp per line (or values separated by commas and spaces) and converts every row in a single pass. Each result is copied with one click, and the full table exports as a spreadsheet-ready TSV or CSV. It is the fastest online epoch converter for bulk timestamp-to-date work.

Specialized Converters for Every Timestamp Format

Unix time is just one of many epoch systems, and each of the others gets its own dedicated converter on this site: a snowflake ID converter for Discord and Twitter/X 64-bit IDs, an LDAP timestamp converter for Active Directory 100-nanosecond values, a GPS time converter for week and seconds-of-week readings, an NTP timestamp converter for seconds since 1900, a .NET ticks converter for DateTime ticks since year 1, a Mac HFS+ timestamp converter for seconds since 1904, and an Excel date converter for OADate serial numbers. A second wave of specialists fills the remaining gaps: a UUID v1 / v7 & ULID converter that extracts the creation time from time-ordered IDs, a Chrome / WebKit timestamp converter for microseconds since 1601, a Cocoa Core Data timestamp converter for seconds since 2001, a timezone converter for moving a wall-clock time between two zones, a time zone difference calculator for the standing gap between two zones, a UTC offset lookup that shows every zone sharing an abbreviation, a nanosecond and microsecond timestamp converter for 19-digit values, a Unix hex timestamp converter for hexadecimal epoch values, a Year 2038 countdown to the 32-bit overflow, and a common Unix timestamps reference. Each landing page explains the epoch, the arithmetic, worked examples, and the code you need, and the programming guides cover getting and converting Unix time in ten languages: JavaScript, Python, PHP, Go, Java, C#, Rust, C++, SQL, and PowerShell.

Free, Fast, and Private Online Epoch Converter

This is a free online epoch converter and epoch date converter with no sign-up and no paywall. Conversions run entirely in your browser, so they are instant and your data never leaves your machine. The site is supported by unobtrusive advertising, and nothing you convert is ever sent to a server. Deep-link any timestamp with a simple URL parameter, toggle dark mode, and keep the tool open for your next debugging session. Bookmark it: the unix timestamp to date and date to timestamp conversions you use most are now one click away.

References

How this site handles negative timestamps, fractional seconds, leap seconds, unit auto-detection, and DST is documented on the methodology page.

faq

Epoch Converter FAQ

Quick answers about Unix time, timestamps, timezones, and this tool, including the questions developers ask most.

How do I convert IST to epoch?

To convert IST (Indian Standard Time, UTC+5:30) to epoch, select Asia/Kolkata from the timezone list and type your IST date and time into the date-to-timestamp mode. The tool converts it to a Unix timestamp you can use in code. The reverse also works: paste a timestamp and read it back in IST.

What is the Unix epoch?

The Unix epoch is the reference point for Unix time: January 1, 1970, 00:00:00 UTC. Every Unix timestamp is the number of seconds (or milliseconds) elapsed since that instant. It is the standard way computers, operating systems, databases, and logs record an exact moment in time, independent of timezone.

What is a timestamp converter?

A timestamp converter translates Unix time into a human-readable date and time, and back again. Paste a value like 1722750000 and you get the equivalent date in your local timezone and UTC; type a date and the tool returns its timestamp in seconds, milliseconds, or microseconds. Developers use it to decode the numbers that show up in server logs, API payloads, and database rows.

How do I convert epoch to time?

To convert epoch to time, paste the timestamp into the converter and read the result as a human-readable date and time. Since a Unix timestamp is the number of seconds since January 1, 1970, UTC, the converter works it backwards: it shows the exact moment that number represents, in UTC and in your local timezone. For example, 1722750000 converts to August 4, 2024. If you need the other direction (a date back to a timestamp), switch to date-to-epoch mode.

What is an epoch converter used for?

It translates Unix timestamps into dates and dates into timestamps. The common cases: decoding the epoch value in a log line or API response, generating a timestamp to store alongside a record, and checking whether a suspicious-looking number is seconds or milliseconds. Because Unix time carries no timezone, a converter is also the quickest way to see one moment side by side in UTC and local time.

How do I read a timestamp in a specific timezone — UTC, EST, PST, IST?

Pick the zone from the timezone list above the converter and every result renders there. The list uses IANA zone names — UTC, America/New_York for Eastern (UTC−5 standard, UTC−4 daylight time in summer), America/Los_Angeles for Pacific (UTC−8/−7), Asia/Kolkata for India (UTC+5:30, no daylight saving) — so the historical and daylight-saving offsets are applied per moment, the same way the tz database does it. A timestamp itself has no timezone; the zone you pick is a rendering choice, which is why the same value reads differently in January and July in New York.

What is POSIX time?

POSIX time is another name for Unix time: the number of seconds since January 1, 1970, 00:00:00 UTC, as defined by the POSIX standard (also called the Unix epoch, epoch time, or Unix timestamp). Like Unix time, it ignores leap seconds — a day is exactly 86,400 seconds as far as POSIX is concerned.

What format is epoch time?

Epoch time is stored as a single integer counting seconds since January 1, 1970, 00:00:00 UTC (for example 1722750000). The epoch format appears as a 10-digit number for seconds, 13 digits for milliseconds, and 16 digits for microseconds. This tool auto-detects the unit, so you never have to count digits yourself.

Why does my timestamp show a date in January 1970?

A value in seconds was read as milliseconds. A timestamp near zero in milliseconds is still 1970: 1,722,750,000 milliseconds after the epoch is January 21, 1970. If a real-world date comes back as January 1970, your 10-digit seconds value was multiplied by 1000 twice, or passed to code that expects milliseconds. Paste it into the converter with the unit locked to seconds and compare.

Why does my timestamp show a year around 58,500?

A 13-digit millisecond value was read as seconds. 1,722,750,000,123 seconds after 1970 lands in the year 56,552, so a date tens of thousands of years out means the unit was misread. JavaScript makes this easy to hit: new Date(1767225600000) is correct, but new Date('1767225600000') parses the string as seconds in some engines. Lock the unit to milliseconds in the converter to confirm.

Why is my timestamp off by 5 hours 30 minutes?

The value was formatted in the wrong timezone. 5 hours 30 minutes is the India Standard Time offset (UTC+5:30), so a moment formatted in UTC while you expected IST (or the reverse) differs by exactly that amount. The converter shows both readings side by side; pick the zone your source system actually uses.

How do I tell seconds from milliseconds reliably?

Count the digits of the integer part: 10 digits is seconds (until the year 2286), 13 digits is milliseconds (until the year 2286 in ms), 16 digits is microseconds. The heuristic fails in a narrow overlap window around November 2004 in microseconds, so when a value could plausibly be either, check it against a known event or ask the API that produced it. The converter auto-detects and lets you lock the unit manually.

What happens to Unix time during a leap second?

Nothing visible, by design. Unix time ignores leap seconds: during an inserted leap second the same Unix second maps to two UTC seconds, and systems that need true UTC handle the smear or the extra second above the Unix layer. The last inserted leap second was at the end of 2016; Unix timestamps repeated 1483228799 for two UTC seconds that night.

Is 2038 still a problem on 64-bit systems?

No. The 2038 limit comes from signed 32-bit time_t, which overflows on January 19, 2038 at 03:14:07 UTC. 64-bit time_t (the default on modern Linux, macOS, and Windows) handles dates hundreds of billions of years out. It still matters for embedded 32-bit systems, old databases with 32-bit timestamp columns, and file formats that store 32-bit times. See the Year 2038 converter page for specifics.

How do I convert a Discord snowflake ID to a date?

A Discord snowflake ID is a 64-bit integer: the top 41 bits are a timestamp in milliseconds since the Discord epoch (January 1, 2015), and the remaining bits store the worker, process, and sequence. To decode one, shift the ID right by 22 and add 1420070400000 to get epoch milliseconds, then format it as a date. Paste the ID into the snowflake ID converter for the full breakdown: timestamp, worker, process, and sequence.

What is an LDAP or Active Directory timestamp?

Active Directory and LDAP record moments like password changes and account expirations as 100-nanosecond intervals since January 1, 1601 UTC. A typical value is 18 digits long, for example 134305344000000000. To convert one to Unix time, divide by 10,000,000 and subtract 11644473600 seconds. The LDAP timestamp converter does exactly that, in both directions.

What are GPS week and seconds-of-week?

GPS receivers count time as a week number plus seconds since the GPS epoch: midnight UTC on January 6, 1980. GPS time ignores leap seconds, so its clock currently runs 18 seconds ahead of UTC. To convert, use Unix time = GPS total seconds + 315964800 − 18. The GPS time converter handles weeks, seconds-of-week, and the leap-second offset.

guides

Unix time, explained

Long-form guides for developers who debug logs, APIs, and databases. Written by the team, reviewed against the specifications, and linked to a converter whenever one helps.

All guides
Copied