On this page
TL;DR (May 2026): MessageFormat 2 (MF2) is the new Unicode standard for localized messages, final candidate since March 2025, spec-stable. But adoption is still early. The
i18next-mf2plugin had single-digit weekly npm downloads. The underlyingmessageformatlibrary had about 340,000. For most i18next users today, the answer to "should I migrate?" is "not yet, but understand what's coming."
Update (October 2026): the TC39 proposal is still at Stage 1. Weekly npm downloads in the week of October 5, 2026:
i18next-mf247,i18next-icuabout 757,000,messageformatabout 342,000. The picture holds: the MF1 install base keeps growing, and MF2 adoption on the i18next side is still early.
Update (October 18, 2026): i18next-mf2 2.x runs on messageformat 4.1, the stable MF2 implementation, and the i18next tooling caught up: debug warnings when i18next syntax ends up in MF2 messages, type-checked MF2 variables in TypeScript (i18next 26.5), an MF2 mode in i18next-cli that extracts and lints messages per locale, and
next-i18next/mf2for the App Router. What changed, with code, is in ICU and MessageFormat 2 in i18next. Adoption is still early, so the advice below stands.
What is MessageFormat 2?
MessageFormat 2 (MF2, formally messageformat-2.0) is the new Unicode standard for representing localized messages. It is maintained by the Unicode Common Locale Data Repository (CLDR) Technical Committee and reached Final Candidate status in March 2025, with refinements in LDML 47 and 48 (October 2025). The specification is now stable. For a developer-focused overview, Igalia's MessageFormat 2.0 introduction (May 2024) is the most accessible read.
MF2 is the successor to ICU MessageFormat (sometimes called MF1 retroactively), the format the i18next ecosystem has used via the i18next-icu plugin for over a decade. (For broader context on how JavaScript i18n formats compare, see our overview of JavaScript i18n formats.)
- Spec status: Final Candidate (March 2025), refined in LDML 47 / 48 (Oct 2025), syntax and semantics locked
- TC39
Intl.MessageFormatproposal: Stage 1, stuck since early 2024 (the committee wants roughly a dozen organizations using MF2 syntax in production, likely as the bar for Stage 2.7) - i18next-mf2 plugin: v1.0.0, single-digit weekly npm downloads (v2 on messageformat 4.1 since October 2026)
- i18next-icu plugin (MF1): growing from ~100k → ~300k weekly downloads over the past year, the active install base that would eventually migrate
messageformatreference lib: about 340,000 weekly npm downloads, but mostly used as a transitive dependency, not as the direct MF2 adoption signal- FormatJS / react-intl, Lingui, Tolgee: all still MF1 only; no public MF2 roadmaps
- Production case studies: none publicly documented as of May 2026
What MF2 actually changes: side-by-side
The clearest way to see the difference is a real example. Consider a plural message with interpolation.
ICU MessageFormat 1
{
"items": "{count, plural, =0 {You have no items.} one {You have one item.} other {You have {count, number} items.}}"
}The whole message is one curly-brace expression. The variable, the selector, and the variants are all inline.
MessageFormat 2
.input {$count :integer}
.match $count
0 {{You have no items.}}
one {{You have one item.}}
* {{You have {$count} items.}}MF2 splits the message into three explicit parts:
.inputdeclarations name and type the variables (here$countis an integer)..matchdeclares which variable drives selection.- Variants are listed under explicit selector values;
*is the fallback (replaces MF1'sother).
For simple cases the verbosity feels like overkill. For complex cases (gender + plural + format combinations, multiple selectors per message, message reuse with .local declarations), MF2 becomes meaningfully cleaner. Full syntax reference lives in the ICU User Guide for MessageFormat 2.
The npm download story
A direct way to measure i18next-side adoption: compare the official i18next-mf2 bridge, the underlying messageformat reference library, and the established i18next-icu plugin (which implements MF1).
Two things stand out:
messageformathas reach: but mostly as a transitive dependency or in non-i18next ecosystems. Not a direct MF2-on-i18next adoption signal.i18next-icu(MF1) is growing, roughly tripled over the past year, from ~100k to ~300k weekly. The MF1 install base in the i18next ecosystem is healthy and expanding, not shrinking. That's the audience MF2 would eventually need to migrate from.i18next-mf2was at single-digit weekly downloads in May 2026 (47 in the week of October 5). Functionally zero traffic so far, closer to "spec-curious developers" than to "production projects shipping."
Read: the standard exists, the runtime exists, the i18next MF1 install base is healthy and growing, but the i18next side has not started migrating to MF2 yet.
Why adoption is slow
Three reinforcing factors:
- TC39
Intl.MessageFormatis stuck. Per issue #49 on the TC39proposal-intl-messageformat, the committee asked for roughly a dozen organizations to be using MF2 in production before advancing to Stage 2.7. That gating signal hasn't been met. - No major framework default has switched. FormatJS / react-intl are still ICU MessageFormat 1. Lingui is MF1. Tolgee is MF1 in its ICU docs. i18next removed legacy
interpolation.formatin v26 but kept the built-in Formatter, not a MF2 migration. - No competing TMS has shipped MF2 support. Crowdin's blog has no MF2 post (checked May and October 2026). Lokalise's MF1 guide and Phrase's ICU guide do not mention MF2; no MF2 announcement found from either, or from Transifex.
Net: the spec is stable but the gravitational pull toward adoption hasn't started.
Should you migrate to MF2 today?
Most teams: no, not yet.
ICU MessageFormat 1 still works, has wide framework support, has documentation everywhere developers look, and has been battle-tested for over a decade. Until at least one of FormatJS, Lingui, or a major framework defaults to MF2 (or until TC39 moves the proposal past Stage 1), migrating now means owning the rough edges yourself.
Migrate now if you fit one of these:
- Brand-new project. You're starting fresh and don't have an existing message library. Picking MF2 means future-proofing without rewrite cost.
- Heavy use of complex selectors. Gender + plural combinations, nested selectors, multi-variable matching: these are MF1's pain points and MF2's strengths.
- You want to be early. You have the engineering bandwidth to deal with sparse documentation and limited tooling outside i18next (most translation editors and linters only know ICU), and the strategic interest in being ahead.
For everyone else, the right move is: stay on ICU MessageFormat 1, watch the inflection signals, and be ready to migrate when the ecosystem moves.
How Locize handles this today (and tomorrow)
Three things matter for a TMS in this transition:
- Format-agnostic storage today. Locize stores translation messages as text. Whatever format you write (ICU MessageFormat 1, MessageFormat 2, plain interpolation, or anything else) is preserved verbatim through the editor, the CDN, and the API. See supported i18n formats, the pluralization reference, and the full file-format support matrix.
- No vendor lock-in to a specific message format. The
i18next-mf2plugin reads Locize-served messages the same wayi18next-icudoes. When MF2 adoption inflects and you want to migrate, you can update messages in-place in Locize. No TMS change required. - First-class MF2 editor support coming when MF2 is accepted. Internal work on a Locize-side MF2 message handler is already underway. The plan: ship full first-class MF2 support in the editor (syntax-aware editing, variant tooling, type-checked placeholders) when at least one of the inflection signals below triggers (TC39 advances, a major framework defaults to MF2, or a critical mass of i18next users start migrating). No date promised; the trigger is ecosystem-readiness, not a calendar.
In other words, picking Locize today doesn't lock you into MF1 or MF2 specifically. Both work now; first-class MF2 support is on the runway when the ecosystem is ready.
Update (October 21, 2026): MessageFormat 2 is now a project format in Locize: syntax highlighting, the same checks as MessageFormat v1 (argument names, and plural forms that fit each language) and AI translations that keep the syntax and the plural forms of the target language. In the editor, a message is one highlighted text, without separate fields per variant. What changed is in AI translations that respect your i18n format.
What to watch for in 2026–2027
The signals that meaningful adoption is starting:
- TC39
Intl.MessageFormatadvances to Stage 2, and above all to Stage 2.7. Stage 2.7 is where the committee expects roughly a dozen organizations using MF2 in production, so reaching it is the clearest adoption signal. - FormatJS or Lingui ships MF2 as a default (or first-class) option. Either would represent a significant ecosystem signal.
- A major SaaS or e-commerce platform publicly documents a MF2 deployment. "We use MF2 in production at $company", even a single one, would shift the conversation.
- i18next-mf2 weekly downloads cross ~1,000. Mechanical signal: the i18next-side bridge moves from "spec-curious developers" to "real projects shipping."
We'll publish a follow-up post when any of these triggers. For now, this is where things stand.
Frequently asked questions
What is MessageFormat 2 (MF2)?
MessageFormat 2 (MF2) is the new Unicode standard for localized messages, formally `messageformat-2.0` under the Unicode CLDR Technical Committee. It reached Final Candidate status in March 2025 and was refined in LDML 47 and 48 (October 2025). MF2 is designed to replace the original ICU MessageFormat (sometimes retroactively called MF1) with cleaner syntax, explicit declarations for variables and selectors, and better handling of complex multilingual cases like gendered language and nested plurals.
Is MessageFormat 2 ready for production in i18next?
Spec-wise, yes: MF2 is stable. Ecosystem-wise, not yet. The official i18next-mf2 plugin (v2 on messageformat 4.1 since October 2026) had single-digit weekly npm downloads as of May 2026 (47 in the week of October 5, 2026), while the i18next-icu plugin (MF1) grew from roughly 100k to 300k weekly downloads in the year to May 2026 (about 757,000 in October 2026). No major framework (FormatJS / react-intl, Lingui, etc.) has shipped MF2 as default. The TC39 Intl.MessageFormat proposal is stuck at Stage 1 pending production adoption signals. For most teams, ICU MessageFormat 1 remains the practical choice in 2026.
What is the difference between MessageFormat 1 and MessageFormat 2?
MF1 (ICU MessageFormat) puts variables, selectors (plural / select / selectordinal) and formatters inline in one curly-brace expression. MF2 separates variable declarations, selectors, and message variants into a cleaner structure with explicit `.input`, `.local`, `.match` blocks. For simple plurals or interpolation, the two formats are similar. For complex cases (nested selectors, multiple plurals per message, gender + plural combinations), MF2 is significantly more readable and easier to translate.
Should I migrate my i18next project from ICU MessageFormat to MF2?
Most teams should not migrate yet. Until at least one of FormatJS, Lingui, or a major framework defaults to MF2 (or until TC39 Intl.MessageFormat, at Stage 1 since 2022, advances), staying on ICU MessageFormat is safer. The migration is reversible and can be done incrementally with i18next-mf2 alongside i18next-icu, so there is no urgency. If you are starting a brand-new project with very-multilingual edge cases (gender + plural combinations, complex selectors) and accept the early-adopter risk, MF2 is a reasonable choice now.
Does Locize support MessageFormat 2?
Yes. Locize stores translation messages as text: your message format (ICU MessageFormat 1, MessageFormat 2, plain interpolation, anything else) is preserved verbatim. The i18next-mf2 plugin reads Locize-served messages the same way i18next-icu does. There is no vendor lock-in to a specific message format: when MF2 adoption inflects and you want to migrate, you can update messages in-place in Locize without changing your TMS.
When will MessageFormat 2 become widely adopted?
Hard to predict precisely. The signals to watch are: (1) TC39 Intl.MessageFormat advancing beyond Stage 1; the committee said roughly a dozen organizations using MF2 syntax in production will likely be required for Stage 2.7; (2) FormatJS or Lingui shipping MF2 as default; (3) Major SaaS or e-commerce platforms publicly documenting MF2 deployments. None of these have happened as of May 2026. Realistic expectation: meaningful adoption inflection in late 2026 or 2027, mainstream defaulting unlikely before 2028.
Where can I learn the MessageFormat 2 syntax?
The Unicode CLDR working group maintains the specification at messageformat.unicode.org. The most accessible introduction for engineers is Igalia's "MessageFormat 2.0: a new standard for translatable messages" blog post (May 2024). The ICU User Guide has a Java-leaning syntax reference. For JavaScript / TypeScript specifically, the `messageformat@4` npm package is the reference implementation and its README plus tests are useful study material.
Tired of managing translations by hand?
Locize is the translation management backend by the i18next team: CDN delivery, AI translation, in-context editing, no redeploys.
Start your free 14-day trial