localdatetime Open local time

Your Local Date and Time

Every format at once — ISO 8601, RFC 2822, epoch, week number, day of year — each one copyable.

This page shows your local date and time in every notation that matters, live and each with a copy button. ISO 8601 for data, RFC 2822 for headers, epoch seconds and milliseconds for code, plus the ISO week, day of year, UTC offset and the IANA zone identifier your browser reports. No conversion, no maths, no switching between four different sites.

Which format to use where

ISO 8601 is the default for storing or exchanging a date: it sorts lexicographically and is unambiguous everywhere. Epoch values are best for durations and comparisons in code. RFC 2822 is what email headers and HTTP dates use. Anything with slashes is for humans in one country only — see date formats around the world.

Your offset is not your time zone

The offset shown is where your clock sits right now; the IANA identifier is the durable fact about where you are. Offsets change with daylight saving, identifiers do not, which is why software should record the latter — see why store dates in UTC and the offset checker.

Guides about Local Date & Time

More localdatetime.now pages

Frequently asked questions

What is my current timestamp?
The epoch seconds and milliseconds values above update live and can be copied with one click. Both count from 1 January 1970 UTC.
What is my time zone?
The IANA time zone row shows the identifier your browser reports, such as Europe/London or America/New_York, along with your current UTC offset.
Is any of this sent anywhere?
No. Every value is computed in your browser from your device's clock. Nothing is transmitted or stored.
Why does ISO 8601 appear twice?
Once in your local time with its offset, and once in UTC ending in Z. They describe the same instant in two equally valid ways.