Convert any date and time to the RFC 2822 email date format — the standard used in email headers and HTTP timestamps. Enter your date, time, and timezone, and get back the properly formatted RFC 2822 string (e.g. Wed, 11 Jun 2025 10:30:00 +0000). You can also paste an existing RFC 2822 string to decode it back into its component parts.
RFC 2822 Formatted Date
--
Day of Week
--
Decoded Date
--
Decoded Time
--
Timezone Offset
--
Unix Timestamp
--
RFC 2822 is a date and time notation format defined in the RFC 2822 Internet Message Format standard. It is the format used in email headers (the 'Date:' field) and some HTTP headers. A typical RFC 2822 date looks like: Wed, 11 Jun 2025 10:30:00 +0000, where the day-of-week abbreviation is optional but commonly included.
RFC 2822 dates are most commonly found in email headers to timestamp when a message was sent or received. They also appear in HTTP headers, RSS/Atom feeds, and various internet protocols that require a standardized human-readable timestamp with timezone information.
The format is: Day, DD Mon YYYY HH:MM:SS ±HHMM — for example, Wed, 11 Jun 2025 10:30:00 +0000. The day-of-week (e.g. Wed) is followed by a comma, then the numeric day, three-letter month abbreviation, four-digit year, time in 24-hour format, and a timezone offset from UTC.
Enter your date, time, and timezone in the fields above and the tool will generate the correctly formatted RFC 2822 string for you. It automatically calculates the day of the week, formats the month as a three-letter abbreviation, and appends the correct timezone offset.
Paste your RFC 2822 string into the 'Or Paste RFC 2822 String to Decode' field. The tool will parse it and display the individual components: date, time, day of week, timezone offset, and the equivalent Unix timestamp.
RFC 2822 accepts both numeric offsets like +0530 and legacy timezone abbreviations like EST or GMT. However, numeric offsets are preferred and more reliable because abbreviations like CST can be ambiguous (Central Standard Time vs China Standard Time). Always use numeric offsets in new implementations.
ISO 8601 uses a format like 2025-06-11T10:30:00Z, which is common in APIs and databases. RFC 2822 uses a more human-readable format like Wed, 11 Jun 2025 10:30:00 +0000, designed for email and internet message headers. Both include timezone information but have different syntax conventions.
A Unix timestamp is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC. Any RFC 2822 date can be expressed as a Unix timestamp and vice versa. This tool shows the Unix timestamp equivalent alongside the RFC 2822 string so you can use whichever format your application requires.