Progressive Web Apps (PWAs) are increasingly treated like first-class applications by users and browsers alike. That makes changing a PWA\u2019s domain (origin) a high\u2011risk move if it\u2019s not handled correctly. With changes available from Chrome 150 onward, it\u2019s now possible to migrate a PWA to a new same\u2011site origin with minimal disruption and without forcing users through a painful reinstall.<\/p>\n
This guide explains how origin migration works for PWAs, what \u201csame\u2011site\u201d means in practice, and how business owners and developers can plan and execute a smooth transition when rebranding, restructuring infrastructure, or consolidating domains.<\/p>\n
For many organizations, a PWA is more than a website\u2014it\u2019s a core customer touchpoint comparable to a native mobile app. Installed PWAs live on users\u2019 devices with their own icon, offline capabilities, and stored data. When you change domains, that installed experience typically does not follow automatically, creating serious risks:<\/p>\n
Until now, changing a PWA\u2019s origin meant effectively asking every user to reinstall the app under the new domain. For businesses operating at scale, that\u2019s a significant barrier and can translate into measurable revenue loss.<\/p>\n
Common business and technical scenarios that require a PWA origin change include:<\/p>\n
myapp-old.com<\/code> to myapp.com<\/code> after an acquisition or branding update.<\/li>\n- Infrastructure changes:<\/strong> Consolidating multiple subdomains (e.g.,
app.example.com<\/code> to pwa.example.com<\/code>).<\/li>\n- Hosting and architecture upgrades:<\/strong> Migrating to a new hosting provider, CDN, or multi-region architecture that uses a new origin.<\/li>\n
- Security and compliance:<\/strong> Shifting from legacy or shared domains to hardened, dedicated origins.<\/li>\n<\/ul>\n
\nWith Chrome 150 and later, you can migrate a PWA between same-site origins while preserving the installed app, reducing friction for users and protecting your active install base.<\/p>\n<\/blockquote>\n
\nUnderstanding Same-Site Origins and PWA Behavior<\/h2>\n
Origin migration support is powerful but intentionally constrained for security and privacy reasons. To use it correctly, you need a clear understanding of how browsers define \u201csame-site\u201d and how that affects your migration strategy.<\/p>\n
What Does \u201cSame-Site\u201d Mean?<\/h3>\n
In browser terms, the \u201csite\u201d is defined by the scheme<\/strong> (protocol), registrable domain<\/strong>, and port<\/strong>. Two origins are considered same-site if they share the same registrable domain and scheme, even if the subdomains differ. For example:<\/p>\n\nhttps:\/\/app.example.com<\/code> and https:\/\/pwa.example.com<\/code> are same-site.<\/li>\nhttps:\/\/example.com<\/code> and https:\/\/www.example.com<\/code> are same-site.<\/li>\nhttps:\/\/myapp.com<\/code> and https:\/\/myapp.net<\/code> are not<\/strong> same-site.<\/li>\nhttp:\/\/example.com<\/code> and https:\/\/example.com<\/code> are different due to the scheme.<\/li>\n<\/ul>\nChrome\u2019s PWA origin migration feature currently applies only to moves where the old and new origins are same-site. Cross-site migrations (for example, from myapp-old.com<\/code> to myapp.com<\/code>) still require a more traditional migration strategy with careful redirects and user communication.<\/p>\nHow PWAs Are Tied to an Origin<\/h3>\n
Every PWA is tightly coupled to the origin where it\u2019s installed:<\/p>\n
\n- The service worker<\/strong> is scoped to a specific origin and path.<\/li>\n
- The web app manifest<\/strong> (
manifest.json<\/code>) is fetched and validated relative to that origin.<\/li>\n- Persistent storage (IndexedDB, Cache Storage, localStorage) is partitioned by origin.<\/li>\n<\/ul>\n
Historically, this meant that moving to a new origin effectively created a \u201cnew app\u201d from the browser\u2019s perspective. Chrome 150 introduces mechanisms to treat certain origin changes as migrations instead of replacements, within strict security boundaries.<\/p>\n
\nHow Seamless PWA Origin Migration Works in Chrome 150+<\/h2>\n
At a high level, seamless migration allows Chrome to:<\/p>\n
\n- Recognize that a PWA installed from one origin is now available at another same-site origin.<\/li>\n
- Update the installed app to use the new origin instead of uninstalling and reinstalling.<\/li>\n
- Preserve user-facing aspects such as the app icon, name, and presence in app launchers.<\/li>\n<\/ol>\n
This process minimizes disruptions for users and helps maintain continuity during technical or branding changes.<\/p>\n
Key Requirements for Migration<\/h3>\n
To take advantage of seamless origin migration, your setup should satisfy several conditions:<\/p>\n
\n- Same-site origins:<\/strong> Both old and new origins must share the same registrable domain and scheme (for example, from
https:\/\/app.example.com<\/code> to https:\/\/pwa.example.com<\/code>).<\/li>\n- Equivalent PWA identity:<\/strong> The web app manifest should represent the same app identity (same or consistent
name<\/code>, short_name<\/code>, and id<\/code> values).<\/li>\n- Valid HTTPS configuration:<\/strong> Both origins must serve content over HTTPS with correctly configured certificates.<\/li>\n
- Thoughtful redirect strategy:<\/strong> Requests to the old origin should be redirected to the new origin without breaking service worker updates.<\/li>\n<\/ul>\n
Chrome uses a combination of manifest data, user interaction history, and network behavior to determine whether it should treat the new origin as a continuation of the existing app.<\/p>\n
Data and Service Worker Considerations<\/h3>\n
Even when the migration is seamless from the user\u2019s perspective, developers must carefully manage:<\/p>\n
\n- Service worker scripts:<\/strong> Ensure the service worker at the new origin is compatible with the previous version so cached assets and queued requests are handled correctly.<\/li>\n
- Stored data:<\/strong> Plan for data migration if you use origin-specific keys or back-end APIs tied to the old domain.<\/li>\n
- Offline behavior:<\/strong> Test the PWA\u2019s offline functionality post-migration to ensure it still works as expected.<\/li>\n<\/ul>\n
In many same-site migrations, user data stored in IndexedDB or Cache Storage will not automatically \u201cmove\u201d between origins. You may need to implement client- or server-side strategies to reconcile or re-fetch necessary data under the new origin.<\/p>\n
\nPractical Migration Strategy for Business and Development Teams<\/h2>\n
A successful PWA origin migration is a coordinated effort involving product owners, developers, DevOps, and sometimes marketing or legal teams. Below is a practical blueprint you can adapt.<\/p>\n
1. Plan the Migration<\/h3>\n
Before touching production, map out the full scope:<\/p>\n
\n- Confirm that the old and new origins qualify as same-site.<\/li>\n
- Audit all PWA-related assets: manifest, service worker, icons, and entry points.<\/li>\n
- Inventory dependencies on the old domain in your back-end services and third-party integrations.<\/li>\n
- Define success metrics such as retained daily active users (DAU) or error rates.<\/li>\n<\/ul>\n
At this stage, align business stakeholders on timing (for example, during off-peak hours) and communication plans if user-facing messaging is needed.<\/p>\n
2. Prepare the New Origin<\/h3>\n
Next, bring the new origin to a production-ready state:<\/p>\n
\n- Configure DNS and TLS\/SSL certificates for the new subdomain or hostname.<\/li>\n
- Deploy the PWA codebase to the new origin, ensuring consistent build and asset paths.<\/li>\n
- Serve a valid web app manifest<\/strong> at the new origin with an appropriate
id<\/code> and name matching the existing PWA identity.<\/li>\n- Register a service worker<\/strong> with compatible cache strategies and update logic.<\/li>\n<\/ul>\n
Use staging environments that mirror production as closely as possible to test installation, updates, and offline behavior from the new origin.<\/p>\n
3. Configure Redirects and Routing<\/h3>\n
How you implement redirects from the old to the new origin can affect migration quality:<\/p>\n
\n- Use HTTP 301 or 308 redirects<\/strong> where appropriate to signal permanent moves.<\/li>\n
- Maintain consistent paths where possible (for example,
\/app\/<\/code> on both origins) to simplify routing.<\/li>\n- Avoid redirect loops or mixed-content scenarios that might interfere with service worker registration.<\/li>\n<\/ul>\n
Ensure that the service worker on the old origin can still update during the transition window so users receive any final migration-specific logic you may deploy.<\/p>\n
4. Test Across Devices and Chrome Versions<\/h3>\n
Because origin migration support is tied to specific browser versions, robust testing is crucial:<\/p>\n
\n- Test on Chrome 150 and later<\/strong> on both desktop and mobile platforms.<\/li>\n
- Validate that existing installations on the old origin behave as expected when the user next opens the app.<\/li>\n
- Check that the PWA appears correctly under the new origin in the browser\u2019s installed apps or app launcher UI.<\/li>\n<\/ul>\n
For users on older browsers or other engines (Safari, Firefox, Edge variants), design a fallback experience using standard redirects and in-app messaging to guide them to the new origin.<\/p>\n
\nBusiness Benefits of Seamless PWA Origin Migration<\/h2>\n
When implemented correctly, same-site origin migration provides tangible advantages for both technical teams and the business as a whole.<\/p>\n
Reduced User Friction and Churn<\/h3>\n
Users keep their installed app, icon, and workflow without needing to reinstall or search for a new URL. This is especially important for:<\/p>\n
\n- Subscription-based services where user retention is critical.<\/li>\n
- Internal enterprise PWAs deployed across large workforces.<\/li>\n
- Consumer apps with high engagement and brand loyalty.<\/li>\n<\/ul>\n
By avoiding forced reinstallation, you preserve engagement metrics and minimize support tickets related to \u201cmissing\u201d apps.<\/p>\n
More Flexibility in Infrastructure and Hosting<\/h3>\n
From a technical and hosting perspective, seamless migration enables you to:<\/p>\n
\n- Reorganize subdomains to better reflect architecture changes.<\/li>\n
- Move to new hosting providers or CDNs under the same main domain with less risk.<\/li>\n
- Adopt new security or performance best practices without sacrificing user continuity.<\/li>\n<\/ul>\n
For organizations continuously optimizing their web hosting<\/strong> and performance<\/strong> stack, origin migration support reduces the \u201clock-in\u201d effect that PWAs previously created at the domain level.<\/p>\n
\nConclusion<\/h2>\n
Changing the origin of a PWA has traditionally been a high-stakes operation, often resulting in lost installs, broken experiences, and increased user support. With features introduced in Chrome 150, businesses can now migrate PWAs between same-site origins in a way that feels seamless to users, provided they plan carefully and respect the underlying security model.<\/p>\n
For business owners, this unlocks more strategic freedom to rebrand, consolidate domains, or modernize infrastructure. For developers, it offers a clear framework for executing technically sound migrations that preserve user trust and application integrity.<\/p>\n
\n