RFC 2822 to ISO 8601 date converter
Paste the Date value from an email header or the pubDate of an RSS item and get the form databases and programming languages expect.
Loading the tool…
Processing and privacy: The result is calculated inside your browser and your data is not sent to any server.
How to use it
- Enter rfc 2822 date.
- The result appears straight away and updates as you edit.
- Copy the result, or copy a link that keeps the same values to share it.
How it is calculated
Day, English month abbreviation, year, time and the ±hhmm offset are read, then written as YYYY-MM-DDTHH:MM:SS±hh:mm. UTC = local time - offset, and the Unix timestamp counts seconds since 1970-01-01 UTC.
Example
Inputs: RFC 2822 date = Thu, 01 Oct 2026 09:30:00 +0300. Result: ISO 8601 with offset: 2026-10-01T09:30:00+03:00.
Thu, 01 Oct 2026 09:30:00 +0300
2026-10-01T09:30:00+03:00
Limits and caveats
- Only UT, GMT, Z and the old US zone names such as EST and PDT are accepted as names; any other zone must be written as a number such as +0300.
- Leap second 60 and years before 1900 are not accepted.
- -0000 is treated as UTC, although the standard uses it to mean the local zone is unknown.
Questions about this tool
What is the difference between RFC 2822 and ISO 8601?
RFC 2822 is the text style used in email, such as Thu, 01 Oct 2026 09:30:00 +0300. ISO 8601 is numeric and runs from the largest unit to the smallest, such as 2026-10-01T09:30:00+03:00, which sorts and parses more easily.
What if the weekday is wrong?
The tool stops and tells you the correct weekday, since a mismatched day usually means the date was copied or typed wrongly.
Are 2-digit years accepted?
Yes, as the standard allows for old messages: 00 to 49 mean 2000 to 2049 and 50 to 99 mean 1950 to 1999.