Manifest localization lets one PWA speak multiple languages

Why manifest localization matters

For years, PWAs shipped with a single-language manifest. If you wanted to reach Japanese users, French users, and Chinese users, you either:

• Built three separate PWAs at different origins
• Served language-specific icons and text from JavaScript, which install prompts didn't use
• Ignored the problem and showed English app names globally

Chrome 148 changes this. Manifest localization, implemented by the Microsoft Edge team in collaboration with Chrome, lets your PWA adapt its name, description, icons, and shortcuts to the user's browser language. This reduces friction for global distribution and makes your app discoverable in local search results.

According to the Chrome 148 release notes, this feature "supports localization of manifest members so apps can adapt their names, descriptions, icons, and shortcuts to the user's language and region."

The implementation checklist

Add localized manifest members to your manifest.json:

{
  "name": "My App",
  "name_ja": "マイアプリ",
  "name_zh": "我的应用",
  "description": "A progressive web app",
  "description_ja": "プログレッシブ Web アプリ",
  "description_zh": "渐进式网页应用",
  "icons": [{ "src": "icon.png", "sizes": "512x512" }],
  "icons_ja": [{ "src": "icon-jp.png", "sizes": "512x512" }],
  "icons_zh": [{ "src": "icon-zh.png", "sizes": "512x512" }],
  "shortcuts": [
    {
      "name": "Create new",
      "url": "/create"
    }
  ],
  "shortcuts_ja": [
    {
      "name": "新規作成",
      "url": "/create"
    }
  ]
}

Localization support rubric

Before shipping multilingual manifests, verify:

• [ ] Each language variant has complete translation (name, description, shortcuts)
• [ ] Icons are culturally appropriate (avoid offensive imagery, use regional branding)
• [ ] Shortcuts lead to working pages in that language
• [ ] Your build process validates localized members before deploy
• [ ] You test install prompts in Chrome 148+ on Windows, macOS, and Android with different browser languages

Should you localize?

| Scenario | Recommendation | |----------|----------------| | Single-country launch | Skip localization, optimize for that market | | Multi-regional with distinct branding | Use localization to adapt names and icons | | Global product with universal branding | Localize descriptions, keep name consistent | | Deeply localized apps with region-specific features | Consider separate PWAs per major market |

What developers should do now

1. Audit your PWA's install funnel by geography. If you see high drop-off from non-English users, localization is a high-priority fix.

- Translated app names (keep them short for desktop surfaces) - Culturally appropriate icons (colors, symbols, text) - Translated shortcuts that match your UI

1. Prepare localized assets. You don't need new binaries, but you will need:

1. Test in Chrome 148+. Install prompts respect browser language, not system language. Set Chrome's language to Japanese or Chinese and verify the install prompt shows the localized name.

1. Don't break existing installs. Chrome will fall back to English if localization is missing or malformed. Ship gradually and monitor bounce rates per region.

1. Observe platform adoption. Safari, Firefox, and Edge on Chrome-based browsers may implement this at different times. Feature-detect before gating critical UI on localization.

What this means for distribution

Marketplaces and directories that consume manifest metadata will start seeing localized names and descriptions. Your app's discoverability in non-English search surfaces depends on:

• Complete localized descriptions (not just names)
• Keywords that match regional search intent
• Screenshots that reflect the localized experience

If you're listing your PWA in app marketplaces or PWA directories, update your listings to match the localized manifest. Consistency between install prompts and marketplace headers builds trust.

The next step

Manifest localization is table stakes for global PWAs. The next frontier is runtime localization—adapting your app's content, error messages, and help text to the user's language without full page reloads. The navigator.languages API and service worker localization patterns can help, but they require careful offline design.

Don't let localization be an afterthought. Start with manifest metadata, test your install funnel in multiple languages, and iterate toward a truly global PWA.