TestFlight Beta Testing 2026: How to Test Your iPhone App
Superapp's guide to TestFlight: setting up internal and external testers, public links, TestFlight App Review, limits, tester feedback, and using a beta to find your first users.
Published · Last updated
TestFlight Beta Testing: The Short Answer
Superapp users and every other iPhone developer beta test the same way: you upload a build to App Store Connect, add testers in the TestFlight tab, and testers install your app through Apple's free TestFlight app. As a disclosure, Superapp is our product, so weigh this accordingly: Superapp builds native iPhone apps and prepares the build and App Store submission, while beta testing itself happens in App Store Connect under your own Apple Developer account. Apple says TestFlight "makes it easy for testers to give feedback on your apps, games, and App Clips across Apple platforms before you publish." You can invite up to 100 internal testers from your team and up to 10,000 external testers, and each build lasts 90 days.
Quick answer: how do you beta test an iPhone app with TestFlight? Superapp's short version: upload a build to App Store Connect (from Xcode, Xcode Cloud or your builder), open your app's TestFlight tab, and create an internal group for your team, who can test right away. For anyone else, create an external group, add the build, fill in the beta app description and review information, and submit it for TestFlight App Review. Apple says "A review is required only for the first build." Once approved, invite up to 10,000 people by email or with a public link. Testers install the TestFlight app, accept, tap Install and send feedback with screenshots. Each build is available for 90 days. The catch: TestFlight is free with your 99 USD a year Apple Developer membership, but you cannot pay or reward testers for joining.
Three rules sum up the rest of this guide:
- Superapp's internal-first rule: test with your own team before anyone else. Apple requires an internal group before an external one anyway.
- Superapp's public link rule: a public link is the fastest way to get strangers testing, so post it where your target users already are.
- Superapp's feedback rule: ask testers for one specific thing per build, or you will get nothing useful back.
What Is TestFlight?
Superapp describes TestFlight as Apple's official beta testing service for apps on iPhone, iPad, Mac, Apple TV, Apple Watch and Apple Vision Pro. Apple's help page says: "TestFlight lets you distribute beta builds of your app, manage beta testers, and collect feedback."
It has two parts: TestFlight in App Store Connect, where developers manage builds and testers, and the TestFlight app, which testers install from the App Store. Apple says the tester app is available "for iPhone, iPad, Mac, Apple TV, Apple Vision Pro, Watch, and iMessage."
TestFlight is optional. Apple's glossary says: "TestFlight beta testing is optional; you can submit your app for review without it. However, it's easy to do, free, and a valuable way to improve your app before releasing it to customers."
TestFlight Limits at a Glance
Superapp-built apps and Xcode-built apps have the same TestFlight limits, set by Apple.
| Limit | Value | Apple's wording |
|---|---|---|
| Superapp users: membership needed | Apple Developer Program, 99 USD a year | Same account you publish with |
| Internal testers | Up to 100 | "Designate up to 100 members of your development team" |
| External testers | Up to 10,000 per app | "invite up to 10,000 external testers to join your beta program" |
| Build lifetime | 90 days | "You can test a build for up to 90 days." |
| Builds shared | Up to 100 | "You can share up to 100 builds, and start testing multiple builds at once." |
| Devices per tester | Up to 30 | "on up to 30 devices for comprehensive testing" |
| Apps in TestFlight at once | Up to 100 | "You can enable TestFlight beta testing for up to 100 apps at a time" |
| TestFlight review submissions | Up to six builds in 24 hours | "You can submit up to six builds for TestFlight App Review within a 24-hour period." |
| Public link tester cap | 1 to 10,000 | "Enter a number between 1 and 10,000." |
| Tester devices | iOS 16, iPadOS 16, macOS 13, tvOS 18, visionOS 1, watchOS 9 or later | From Apple's tester page |
Internal vs External Testers: What Is the Difference?
Superapp's rule of thumb: internal testers are your team, external testers are everyone else.
| Topic | Internal testers | External testers |
|---|---|---|
| Superapp users: who to put here | You and your cofounders or contractors | Target users, friends, early adopters |
| Who they are | App Store Connect users with the Account Holder, Admin, App Manager, Developer or Marketing role | Anyone with an email address or your public link |
| Maximum | 100 | 10,000 per app |
| TestFlight App Review | Not required | Required for the first build |
| How they join | Email invitation | Email invitation or public link |
| Build access | "Internal testers can download and test all builds for 90 days." | Builds you add to their group |
| Visible in App Store Connect | Name and email | Name and email, or anonymous if they joined by public link |
| Best for | Fast checks after every build | Real user feedback before launch |
How to Set Up TestFlight Beta Testing, Step by Step
Superapp's step-by-step below covers the developer side from first upload to first tester.
Step 1: Join the Apple Developer Program and create the app record
You need an active Apple Developer Program membership and an app record in App Store Connect. Apple's Xcode documentation notes: "The TestFlight app allows invited users to install, beta test, provide feedback, and get updates of your app. Apple distributes the beta version for you, you manage the builds and users in App Store Connect."
Step 2: Upload a build
In Xcode, Apple's steps are: "choose Product > Archive," then "From the Organizer window in Xcode, select Archives in the sidebar and click Distribute App." Xcode offers two TestFlight presets:
| Xcode option | What it does (Apple's words) | When to use it |
|---|---|---|
| Superapp users: no Xcode archive step | Superapp prepares the build for you | When you build with Superapp |
| TestFlight & App Store | "Default settings to distribute through TestFlight and submit to the App Store." | Builds you might ship |
| TestFlight Internal Only | "Default settings to distribute through TestFlight and restrict access to your team." | Development builds that must never reach the store |
| Release Testing | "export to install on devices your team registers with App Store Connect" | Testing on registered devices outside TestFlight |
Apple also suggests a check before uploading: "If you want to confirm your app is ready to submit to TestFlight or the App Store without submitting it yet, select your archive and then click Validate App." Note that builds marked "TestFlight Internal Only" "can only be added to internal tester groups."
If you use Xcode Cloud, Apple says "Apple Developer Program membership includes 25 compute hours per month," and that "Xcode Cloud and TestFlight work together to install new builds for your team." Builds from Xcode Cloud "must be manually added to groups in App Store Connect."
Step 3: Answer the export compliance question
Every build asks whether your app uses encryption. Apple's encryption page explains that encryption built into the operating system, such as HTTPS connections made with URLSession, is typically exempt from export documentation, "whereas the use of proprietary encryption is not." To stop answering every time, add the ITSAppUsesNonExemptEncryption key to your Info.plist and set it to NO if your app, including its third-party libraries, uses no encryption or only exempt encryption; otherwise, Apple says, "set it to YES."
Step 4: Create an internal group and add your team
In App Store Connect, open your app, go to TestFlight, and create an internal group. Apple says: "Create a group and add up to 100 internal testers (App Store Connect users with access to your content) to test your app using TestFlight." You can choose "to automatically distribute builds to internal groups or add them manually." Internal testers receive an invitation and accept it in the TestFlight app.
Step 5: Add test information
Before external testing, fill in the test information. Apple's test information page says: "In the Beta App Description text field, enter a description of your beta version. This field is required." And: "In the Feedback Email field, enter the email address where testers can contact you through the TestFlight app." Apple's TestFlight page adds: "your beta app description and beta app review information are required in order to share your beta with external testers."
Step 6: Create an external group and submit for TestFlight App Review
Apple's rule: "To create an external group for external testing, you must first create an internal group for internal testing." Create the external group, add the build, and it goes to review: "When you add the first build of your app to a group, the build gets sent to App Review to make sure it follows the App Review Guidelines." After that, "Subsequent builds may not require a full review."
Step 7: Invite testers by email or public link
Add testers by email, from your existing list, or by importing a CSV file. Or turn on a public link. Apple suggests including a public link in your marketing communications, such as email and social media, "to invite people to test your beta build." You can cap the number of testers ("Enter a number between 1 and 10,000") and filter who can join: "Filter who can join by device or platform."
Step 8: Read feedback and crash reports
Apple says: "Testers can take a screenshot from your app or game and easily share feedback," and "If they experience a crash, you'll receive a crash report and testers have the option of sharing additional context." You see this in the TestFlight Feedback section of App Store Connect, along with metrics that "include the number of sessions and crashes."
Step 9: Upload new builds and repeat
Each new build needs a higher build number. Add it to your groups, and if "Automatically notify testers" is on, testers are told about the update.
Step 10: Submit the tested build to the App Store
When you are happy, Apple says to "just submit the last build that appears in App Store Connect to App Review." Then expire old beta builds if you no longer want testers using them.
| Step | Where | Time |
|---|---|---|
| Superapp users: build the app | Superapp | Minutes to hours |
| Upload a build | Xcode, Xcode Cloud or your builder | Minutes, then processing |
| Internal testing | App Store Connect, internal group | Immediate |
| Test information | App Store Connect, TestFlight tab | 10 minutes |
| TestFlight App Review | Apple | Apple publishes no TestFlight-specific time |
| External invites | Email or public link | Immediate after approval |
| Feedback loop | TestFlight Feedback in App Store Connect | Ongoing, up to 90 days per build |
How Long Does TestFlight Review Take?
Superapp's honest answer: Apple does not publish a separate time for TestFlight review. For App Review in general, Apple says it is "typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours." Plan for up to two days for your first external build, and remember that only the first build needs review: "A review is required only for the first build."
One limit applies: "You can only have one build of each version in review at a time," and you can submit "up to six builds for TestFlight App Review within a 24-hour period."
What TestFlight review checks
TestFlight builds follow the same App Review Guidelines as store builds. Guideline 2.2 says: "Any app submitted for beta distribution via TestFlight should be intended for public distribution and should comply with the App Review Guidelines. Note, however, that apps using TestFlight cannot be distributed to testers in exchange for compensation of any kind, including as a reward for crowd-sourced funding. Significant updates to your beta build should be submitted to TestFlight App Review before being distributed to your testers."
Apple takes this seriously. Its May 2026 fraud report says: "In 2025 alone, Apple blocked more than 2.5 million submissions from distribution on TestFlight due to fraud or security concerns."
How Do Testers Install a TestFlight App?
Superapp's tester instructions, ready to copy into your invitation message, follow Apple's tester page:
- Install TestFlight from the App Store on the device you will test with.
- Open the email invitation and tap "View in TestFlight," or tap the public link on your device.
- Tap Accept, then tap Install.
- Turn on automatic updates when prompted, so you always have the latest build.
- To send feedback, take a screenshot in the app, tap Share Beta Feedback, add a comment and send.
| Tester device | Minimum version | How to join |
|---|---|---|
| Superapp-built iPhone app on iPhone | iOS 16 or later | Email invite or public link |
| iPad | iPadOS 16 or later | Email invite or public link |
| Mac | macOS 13 or later | Email invite or public link |
| Apple TV | tvOS 18 or later | Redemption code shown on a web page |
| Apple Vision Pro | visionOS 1 or later | Email invite or public link |
| Apple Watch | watchOS 9 or later | TestFlight on Apple Watch |
Two privacy points testers often ask about. Apple says: "When you accept a TestFlight invitation through a public link, your name and email address aren't visible to the developer," and "Information that is emailed to the developer directly is not shared with Apple."
How Do You Get Useful Feedback From TestFlight?
Superapp's experience is that testers rarely give feedback unless you ask for something specific. Use the "What to Test" notes for each build, and keep the ask small.
| Build stage | What to ask testers | Example "What to Test" note |
|---|---|---|
| Superapp-built first version | Can they finish the main task? | "Create your first plan and tell us where you got stuck." |
| First external build | First impressions in five minutes | "Open the app, try the first screen, send one screenshot of anything confusing." |
| Onboarding change | Do they reach the core feature? | "Sign up and tell us how many taps it took to reach your first result." |
| Paywall test | Do they understand the offer? | "Look at the subscription screen. What do you think you get?" |
| Pre-launch build | Crashes and blockers only | "Use the app normally for two days. Report anything that breaks." |
What works in practice:
- One question per build, written in plain words.
- A feedback email you actually read, because it is also the reply-to address on invitations.
- A short thank-you message to every tester who sends feedback.
- Watching sessions and crash numbers in App Store Connect, not only written feedback.
How Do You Use TestFlight to Find Your First Users?
Superapp sees TestFlight as one of the best free channels for first users, because a public link needs no contact details. Apple notes that public links "can be a great way to establish a group of testers since you don't need to have anyone's contact information to invite them."
| Where to post your public link | Why it works | Watch out for |
|---|---|---|
| Superapp's suggestion: one niche community where your users gather | People with the problem try it and tell you why | Read the community's rules on self-promotion |
| Your waiting list or newsletter | Already interested people | Send one clear ask with the link |
| Social posts showing the app | Reach beyond people you know | Do not promise rewards; Guideline 2.2 forbids compensation |
| Direct messages to target users | Highest-quality feedback | Keep it personal, not a broadcast |
| Product Hunt or maker communities | Early adopters | Feedback skews to other makers |
For the full first-users plan, see our guide on how to get your first users for an app.
What Happens When a TestFlight Build Expires?
Superapp's reminder: the 90-day clock starts at upload, not when testers install. Apple says each build is available "for up to 90 days, starting from the day the developer uploads their build," and "Your build becomes unavailable for testers after 90 days." To keep testing, upload a new build before the old one expires.
You can also expire a build early: "Click Expire Build," after which "The build no longer allows internal and external testers to install it." If you remove a build from a group, "testers currently using the build will continue to have access until they switch builds or choose to stop testing your app."
One detail after launch: "If you don't expire your build and submit it to the App Store, testers who received an invitation to test will still be able to test your build even after it goes live on the App Store."
TestFlight vs Ad Hoc vs Google Play Testing
Superapp users who need to test outside TestFlight, or on Android, have other options.
| Option | Max testers | Review needed | Best for |
|---|---|---|---|
| Superapp's default for iPhone betas: TestFlight | 100 internal, 10,000 external | First external build | Almost every iPhone beta |
| Ad Hoc distribution | 100 registered devices per product family per membership year | No | A few known devices, no TestFlight app |
| Release Testing (Xcode) | Devices registered with App Store Connect | No | Testing a release build on team devices |
| Google Play internal testing | Up to 100 testers per app | "might not be subject to standard Play policy or security reviews" | Fast Android team checks |
| Google Play closed testing | Lists of up to 2,000 users, up to 200 lists | Yes | Android betas; required for new personal accounts |
| Google Play open testing | Limit must be at least 1,000 | Yes | Large public Android betas |
For Ad Hoc, Apple says developers "can register up to 100 of the following devices, per product family, per membership year," and each device's identifier must be registered. That is why TestFlight is easier for anyone outside your team. On Android, Google requires new personal developer accounts created after November 13, 2023 to run a closed test "with a minimum of 12 testers who have been opted in continuously for at least 14 days" before publishing.
What Changed in TestFlight in 2025 and 2026?
Superapp tracks Apple's release notes so this list stays current.
| Date | Change | Source |
|---|---|---|
| Superapp's note: check Apple's release notes before relying on a feature | TestFlight updates ship several times a year | Apple TestFlight release notes |
| June 2025 (WWDC25) | TestFlight feedback and notifications in the App Store Connect app; webhooks and feedback APIs for screenshot and crash feedback; a new Build Uploads section | Apple, What's new in App Store Connect |
| June 10, 2025 | TestFlight 3.9: testing for Managed Background Assets and Apple-Hosted Background Assets | Apple release notes |
| October 6, 2025 | TestFlight 4.0: "A refreshed look, featuring the Liquid Glass design" and accessibility improvements | Apple release notes |
| April 30, 2026 | TestFlight 4.2: 11 new languages | Apple release notes |
| September 24, 2026 | TestFlight 4.4.0: "Landscape orientation on iPhone" and resizing with iPhone Mirroring on Mac | Apple release notes |
| October 22, 2026 | TestFlight 4.4.1: "Support for iPhone Duo" | Apple release notes |
Common TestFlight Mistakes
Superapp sees these mistakes again and again:
- Trying to create an external group before an internal one. Apple requires the internal group first.
- Uploading a "TestFlight Internal Only" build and wondering why it cannot go to external testers.
- Forgetting the beta app description, which blocks external testing.
- Reusing a build number. Every upload needs a higher one.
- Offering testers rewards or payment. Guideline 2.2 forbids "compensation of any kind."
- Letting builds expire before launch, so testers suddenly cannot open the app.
- Sending testers a link with no instructions, so nobody knows what to test.
- Expecting feedback from tvOS testers in TestFlight. Apple says they send feedback to the email address you set.
How Superapp Fits
Superapp builds native iPhone, iPad, Watch and Mac apps from a description and, once you connect your Apple Developer account, "prepares the build, metadata, screenshots, privacy declarations, ASO optimization, and submission flow for you." Superapp's site does not describe a TestFlight workflow, so plan to manage beta testers yourself in App Store Connect, exactly as described above. The TestFlight steps are the same whether your build came from Superapp, Xcode, Xcode Cloud, Expo EAS, fastlane or FlutterFlow, because TestFlight is part of your Apple Developer account, not the tool that built the app.
What no tool can do for you: recruit testers, read their feedback, or decide what to fix. Those are where a beta earns its value.
Frequently Asked Questions
What is TestFlight?
TestFlight is Apple's free beta testing service. Developers upload builds to App Store Connect and invite testers, who install the app through the TestFlight app and send feedback.
Is TestFlight free?
Yes for testers. Developers need an Apple Developer Program membership, 99 USD a year, and TestFlight is included.
How many testers can I have on TestFlight?
Up to 100 internal testers from your App Store Connect team and up to 10,000 external testers per app.
How long do TestFlight builds last?
90 days from the day you upload the build. After that, testers cannot install it.
Does TestFlight need App Review?
Only for external testing. The first build you add to an external group goes to TestFlight App Review. Internal testing does not need review, and later builds may not need a full review.
How long does TestFlight review take?
Apple does not publish a TestFlight-specific time. For App Review in general, Apple says at least 50% of submissions are reviewed in under 24 hours and 90% in under 48 hours.
How do I invite testers to TestFlight?
Create a group in your app's TestFlight tab, add a build, then add testers by email, import a CSV file, or turn on a public link.
What is a TestFlight public link?
A link anyone can open to join your beta, without you needing their email. You can cap the number of testers between 1 and 10,000 and filter by device or platform.
Why can't I create an external TestFlight group?
Apple requires an internal group first. Also check that the build was not uploaded as TestFlight Internal Only.
How do testers give feedback in TestFlight?
They take a screenshot in the beta app, tap Share Beta Feedback and add a comment, or send feedback from the TestFlight app. Crash reports are sent if they agree.
Can I see who joined through a public link?
No. Apple shows public link testers as anonymous in App Store Connect.
Can I pay testers or give rewards for joining my TestFlight beta?
No. Guideline 2.2 says apps using TestFlight cannot be distributed to testers in exchange for compensation of any kind.
How many devices can a tester use?
Up to 30 devices per tester.
What iOS version do testers need?
iOS 16 or iPadOS 16 or later. Mac testers need macOS 13 or later.
Do I need a Mac to use TestFlight?
Not as a tester. As a developer, you need a way to build and upload the app, such as Xcode on a Mac, Xcode Cloud, or a builder that compiles in the cloud.
What is the difference between TestFlight and Ad Hoc?
TestFlight distributes through Apple's tester app to up to 10,000 people without registering devices. Ad Hoc installs on up to 100 registered devices per product family per membership year.
Can testers keep using the beta after my app launches?
Yes, until the build expires, unless you expire it yourself.
Can I use TestFlight for a Mac or Apple TV app?
Yes. Apple supports TestFlight for Mac (built with Xcode 13 or later), Apple TV, Apple Vision Pro and Apple Watch apps. Apple TV testers join with a redemption code.
Does TestFlight work for Android?
No. Android apps use Google Play's internal, closed and open testing tracks.
Can a Superapp-built app be tested on TestFlight?
Yes, because TestFlight works with any build uploaded to your App Store Connect account. You manage testers in App Store Connect yourself.
References
- Apple, TestFlight
- Apple, TestFlight overview
- Apple, Add internal testers
- Apple, Invite external testers
- Apple, Provide test information
- Apple, Stop testing a build
- Apple, Testing apps with TestFlight (testers)
- Apple, Distributing your app for beta testing and releases
- Apple, Xcode Cloud
- Apple, Complying with encryption export regulations
- Apple, Devices overview (Ad Hoc limits)
- Apple, App Review Guidelines
- Apple, App Review
- Apple, TestFlight release notes
- Apple, What's new in App Store Connect (WWDC25)
- Apple Newsroom, App Store fraud prevention in 2025 (May 2026)
- Google Play Console Help, Testing tracks
- Google Play Console Help, Testing requirements for new personal accounts
- Superapp
- How to get your first users for an app
- App Store review process 2026