App Store Link Not Opening in Instagram? How to Fix

What the Visitor Sees

The failure looks different depending on the app and the version, which is part of why it goes unnoticed. On an iPhone it is usually one of three things:

• Nothing happens. The tap registers and the page stays where it was. No error, no store.
• A blank page. A new white tab opens inside the app and never loads anything.
• It stalls. The in-app browser starts loading the App Store link and never finishes, or shows the store’s web page instead of handing off to the App Store app.

Whichever it is, the visitor who wanted your app now has to find it in the App Store by hand. Some do. The rest close the tab, and nothing in your analytics says why.

Why It Happens: the In-App Browser

Instagram, TikTok, Threads, Facebook and X do not hand links to Safari or Chrome. They open them in a browser built into the app. That browser looks like Safari, but the app decides what a tap on an App Store or Google Play link does, and it can decide to do nothing.

It also changes. In a 2023 thread on Apple’s developer forums, an App Store link in an Instagram profile loaded and then stalled, while the same link opened fine after Open in external browser; the poster saw the same on Facebook. In a 2026 thread, developers reported that after an Instagram update, App Store links on iPhone stopped doing anything at all — “no error, no page” — while Google Play links on Android kept working. One later reply says a newer Instagram release fixed it; nobody else in the thread confirms it.

Your link is not broken. It is opening inside an app that decides, release by release, whether a store link is allowed to leave.

That is the practical lesson: you cannot test this once and move on. A link that worked in last month’s Instagram can be dead in this month’s.

Threads on iPhone: Every Way Out We Tried

We measured Threads ourselves, on Threads 446 and iOS 27, because a page can try several tricks to leave an in-app browser on its own. From a page opened inside Threads, we tried:

• a plain App Store link and the itms-apps:// scheme: nothing happened;
• the x-safari-https:// scheme, as a link, through window.open and as a page redirect: nothing, or a blank tab inside Threads;
• googlechrome:// and instagram://extbrowser: a system dialog instead of a way out.

None of them reached Safari or the App Store. The one exit that worked was the one a person has to take: the round ⋯ button at the top right, then Open in external browser. Once the page is in Safari, the App Store link opens as it should.

Instagram, TikTok, Facebook and X we have not measured the same way, so we only repeat what developers report about them. Their in-app browsers have a similar menu, but its label and position vary by app and version.

How a Visitor Gets Out

If you are the one stuck on a page in Instagram, TikTok or Threads, any of these works:

• Open the browser menu. Tap ⋯ and choose Open in external browser, Open in browser or Open in Safari, whichever your app shows. Then tap the store button again.
• Copy the link. Copy it from the same menu, paste it into Safari or Chrome, and tap the store button there.
• Search the store. It works, and it is exactly the step where app owners lose people.

The catch is that almost nobody knows the first two exist. Nothing on the page says the exit is behind ⋯.

What You Can Do as the App Owner

• Link to your own page, not straight to the store. A bare apps.apple.com link in a bio or a post can only work or fail. A page on your site with a Download button gives you somewhere to react when the tap goes nowhere.
• Use the app’s own exit where one exists. Instagram has a URL scheme, instagram://extbrowser, that asks it to open a page in the phone’s browser. It is the accepted answer in the developer thread above. It only works in Instagram, and it is worth re-testing after Instagram updates.
• Be careful with smart links and redirect pages. They send every visitor through another company’s domain and use the same handful of tricks. Where an app has no exit that works from code, as on Threads for iPhone, a redirect cannot invent one either.
• When nothing works, show the way out. If the tap left the visitor on your page, tell them exactly which button to press: the ⋯ menu and the item that opens the page in the real browser. Add a Copy link button as a backup.

The last two are what we built Overlay to do, first for our own app. It is one script on your site. In Safari and Chrome it does nothing. Inside an in-app browser it waits for a tap on an App Store or Google Play link; it tries the app’s own exit where there is one, like Instagram’s, and on Android it usually tries to open the store directly. If the visitor is still on your page after that, it points at the ⋯ menu, names the item to tap and offers Copy link. Your links stay as they are, and Overlay is free.

Test Your Own Link in Five Minutes

1. Put the link where your audience will meet it: a post, a story, a DM to yourself, the bio.
2. Open it on an iPhone and on an Android phone, from inside each app you post to.
3. Tap your Download button and note what you see: the store, nothing, a blank tab, or the store’s web page.
4. Repeat after the app updates. The behaviour changes between releases without notice.

If any app gives you anything other than the store, every visitor from that app gets the same. That is the traffic worth fixing first, and the Overlay page has a live demo of what they would see instead.