How to find iOS beta testers for your TestFlight beta

TestFlight makes distributing an iOS beta easy; finding people who install it and keep reporting is the hard part. This guide covers how TestFlight public links and limits work, where to recruit iPhone testers, what to offer them, how to keep them engaged across 90-day build cycles, and how an AI beta tester fits in before the first invite goes out.

Who it’s for

  • iOS developers preparing their first external TestFlight beta
  • Indie teams who need iPhone testers on different models and iOS versions
  • Founders moving a web product to iOS and recruiting from their user base
  • Teams running a long beta that spans several builds

Updated 2026-10-25.

How TestFlight testers work

Apple's TestFlight is the only official way to distribute an iOS beta to people outside your team. Testers install the free TestFlight app, accept an invite, and install your build like any other app. A few facts shape how you recruit:

  • Internal testers are members of your App Store Connect team, up to 100. They get builds as soon as processing finishes, with no review.
  • External testers are anyone you invite by email or through a public link, up to 10,000 per app. The first build for external testers goes through Beta App Review; later builds of the same version usually clear faster.
  • Public links can be shared anywhere and you can cap how many people join. This is the main recruitment tool: no collecting email addresses, no manual invites.
  • Builds expire after 90 days. Testers see the app go dark if you stop shipping, so a long beta needs regular builds.
  • Testers can send feedback with screenshots straight from the TestFlight app, and crash reports land in App Store Connect.

Check Apple's current TestFlight documentation for limits; they have changed over the years.

Where to find iOS beta testers

  1. Your existing audience. Waitlist, newsletter, web app users, social followers. These people already want the app and will keep TestFlight installed. A public link in a single email usually fills a first group.
  2. Friends, family and colleagues. Fast and loyal, but polite. Good for install coverage on different iPhone models, weak for honest usability feedback.
  3. Communities around your app's topic. Subreddits, Discord servers, Slack groups, forums and Facebook groups for the problem you solve. Read the rules, ask moderators, and lead with what the app does for members rather than "please test my app".
  4. iOS and indie developer communities. Developer forums and Discords often have a channel for TestFlight links. Fellow developers find different bugs than end users and are good at describing them. They may not represent your real audience.
  5. Public beta directories. Several websites and newsletters list open TestFlight betas. Quality varies; expect curious installers rather than committed testers.
  6. Your other platforms. If you have an Android app, a website or an extension, a banner for iPhone users converts better than any forum post.
  7. Paid panels and freelance testers. When you need specific devices, regions or accessibility expertise, pay for it. They show up and follow instructions.

Incentives that keep iPhone testers active

  • Free or discounted access to the paid tier after launch, ideally for life for the founding group.
  • Credits in the app's About screen or on the website.
  • Early access to new features as long as they stay in the beta.
  • Small gift cards for completing a task list plus a feedback form, not for installing.

TestFlight testers who stop opening the app are invisible until you notice feedback has dried up. Tie rewards to the tasks you want done.

What to ask iOS testers to do

  • Give three to five concrete tasks that cover your core flows, and say which iPhone features they should try (notifications, Sign in with Apple, widgets, Share sheet).
  • Ask them to use TestFlight's built-in feedback for bugs so screenshots and device details arrive together, or give one form if you need structured answers.
  • Request iPhone model, iOS version and build number with each report. TestFlight includes most of this automatically when they report from the app.
  • State the beta end date and what happens to their account and data at launch.

Keeping testers through 90-day cycles

  • Ship a new build at least monthly so nothing expires mid-beta, and use the "What to Test" notes to point testers at what changed.
  • Start with a small external group of trusted testers, then open a public link once the first wave of bugs is fixed. Groups in App Store Connect let you stage this.
  • Send a short update after each build: what was fixed, what to try next. Silent builds get ignored.
  • Remove testers who never installed, so your group counts reflect real coverage.

Example recruitment message

Subject: Be one of the first to try [App] on iPhone

[App] is a [one sentence]. It's in beta on TestFlight and I'd love your help
before the App Store launch.

Join here: [public TestFlight link]. Install the TestFlight app if you don't
have it, then install [App]. The build works on iOS [minimum version] and up.

Please try these three things in the first week:
- Create an account (Sign in with Apple works) and finish onboarding
- [core task]
- [second core task]

Report anything strange from inside TestFlight (shake or screenshot, then
"Send Beta Feedback"). Testers who send feedback get [App] Pro free for a
year at launch. The beta runs until [date].

Common mistakes

  • Sharing the public link before internal testing catches launch crashes. First impressions decide whether testers come back.
  • Letting the only build expire, so testers open the app to an expiry message and leave for good.
  • Recruiting hundreds of installers with no tasks or feedback channel, then wondering why nothing comes in.
  • Testing only on the newest iPhone. Ask for coverage on a small phone and an older iOS version explicitly.
  • Forgetting a demo account for testers (and later for App Review) when sign-up requires a real phone number or invite code.

Where an AI beta tester fits

An AI beta tester like betatest.ing takes the systematic pass that your human testers will not do: install the build on a real iPhone or iOS simulator, go through every screen and flow, deny permissions, check the notch and home indicator areas, swipe back everywhere, background and resume, and file bug reports with steps to reproduce, severity, annotated screenshots and screen recordings. Export the same build as an ad-hoc or development .ipa and upload it; it cannot install from TestFlight itself.

Run it before the first external invite and on every new build after that. Your human testers then spend their attention on what only they can judge: whether the app is useful, how it feels in daily use, and what happens on their network, camera and notifications. The AI tester does not count as a TestFlight tester and does not replace Beta App Review.

A simple recruiting plan

  1. Internal testers plus the AI pass on the first stable build; fix crashes and blockers.
  2. Invite 10 to 20 trusted external testers by email with a task list; submit the build for Beta App Review.
  3. After one fixed build, open a public link in your newsletter and one or two communities, capped at a number you can support.
  4. Ship monthly builds with "What to Test" notes and a short update message.
  5. Close the beta with a survey, remove inactive testers, and keep the engaged group for the next version.

The test task

What you send your AI beta tester. It works out the steps and tests like a real user.

Beta test my iOS app (the uploaded .ipa, exported for ad-hoc or development distribution) before I invite external TestFlight testers. It is [WHAT THE APP DOES AND WHO IT IS FOR]. Install it on an iPhone, go through first launch, onboarding and every permission prompt (deny one and check the app explains what to do), sign in with the saved test login, then use each main screen and flow, especially [THE CORE TASKS TESTERS WILL BE ASKED TO DO]. Check that nothing sits under the notch, Dynamic Island or home indicator, that swipe back works on every pushed screen, that sheets dismiss, that the keyboard never covers the active field, and that dark mode and large text look right. Do not make any purchases. Log each bug with steps to reproduce and an annotated screenshot, record any flow that breaks, and finish with a report that scores first-run experience, stability, navigation and layout, with the fixes to ship before testers get the build.

Fill in your details

Here, or later in the chat with your tester.

  • [WHAT THE APP DOES AND WHO IT IS FOR] One sentence about the app and its users
  • [THE CORE TASKS TESTERS WILL BE ASKED TO DO] The same three to five tasks from your tester brief

What the AI beta tester checks

  • Install of the .ipa and a clean first launch
  • Onboarding and sign-in with the test login
  • Permission prompts, including deny
  • The core tasks from your tester brief
  • Safe areas: notch, Dynamic Island, home indicator
  • Swipe back, sheet dismissal and keyboard overlap
  • Dark mode and large Dynamic Type sizes
  • Backgrounding and resuming

What you get

  • Bug reports with steps to reproduce, severity and annotated screenshots
  • Screen recordings of flows that crash or break
  • A scored report on first-run experience, stability, navigation and layout
  • The fixes to ship before the first external TestFlight invite

How to run it with betatest.ing

  1. Add your app as a project in betatest.ing and upload an .ipa exported for ad-hoc or development distribution.
  2. Add a test login if the app needs an account.
  3. Send the task; the tester installs the build on a real iPhone and files findings.
  4. Fix blockers, upload the next build and re-run before sharing the TestFlight public link.

Tips

  • Start with a small trusted external group, then open a public link once the first fixes ship.
  • Ship a new build at least every month so nothing expires mid-beta.
  • Ask testers to report from inside TestFlight so device details come with the screenshot.
  • Ask explicitly for coverage on a small iPhone and an older iOS version.
  • Give every tester the same demo account you will later give App Review.

Find iOS beta testers: FAQ

How many TestFlight testers can I have?

Up to 100 internal testers from your App Store Connect team and up to 10,000 external testers per app. Check Apple's current TestFlight documentation, since limits have changed before.

How do TestFlight public links work?

You create a public link for an external group in App Store Connect and share it anywhere. Anyone with the TestFlight app can join until the cap you set is reached. The build must have passed Beta App Review first.

Do I need Beta App Review to invite external testers?

Yes, the first build for external testing goes through Beta App Review. Internal testers do not need it. Later builds of the same version usually clear faster, but plan a few days for the first one.

Why did my testers' app stop opening?

TestFlight builds expire 90 days after upload. If you did not ship a newer build, testers see an expiry message. Keep a monthly build cadence during long betas.

Where can I find iOS beta testers for free?

Your own waitlist and users, friends and colleagues, communities around your app's topic, indie iOS developer forums and Discords, and public beta directories. Your existing audience usually gives the best testers.

Can an AI beta tester join my TestFlight beta?

No, it cannot install from TestFlight. Upload the same build exported as an ad-hoc or development .ipa to betatest.ing and it tests it on a real iPhone, filing bugs with screenshots and recordings. Keep TestFlight for your human testers.

How do I keep iOS beta testers engaged?

Give them specific tasks, use the What to Test notes on each build, send a short update after every release, tie rewards to completing tasks, and never let the only build expire.

Should I give testers a demo account?

Yes, if sign-up needs an invite code, phone verification or paid access. The same demo account will be needed for App Review, so set it up once with realistic data.

Related beta testing guides

  • TestFlight beta testing — TestFlight is Apple's beta distribution service and the standard way to get iOS, iPadOS, macOS, watchOS, tvOS and visionOS builds to testers before the App Store. This guide walks through internal and external testers, groups and public links, Beta App Review, build expiry, how feedback and crash reports arrive, and how to pair TestFlight with an AI beta tester so your human testers meet a stable build.
  • iOS app beta testing — TestFlight is how almost every iOS app gets into beta testers' hands before the App Store. This guide explains how TestFlight testing works, what to check on iPhone that differs from Android, and how to run an AI beta test on a real iPhone from an uploaded .ipa build.
  • How to find beta testers — Finding beta testers is less about reaching many people and more about reaching the right few who will actually use the product and report back. Here are the places that work, how to invite people, and how to keep them engaged.
  • How many beta testers — There is no single right number of beta testers. The right size depends on what the beta test must answer, how many different kinds of users and devices you have, and how much feedback your team can actually process.
  • Mobile app pre-launch checklist — Launching a mobile app means passing two store reviews, surviving real devices and keeping users on day one. This checklist walks through everything to verify before you submit, from builds and beta testers to store policies, in-app purchases, crashes and the listing itself, with links to detailed guides for each step and a full pre-launch task your AI beta tester can run.
  • Free tool: Beta testing checklist generator — An interactive checklist for websites, SaaS, mobile apps, stores and extensions. Progress saved, Markdown export.

More in guides