Apple Intelligence doubles its language footprint in iOS 27, bringing on-device translation and Siri AI to more markets

Apple Intelligence expands to 16 languages in iOS 27

Apple's iOS 27 page lists support for 16 languages: English, Chinese (Simplified and Traditional), Danish, Dutch, French, German, and additional languages including Italian, Japanese, Korean, Norwegian, Portuguese, Spanish and Swedish, according to a September 15, 2026 roundup of the iOS 27 language list. An Apple support document dated September 15, 2026 confirms the same set for Live Translation in Messages. The English beta of iOS 27 with Siri AI shipped on September 14, 2026, with broader language availability expected in October.

Practically, writers, editors and translators who carry an iPhone can expect system-level translation of message threads to span European, Nordic and major East Asian languages without leaving the Messages app.

Localised drafts shift upstream

For practitioners who draft on iOS, the merged roll of 16 languages changes how first-pass localisation happens. A translator working from English into Italian or Korean no longer needs a separate translation tab to read a colleague's message; Live Translation in Messages handles the read-through, leaving the human edit for tone and terminology. The same coverage list also implies that on-device rewrite and summary features inherit the same set, so editors reviewing drafts on an iPhone can run system-level passes without round-tripping through a web tool.

Teams that have standardised on Unicode Encoder / Decoder for handling stray characters in pasted copy will find that work slightly easier once the source and target scripts share an Apple-supported translation pipeline.

What's next for supported markets

Apple's support page marks the September 14, 2026 iOS 27 beta as English-only, with broader language support planned for October. A September 15, 2026 analyst note frames the rollout as a potential driver of iPhone upgrades and a possible AI subscription tier, but the underlying platform facts are the same: 16 languages are now listed, with the gap between the English beta and the full multilingual release measured in weeks, not quarters. Teams preparing multilingual documentation should plan to test Live Translation in Messages against their existing terminology lists once the October wave lands, rather than against the September beta.

What to do before October

Three concrete checks are worth queueing up now. First, inventory the languages your team actually edits in and mark which of them appear in the published 16-language list, so the October rollout can be tested in priority order. Second, re-run existing translation memory through Unicode Encoder / Decoder and Binary To Text to catch encoding drift introduced when drafts move between iOS, desktop browsers and older CMS fields, particularly for Simplified and Traditional Chinese strings.

Third, audit paste behaviour in your content platform now, since broader multilingual input usually exposes fonts and bold-styling quirks; the How to Get Bold Text That Works Anywhere You Paste It and How to Generate Bold Text You Can Paste on Social Media walkthroughs are worth re-reading before the multilingual iOS 27 build ships. If your team relies on quick heading-style checks across locales, a Title Case Converter (AP, APA, Chicago) is the simplest way to keep capitalization rules consistent once non-English drafts start circulating.

A final, qualitative follow-up: confirm with your device fleet whether the October multilingual iOS 27 build is gated to specific iPhone models before issuing guidance to editors.