ISO 8601 to RFC 2822 converter
Paste an ISO 8601 date to get the RFC 2822 form that email headers and RSS pubDate fields 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 iso 8601 date and zone if the text has no offset.
- 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
Reads the year, month, day, time and offset from the text, then writes: Day, DD Mon YYYY HH:MM:SS ±hhmm. The UTC version = time - offset.
Example
Inputs: ISO 8601 date = 2026-10-01T09:30:00+03:00, Zone if the text has no offset = UTC. Result: RFC 2822 with the same offset: Thu, 01 Oct 2026 09:30:00 +0300.
2026-10-01T09:30:00+03:00
Thu, 01 Oct 2026 09:30:00 +0300
Limits and caveats
- RFC 2822 has no fractional seconds, so they are dropped.
- ISO week and ordinal date forms, and leap second 60, are not accepted.
Questions about this tool
Where is RFC 2822 used?
In the Date header of email, the pubDate field of RSS feeds and some HTTP headers.
What if the text has no Z or offset?
The time is read in the zone you pick, which is UTC by default.
Why are day and month names in English?
The standard requires English abbreviations such as Thu and Oct; translated names would make the date invalid.