v147 · PWA · Web APIs
Compatibility Lab
Validates the current PWA origin migration handshake: the destination manifest's migrate_from entry, the old origin's /.well-known/web-app-origin-association file with allow_migration, optional migrate_to signaling from the old manifest, and redirect-safe install_url handling.
API probes
Origin pair validator
Validate migration handshake
Use bare origins, then choose the handshake options Chrome validates. The generated JSON shows the destination manifest, the old-origin association file, and the optional old manifest signal.
Enter origins and validate.
new origin — manifest.json
Enter origins and click Validate
old origin — /.well-known/web-app-origin-association
Enter origins and click Validate
old origin — optional manifest.json
Enter origins and click Validate
Fallback pattern
/* Destination app manifest: declares the predecessor */
{
"id": "https://files.example.com/app/",
"start_url": "https://files.example.com/app/index.html",
"migrate_from": [{
"id": "https://drive.example.com/",
"behavior": "suggest",
"install_url": "https://drive.example.com/install.html?noredirect=true"
}]
}
/* Old origin: confirms the destination app may migrate the install */
// https://drive.example.com/.well-known/web-app-origin-association
{
"https://files.example.com/app/": {
"allow_migration": true
}
}
/* Optional old manifest: proactively points users to the destination */
{
"id": "https://drive.example.com/",
"migrate_to": {
"id": "https://files.example.com/app/",
"install_url": "https://files.example.com/install.html?from=legacy"
}
}
references
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗