Firebase Dynamic Links shutdown: what still works in October 2026
Google shut Firebase Dynamic Links down on 25 August 2025. Fourteen months on, some old page.link links still redirect, apps can still open from them, and email sign-in links work after an SDK upgrade. Everything else is gone. A dated status table, with sources.
The short answer: Firebase Dynamic Links (FDL) shut down on 25 August 2025, according to Google's deprecation FAQ. You can't create links, read their analytics or get a deep link through an install any more. Three things still work in October 2026: some old short links still redirect to their fallback, apps that keep the page.link domain in their build still open from a tap, and Firebase Auth email links work once you upgrade the Auth SDK.
This post is the status page: what still works, what doesn't, and how long you can count on each part. If something is failing right now and you want to know what an error means, read page.link errors after the shutdown. If you're planning the move, the page.link migration checklist has the steps.
Status on 24 October 2026
| Part of FDL | Status | How long it lasts |
|---|---|---|
| Creating links (REST API or in-app SDK calls) | Gone: HTTP 400 or 403 | Permanent |
| Link Stats API (analytics) | Gone: HTTP 400 or 403 | Permanent |
| Deep link through an install (deferred) | Gone: the SDK returns empty data | Permanent |
Long links (?link=…&apn=…) |
HTTP 400, "Invalid Dynamic Link" | Permanent |
| Old short page.link links | Some redirect to the old fallback, the rest return 400 or 404 | Google can stop the redirects at any time |
page.link's assetlinks.json and apple-app-site-association |
Still served | No date given, no promise |
| An installed app opening from an old link | Works if the build keeps the page.link domain | As long as the files above are served |
| Your own custom FDL domain | Yours to point at a new provider | Permanent, it's your domain |
| Firebase Auth email links | Work after an SDK upgrade, on a Firebase Hosting domain | Supported by Google |
| Link data in the Firebase console | Marked for deletion on 25 August 2025 | Don't count on it |
The rows that say "Gone" come from Google's FAQ. The rows about what still happens on page.link come from our own requests, described below. Google's FAQ says every link "will return a HTTP 404 status response", but that's not what we see.
What Google says happened on 25 August 2025
Google's FAQ is the primary source, and it's short on the main points:
- Links: "All links served by Firebase Dynamic Links (both hosted on custom domains and page.link subdomains) will stop working."
- page.link domains: once the service shut down, "any .page.link domains will no longer be available." You can't keep or transfer one.
- APIs: all requests to the Short Links and Link Stats endpoints "will return a 400/403 HTTP Status response." The errors began gradually on 25 August 2025 and rose to 100% after that date.
- Data: "Your domain and link metadata will be marked for deletion on August 25th, 2025", and URL prefix domains are deleted automatically after it.
- Crashes: "The SDKs themselves will not cause your app to crash." Your code still has to handle the empty answers.
Firebase's Dynamic Links docs page still says the service "will be shutting down soon", even though the FAQ gives the date. Go by the FAQ.
What old page.link links return (24 October 2026)
We requested 108 real short page.link URLs with curl, without following redirects. Apps had published them on their websites, and some we found in web archives:
| Response | Links | What a person sees |
|---|---|---|
302 to the old fallback |
58 | The web page or the store listing, never the app screen |
400, "Invalid Dynamic Link" |
31 | An error page |
404, "Dynamic Link Not Found" |
19 | An error page |
A made-up code on five page.link domains returned 404, and a long ?link=…&apn=… link on the same domains returned 400. Run the same check on your own links:
curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' https://yourapp.page.link/abcA 302 here is a plain redirect. It doesn't open your app or carry the link through an install, and Google gives no date for when it stops. Treat it as borrowed time. The free page.link checker sorts a long list of old links for you. It flags the Firebase ones, reads the destination out of every long link, and marks the short links whose destination only Firebase knew.
Why installed apps can still open from page.link
This part surprises people. On 24 October 2026, page.link still served assetlinks.json (Android) and apple-app-site-association (iPhone) for the five apps we checked, with each app's own package name, fingerprints and Apple app ID. Apple's own association-file CDN, which iPhones read instead of your server, also still held a copy.
So a phone whose app build still lists yourapp.page.link in its intent filter or Associated Domains opens the app on a tap. The tap never reaches Google's redirect. What happens next depends on the code in the app:
- The old Firebase SDK asks Google what the link means and gets nothing back. Google's table says Android's
getDynamicLinkreturns "a success response, but FDL data will be empty", and iOS gets "an FDL object… with empty data" on first open and an error on reopen. The app opens on its home screen. - Code that reads the URL itself still works. A long link carries its destination in the
link=parameter. A short link can be looked up in your own records by its code. That's how Strait handles it: the SDK readslink=on the phone or looks the code up in your workspace. The page.link guide in our docs shows the setup. It has unit tests in every SDK but has not yet been tested on real phones, so test it on yours first.
None of this helps someone who doesn't have your app. They get whatever Google answers, and no provider can change that, because Google owns the page.link domain.
What you can still rescue
Your custom domain. If FDL ran on a domain you own (links.yourapp.com), point it at a new provider and recreate the same paths, and the old links work again. The FAQ adds one warning: if Firebase Hosting served that domain, the Dynamic Links rewrite rules in firebase.json may still send those paths to FDL, so update them and redeploy Hosting first.
Destinations of old links. Long links contain theirs. For short links, use your own database, analytics exports or old campaign sheets. While Google still redirects a code, its 302 shows the fallback URL, but that's the fallback, not necessarily the in-app path. The console data is marked for deletion, so don't plan around it.
Email sign-in, password reset and verify-email links. Google's FAQ says these "will continue to work" if you move to the latest Firebase Authentication SDKs, and that they stop working in older app versions. The migration guides name the versions: Android needs Firebase Authentication 23.2.0 or later (BoM 33.9.0+), per the Android guide, and iOS needs 11.8.0 or later, per the iOS guide. Links move to your project's Firebase Hosting default domain, or to a custom Hosting domain set with linkDomain in ActionCodeSettings. This stays a Firebase fix. Switching deep linking providers doesn't touch it.
What Google recommends instead
Firebase's own migration guide points to plain Android App Links and iOS Universal Links, with Firebase Hosting serving the two association files. It also lists what you lose. App Links and Universal Links won't provide "a continuation of their user journey after downloading, installing and opening the app for the first time." In other words, no deferred deep links. If invites, referrals or ads need the right screen after an install, you need a service or your own build for that part. Deferred deep linking explained covers how it works on each platform.
Whichever way you go, check the new domain's files before you ship: the AASA validator and the assetlinks.json checker fetch them the way the phones do. If links open the browser afterwards, see Universal Links not opening: 12 causes and Android App Links verification failed.
Frequently asked questions
When did Firebase Dynamic Links shut down?
On 25 August 2025. Google's deprecation FAQ gives that date for the shutdown of links, the Short Links API and the Link Stats API. API errors started gradually on that day and reached 100% afterwards.
Do page.link links still work?
Partly. On 24 October 2026, 58 of the 108 short page.link links we tested still redirected to their old fallback. The rest returned 400 or 404. No redirect opens the app or survives an install, and Google can stop them at any time.
Can I keep or transfer my page.link domain?
No. Google's FAQ says page.link domains are no longer available after the shutdown. Only links on a custom domain you own can be brought back, by pointing that domain at a new provider.
Will my app crash because of the shutdown?
Google says the SDKs themselves won't crash your app. They return empty data or an error instead. A crash comes from your own code assuming a link is present, so make the empty case safe.
Do Firebase Auth email links still work?
Yes, after you upgrade: Firebase Authentication 23.2.0+ on Android and 11.8.0+ on iOS. The links then use a Firebase Hosting domain instead of Dynamic Links. Older app versions lose these features.
Sources and how we checked
- Google, Firebase Dynamic Links deprecation FAQ: the 25 August 2025 date, links stopping, page.link domains, the 400/403 API responses and their gradual start, metadata deletion, the
firebase.jsonrewrite note, the per-SDK table and the no-crash note. Read on 24 October 2026 (page marked last updated 22 October 2026). - Google, Dynamic Links docs (still says "shutting down soon") and Migrate from Dynamic Links to App Links & Universal Links (no continuation after install). Read on 24 October 2026.
- Google, Firebase Auth email link migration for Android and iOS: SDK versions, Hosting domains,
linkDomain. Read on 24 October 2026. - Our own requests on 24 October 2026 with
curl: 108 short page.link URLs (58302, 31400, 19404); made-up codes and long links on five page.link domains (404and400);assetlinks.jsonandapple-app-site-associationon the same five domains (all200, with each app's IDs); and Apple's association CDN for one of them (200, with the app ID). - How the Strait SDK reads old page.link links, and what is still untested, as written in our page.link docs.