This is the mirror image of a rule that trips people up elsewhere. On the public App Store, words like "Beta" get your listing rejected, because the store is for finished products. In TestFlight, the opposite is true: TestFlight is the beta channel, so calling your build a beta in the test information is normal and expected. The one place to be careful is the app name itself, which comes from your App Store Connect record and is shared with the store. Here is where "Beta" is fine in TestFlight and where it is not.
Short answer
Yes, you can use "Beta" in your TestFlight test information, like the beta app description and the "What to Test" notes, because TestFlight is Apple's beta-testing channel and those fields are shown only to your testers, not on the public App Store. Per Apple's TestFlight overview, the restriction on beta wording applies to the public App Store listing, not to TestFlight's tester-facing fields. The one caveat is the app name itself, which comes from your App Store Connect app record and is the same name used on the store, so keep "Beta" out of the name even though the TestFlight description can use it freely.
What you should know
- TestFlight is the beta channel: beta wording there is expected.
- Test information can say "Beta": the description and What to Test are tester-facing.
- The public listing cannot: the App Store restriction is on the store listing.
- The app name is shared: it comes from your App Store Connect record.
- Keep the name clean: avoid "Beta" in the name even for TestFlight.
Is "Beta" allowed in TestFlight?
Yes, in the tester-facing fields. TestFlight exists specifically to distribute pre-release builds to testers, so describing a build as a beta there is entirely appropriate, and Apple expects it. The beta app description and the "What to Test" notes are seen only by your testers inside the TestFlight app, not by the public, so wording like "this is a beta, expect rough edges" is fine and even helpful. This is the opposite of the public App Store, where calling your listing a beta gets it rejected because the store is meant for finished products. The difference comes down to audience: TestFlight is for testers and pre-release software, so beta language fits the channel.
TestFlight fields versus the App Store listing
The line is between tester-facing TestFlight fields and the public listing. The table maps it.
| Field | "Beta" wording allowed? |
|---|---|
| TestFlight beta app description | Yes, shown to testers |
| TestFlight "What to Test" notes | Yes, shown to testers |
| App name (from App Store Connect) | No, it is the public store name |
| Public App Store description and screenshots | No, restricted on the listing |
So everything that is purely TestFlight tester information can use beta language, while anything that is the public App Store listing, or the app name that feeds it, should not. The mental model is to ask who sees the field: testers in TestFlight, or shoppers on the App Store.
What about the app name itself?
That is the one to keep clean. Your app's name is set in your App Store Connect app record, and it is the same name that appears on the public App Store, so even though you are only testing in TestFlight right now, putting "Beta" in the name carries over to the store listing later and is the kind of wording Apple rejects there. TestFlight does not give you a separate beta-only name; it shows the app's real name alongside the tester-facing description you write. So describe the build as a beta in the description and the What to Test notes, but leave the name as the clean, final product name you intend to ship. That way nothing has to change when you move from TestFlight to the App Store.
What to watch out for
The first trap is over-correcting from the App Store rule and scrubbing "beta" out of your TestFlight test information, where it actually belongs and helps testers. The second is the reverse, putting "Beta" in the app name because you are in TestFlight, which then follows the name to the public listing. The third is treating the TestFlight description as public; it is tester-facing, so write it for testers. Naming and metadata are separate from your app's security, so they sit apart from a pre-submission scan such as PTKD.com (https://ptkd.com), which reads the binary against OWASP MASVS; the beta-wording decision is purely about which field you are editing and who sees it.
What to take away
- Yes, you can use "Beta" in your TestFlight test information, since the beta app description and What to Test notes are tester-facing and TestFlight is the beta channel.
- The restriction on beta wording applies to the public App Store listing, not to TestFlight's tester fields.
- Keep "Beta" out of the app name, which comes from your App Store Connect record and is the same name used on the store.
- Describe the build as a beta for testers, but leave the name as the final product name so nothing changes when you ship.
