v150 · PWA · Installation
Manifest Builder
Build the files needed for a Chrome 150 PWA origin migration. Fill in your new origin, old origin, and app IDs. The builder generates the destination manifest.json with migrate_from, the old origin's /.well-known/web-app-origin-association file with allow_migration, and an optional old-manifest migrate_to hint.
Both sides are required: the destination app declares the old installed app in
migrate_from, and the old origin explicitly authorizes the destination app ID with allow_migration. Chrome currently limits this feature to same-site migrations.
New origin (migration target)
Old origin (migration source)
Serve at:
Optional proactive signal from the old origin. Useful when the old app can still update before redirects take over.
see also
- Verification Checker — validate the same fields before deploying
- Manifest Configuration — field-by-field reference
- ChromeStatus entry
- Chrome Developers — Seamless PWA origin migration
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗