Free trial The cheapest email marketing platform: try Moosend free for 30 days, no credit card. Don't miss your seat. The cheapest email marketing platform Start free trial →

RFC 3282: Content Language Headers

RFC 3282 Content-Language: language tags in email headers and MIME parts, how it differs from charset and from the HTML lang attribute that screen readers actually use.

Alaa Touil
Email infrastructure specialist, 8+ years in SMTP and deliverability
6 min read Updated Nov 9, 2026 109 views
RFC 3282 Content Language Headers - SMTPedia reference
RFC 3282
Content Language Headers

Current standard

Domain
MIME
Published
May 2002
Obsoletes
RFC 1766
SMTP relevance
Low

↗ Read on rfc-editor.org

What this RFC defines

RFC 3282 (May 2002, obsoleting RFC 1766) defines two header fields for any protocol that carries content: Content-Language, which declares the natural language of the content (en, fr, zh-Hant), and Accept-Language, which states the languages a user prefers. In email, only Content-Language matters in practice: Accept-Language is the field your browser sends to websites, and it is defined in this same RFC.

Where you see it in practice

Open the source of a localized newsletter or of mail sent from Microsoft Outlook and you will often find a line like Content-Language: en-US. Most other messages carry nothing. Mail clients do not need the header to work: translation features in webmail detect the language from the text itself, and the header has no effect on delivery. It is metadata, useful mainly for archiving, search and multilingual systems that want a declared value rather than a guess.

The Content-Language header

The value is one or more language tags, comma-separated: Content-Language: fr, or Content-Language: fr, en for a bilingual message. The header can sit in the message header or on an individual MIME part, which lets a multipart/alternative message say “this part is French, that part is English”. The tags themselves follow BCP 47, today RFC 5646.

Content-Language versus the HTML lang attribute

For HTML email, the signal that screen readers and browsers actually use is the lang attribute on the HTML element, for example <html lang="fr">. A screen reader picks its pronunciation from that attribute, not from a MIME header it never sees. If you care about accessibility, set lang (and dir="rtl" for Arabic or Hebrew) in your template first; add Content-Language as a complement, with the same value.

Content-Language works alongside the charset parameter of Content-Type, which describes encoding, not language. A message can be encoded in UTF-8 and written in Japanese: Content-Type declares UTF-8, Content-Language declares ja. Charset is about bytes; language is about the human-readable text. Neither replaces the other.

Quick Reference

RFC 3282 (May 2002) defines the Content-Language header: identifies the natural language(s) of the message content using BCP 47 language tags (en, fr, es-419, zh-Hant). Complements the charset parameter (Content-Type) which describes bytes; language describes semantics. Useful for archiving, search and localization systems; for accessibility in HTML email, the lang attribute of the HTML element is what screen readers use. Simple, widely supported, underutilized by many bulk senders.

RFC 3282 at a glance

AspectDetail
PurposeDeclare the natural language of message content
HeaderContent-Language
FormatBCP 47 language tag(s), comma-separated
CompanionContent-Type charset (bytes vs language distinction)
PlacementMessage headers or per MIME part headers
PublishedMay 2002

Content-Language format

Content-Language header examples
Single language:
Content-Language: en

With regional variant:
Content-Language: en-US
Content-Language: es-419 (Latin American Spanish)
Content-Language: zh-Hant (Traditional Chinese script)

Multiple languages (multi-language message):
Content-Language: en, fr

Per-part in multipart/alternative for language variants:
Content-Type: multipart/alternative
…
–boundary
Content-Type: text/plain; charset=utf-8
Content-Language: en
[English body]

–boundary
Content-Type: text/plain; charset=utf-8
Content-Language: fr
[French body]

BCP 47 language tag structure:
language[-Script][-Region][-Variant]
Examples:
en English (any region)
en-US US English
en-GB British English
zh-Hans Simplified Chinese script
zh-Hant Traditional Chinese script
zh-Hans-CN Simplified Chinese as used in China
es-419 Spanish, Latin America and Caribbean

Common Content-Language mistakes

Confusing charset and language. Content-Type charset (UTF-8, ISO-8859-1) describes the byte encoding. Content-Language describes the natural language. A UTF-8 message can be English, French, Japanese; a message declared “en” can be encoded in UTF-8 or ASCII. Both headers convey different information and are complementary.
Using non-BCP 47 language codes. Legacy or invented codes (e.g., english, chinese) do not parse. BCP 47 uses standardized ISO codes: en, zh, fr. Look up the correct tag for your language; use validators when unsure.
Not declaring language on internationalized bulk mail. Sieve scripts, archives and multilingual help desks can route or index on a declared language instead of guessing it. For HTML mail, also set the lang attribute, which is the signal screen readers actually read. Bulk senders should emit Content-Language reflecting the message’s actual language.
Declaring wrong regional variant. en-US and en-GB are treated as different in some filtering contexts. Declaring en-US when the content is British English mismatches. When unsure, use the base language code (en) rather than an incorrect regional tag.
Emitting Content-Language on empty or auto-generated messages. A bounce message or empty confirmation with no natural-language content does not benefit from Content-Language. Reserve it for messages with real content in a specific language.
MIME and language RFCs

  • RFC 2045: MIME base headers (Content-Type charset)
  • BCP 47 (RFC 5646): Language Tags
  • RFC 2047: Encoded-word (charset in headers)
  • RFC 6532: Internationalized headers
SMTPedia companion guides

Frequently asked questions

Should I always emit Content-Language on my emails?

For content-bearing messages, yes when practical. It is cheap, and archives, search tools and help desks can use it. For pronunciation by screen readers, what counts in HTML email is the lang attribute on the HTML element, so set both to the same value. Empty or auto-generated messages (bounces, confirmations without body content) do not benefit and can skip. Modern email libraries emit Content-Language automatically when configured.

What is the difference between Content-Language and charset?

charset describes byte encoding (UTF-8, ASCII, Shift-JIS). Content-Language describes natural language (en, fr, ja). Same message can be UTF-8 encoded and in any of these languages; declaring both provides complete information. Complementary headers; neither substitutes for the other.

Which language tag should I use?

BCP 47 (RFC 5646). Common tags: en (English), es (Spanish), fr (French), de (German), it (Italian), pt (Portuguese), zh (Chinese), ja (Japanese), ko (Korean), ar (Arabic), ru (Russian). Add regional variant when relevant (en-US vs en-GB; es-419 for Latin American Spanish vs es for Iberian). Script tags when script matters (zh-Hant vs zh-Hans). Look up correct tag at IANA Language Subtag Registry.

Can a message declare multiple languages?

Yes, comma-separated: Content-Language: en, fr. Used when the message body contains both languages (bilingual documents, mixed-language communication). Some contexts also declare per-part in multipart/alternative: one part in English, one in French, each with its own Content-Language. Recipient clients can choose based on user preference.

Do bulk senders typically emit Content-Language?

Inconsistently. Some mail clients and template systems add it by default (Outlook commonly writes Content-Language: en-US or the user’s locale), many sending platforms do not. Check by viewing the source of one of your own sends. Emitting it costs nothing; just make sure the value matches the real language of the message, and that the HTML lang attribute says the same thing.

Did this guide save you time?

SMTPedia is free and independent. A coffee helps keep every guide accurate.

Buy SMTPedia a coffee

See SMTPedia first on Google

Add us as a preferred source in Top Stories.

Add as preferred source

About the Author

Alaa - SMTPedia author

Alaa · LinkedIn

Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.


About SMTPedia

SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.

We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.