iOS TestFlight Public Link

Yes, you can create an iOS TestFlight public link for a private app — and here's how. If you ship a private or internal iOS app, you already know that Apple's default TestFlight flow assumes you either use internal testers (team members) or go through Beta App Review to get a public link. For many teams, that second path is not an option. The good news: you can get a single, shareable link that behaves like a public TestFlight link without submitting your app for review, by automating invitations and TestFlight group assignment with the App Store Connect API.

What Is a TestFlight Public Link?

A TestFlight public link is a URL that, when opened, lets anyone (or anyone you share it with) join your app's beta. In Apple's world, this link is generated inside App Store Connect only for builds that have been submitted to and approved under Beta App Review. Once approved, you can turn on "Public Link" for that build and share it. Testers click, install TestFlight if needed, and get your build. No manual invitation or email step is required from you. For public-facing apps going through beta review, this is the standard path. For private or internal-only apps, this link often does not exist.

Internal vs External Testing Explained

Apple divides TestFlight into two modes: internal and external. Internal testing is for people in your App Store Connect team (developers, admins, etc.). You can add up to 100 internal testers, and they get builds immediately—no Beta App Review, no public link. External testing is for everyone else: clients, beta testers, QA, or early adopters. You can have up to 10,000 external testers, but to give them a classic "public link" experience, your build must pass Beta App Review. Until then, Apple does not offer a public link for external testers; you must add them as users in App Store Connect and then add them to the right TestFlight group. That's the manual workflow that automation tools are built to replace.

Why Apple's Public Links Don't Work for Private Apps

Apple's public link is tied to the external testing workflow and to Beta App Review. If your app is not submitted for that review—because it's private, internal-only, or not yet ready for a public-facing beta—App Store Connect simply does not show the option to enable a public link. You are left with the manual process: add each tester as a user, send the invite, wait for acceptance, then add them to the correct TestFlight group. For a handful of testers that might be acceptable; for dozens or multiple apps, it does not scale. That's why developers look for a way to create a public-style TestFlight link for private apps: one URL to share, with the rest handled automatically.

How to Create a Public TestFlight Link for a Private iOS App

You cannot get Apple's native public link for a private app without going through Beta App Review. What you can do is create a single, shareable invite link that gives you the same outcome: testers open the link, take one action (e.g. enter email), and you automatically send the App Store Connect invitation and add them to TestFlight when they accept. That is done by using the App Store Connect API to automate user creation (or lookup), sending invites, and adding accepted users to the right TestFlight group. A tool like TF Invites does exactly that: you connect your app once, get a private invite page URL, and share that as your "public" TestFlight link. When testers submit their email, the system handles the rest.

Step-by-Step Guide

1. Connect your app. Use an automation product that integrates with App Store Connect via API (e.g. API key + issuer ID + private key). Link the app by App ID so the system can manage testers and TestFlight groups.
2. Create an invite link. Generate a dedicated invite page for that app. This becomes the link you share (e.g. in email, Slack, or on your site)—your de facto TestFlight public link for that build.
3. Share the link. Send the URL to testers. They open it, enter their email (and optionally name). No need for you to add them manually in App Store Connect first.
4. Let automation run. The system sends the App Store Connect invitation email, monitors for acceptance, and adds accepted users to the TestFlight group you configured. Testers receive the standard Apple email and can install via TestFlight as usual.
5. Track and scale. Use the dashboard to see who was invited, who accepted, and who is in TestFlight. Repeat for new builds by keeping the same link or creating new ones per build if you prefer.

Apple Public Link vs TF Invites

When Should You Use Each Option?

Use Apple's public link when your app is in (or will be in) external testing and you are willing to go through Beta App Review. You get an official, anonymous link and minimal setup. Use a TF Invites–style invite link when your app is private or internal-only, when you want to collect emails and control who joins, or when you need one link without manually adding each tester in App Store Connect. Many teams use both: Apple's link for public betas and an automated invite link for private or client-specific builds. Check pricing and TF Invites to see if the automated flow fits your workflow.

FAQ

Can you create a TestFlight public link for a private app?

Apple's native public links only work for apps that have passed Beta App Review. For private apps that have not been submitted for external testing review, you need an automation tool like TF Invites that uses the App Store Connect API to send invitations and add testers to TestFlight groups, then gives you a shareable invite page.

What is the difference between internal and external TestFlight testing?

Internal testing allows up to 100 testers who are part of your App Store Connect team; no Apple review is required. External testing allows up to 10,000 testers but requires Beta App Review and a public link only after approval. For private apps, external public links are not available until you complete that process.

Why don't Apple's public links work for my private iOS app?

Apple's public TestFlight link is only generated for builds that have been submitted to and approved under Beta App Review. If your app is private or you haven't gone through that process, no public link is offered. You must use the API to invite users and add them to TestFlight groups instead.

How does TF Invites create a public-style link for a private app?

TF Invites generates a private shareable URL for your app. You share that link with testers. When they open it, they enter their email. The system then sends the App Store Connect invitation, monitors acceptance, and automatically adds them to your chosen TestFlight group—so you get a single link to share without manual steps.

Do I need to submit my app for Beta App Review to use TF Invites?

No. TF Invites uses the App Store Connect API to invite users and add them to TestFlight groups. It does not require Beta App Review or a public link from Apple. Your app can remain private while you distribute builds to testers via your TF Invites invite page.

Is a TestFlight invite link from TF Invites the same as Apple's public link?

No. Apple's public link is an anonymous, Apple-hosted page that appears only after Beta App Review. TF Invites gives you a dedicated invite page where testers submit their email; then invitations and TestFlight group assignment are automated via the API. You control who gets the link and you get a list of who signed up.