AZ Tools

Date Format Converter

Time

Paste an ISO 8601 string, an RFC 2822 date, a Unix epoch (seconds or milliseconds — auto-detected by digit count), or any free-form date your browser can parse, and get the same instant rendered as ISO local / UTC, RFC 2822, HTTP `Date` (IMF-fixdate), SQL DATETIME, Unix seconds / milliseconds, locale string, date-only / time-only, and day-of-year. Leave the input empty to format "now".

Formats
  • ISO 8601 (local)2026-06-02T18:03:42.555+00:00
  • ISO 8601 (UTC)2026-06-02T18:03:42.555Z
  • RFC 2822Tue, 02 Jun 2026 18:03:42 +0000
  • HTTP / IMF-fixdateTue, 02 Jun 2026 18:03:42 GMT
  • SQL DATETIME (local)2026-06-02 18:03:42
  • SQL DATETIME (UTC)2026-06-02 18:03:42
  • Unix epoch (seconds)1780423422
  • Unix epoch (milliseconds)1780423422555
  • Locale (full)Tue Jun 02 2026 18:03:42 GMT+0000 (Coordinated Universal Time)
  • Locale (date)6/2/2026
  • Locale (time)6:03:42 PM
  • Date only2026-06-02
  • Time only18:03:42
  • Year / Day-of-year2026-153

How to use

  1. Type or paste a date in any common format.
  2. Read off the format you need; hit Copy to send it to the clipboard.
  3. Click Now to clear the input and use the current time.

Frequently asked questions

How does it tell epoch seconds from milliseconds?
By digit count. 10-or-11-digit pure-integer input is treated as seconds (Unix timestamps are 10 digits through year 2286); 13-plus digits is milliseconds.
Why does ISO 8601 local include a timezone offset?
ISO 8601 requires an offset on local-time strings (`+09:00`, `-05:00`) so the instant is unambiguous. The UTC variant ends in `Z` and the offset is implicit.
What's IMF-fixdate?
The format HTTP defines for the `Date`, `Expires`, `Last-Modified`, `Set-Cookie` (Expires=) headers — `Mon, 02 Jun 2026 15:04:05 GMT`. Always UTC.
Why does the output differ across machines?
Locale (date / time string) and the local-timezone offset depend on your browser settings. The Unix epoch and ISO UTC values are the same everywhere.

Related tools