Firebase Dynamic Links converter
Firebase Dynamic Links shut down on 25 August 2025. This converter reads long-form FDL URLs, explains each parameter (link, apn, ibi, isi, efr, st, sd, si), shows where it goes in SwiftURL, and exports a CSV for SwiftURL Bulk Link Import. It runs in your browser and sends nothing anywhere.
One FDL URL per line, up to 100. Everything runs in your browser, nothing is sent anywhere.
linkCSVBecomes the SwiftURL destination URLstCSVMaps to the link titleapn · ibi · isiDomainSet once in your domain deep-link settingsefrBuilt inSwiftURL routes directly by defaultSwiftURL is a direct replacement for the core of Firebase Dynamic Links: deep links, deferred deep linking, and short links, on a branded domain you own, with analytics and governance included.
See the migration
Google shut Firebase Dynamic Links down on 25 August 2025, and every link it served, on page.link, on app.goo.gl, and on custom domains, stopped resolving. If those links are sitting in old emails, push notifications, QR codes, and app invites, they now lead nowhere. Migrating them means understanding what each one was actually doing, and that information lives in the long-form FDL URL.
An FDL packs its behaviour into query parameters. The link is the destination your app opened. The apn, ibi, and isi named your Android package, iOS bundle, and App Store ID, so the link knew which app to open or which store to fall back to. The efr flag decided whether to show the app preview page, and st, sd, and si set the social preview title, description, and image. The converter above reads each one and tells you where it belongs in SwiftURL.
The mapping is cleaner than it looks. Your app identifiers, the old apn, ibi, and isi, are configured once in your SwiftURL domain deep-link settings, not repeated on every link, and SwiftURL generates and serves the association files that make Universal Links and App Links resolve. Each link then only needs its destination, which is the old link value. That is why the CSV this tool produces has a destinationUrl column and an optional title from the social preview: those are the per-link fields. Set the app configuration once, upload the CSV, and every link is recreated on your own domain.
The output is shaped exactly for SwiftURL Bulk Link Import: a header row of destinationUrl, slug, title, tags, utmSource, utmMedium, utmCampaign, then one row per link, up to a hundred at a time. Every destination is safety-checked as it is created. If you are weighing the move, the Firebase Dynamic Links comparison covers what carries over and the deferred deep linking page covers the install-survival behaviour FDL was known for.
Firebase Dynamic Links stopped working on 25 August 2025, so existing page.link and app.goo.gl URLs no longer resolve. You need a replacement covering deep links, deferred deep linking, and short links on a domain you control. This tool reads your old FDL parameters and gives the equivalent SwiftURL setup.
link is the destination your app opens; apn, ibi, and isi identify your Android package, iOS bundle, and App Store ID; efr controls the app preview page; and st, sd, si set the social preview title, description, and image. The converter explains each parameter it finds.
Yes. Paste up to 100 long-form FDL URLs, one per line, and the tool produces a CSV shaped exactly for SwiftURL Bulk Link Import, with a destinationUrl column and optional title. Upload it and every link is created and safety-checked in one pass.
A short page.link URL carries no parameters in the address itself; they lived on Firebase servers, now shut down. Paste the long-form FDL URL, the one with link, apn and similar query parameters, and the converter reads them directly with no network call.
They configure your domain once, not each link. In SwiftURL you set your Android package, iOS bundle, and App Store ID in the domain deep-link settings, and SwiftURL serves the association files. See deep linking.