TestFlight vs Ad Hoc Distribution: Which Should You Use in 2026?

Use TestFlight for larger or public iOS betas where you invite testers by email or link; use ad hoc for fast installs on a handful of known devices without waiting on review. The core trade-off: TestFlight needs no UDIDs but reviews external builds and expires them after 90 days, while ad hoc skips review but caps you at 100 devices per product type per year and makes you collect UDIDs up front.

Both are legitimate iOS testing routes on the standard $99/year Apple Developer membership. The right one depends on how many testers you have, whether you know their devices, and how much review latency you can tolerate.

How each works

• TestFlight — upload to App Store Connect, invite testers. Internal testers (≤100 App Store Connect users) install instantly; external testers (≤10,000) join by link but the first build of each version passes Beta App Review first.
• Ad hoc — register each device's UDID in the Apple Developer portal, bake them into the provisioning profile, build, and distribute the signed .ipa (usually over the air). Only listed devices can install.

TestFlight vs ad hoc: the comparison

	TestFlight	Ad hoc
Review	External testers only	None
Tester / device limit	100 internal / 10,000 external	100 devices per product type / year
Expiry	90 days per build	Certificate lifetime (up to a year)
UDID needed?	No	Yes, before the build
App Store Connect needed?	Yes	For device/profile management
Setup speed	Fast for many testers	Instant for known devices

When to use which

• Large or public beta: TestFlight — you don't want to collect hundreds of UDIDs.
• A few known devices, need it now: ad hoc — no review, instant install.
• Recurring internal/QA builds where you control the devices: ad hoc, or an OTA tool to automate it.

A third way: OTA tools

You don't have to choose between ad hoc's instant, review-free installs and TestFlight's easy onboarding. Appisto combines both: OTA installs with no review and no 90-day expiry, plus automatic UDID collection so ad hoc stops being manual, and persistent tester groups so a device is added once, not per build. It also covers Android, which neither TestFlight nor ad hoc can. If you keep hitting the 100-device limit or the 90-day clock, that's the signal to move up.

Frequently asked questions

Is ad hoc faster than TestFlight? For the first external build of a version, yes — no review. But ad hoc needs each UDID registered first, so TestFlight can win when onboarding many testers.

Does ad hoc distribution expire? It lasts until the certificate or profile expires (up to a year), not on TestFlight's 90-day clock.

Can I use TestFlight without App Store review? Internal testers (≤100 App Store Connect users) skip review; only external testers need Beta App Review for the first build of each version.

Key takeaways

• TestFlight: no UDIDs, but external review and 90-day expiry.
• Ad hoc: no review, but 100 devices per type per year and manual UDID collection.
• Pick TestFlight for scale, ad hoc for speed on known devices.
• An OTA tool like Appisto gives you ad hoc's immediacy with automated UDIDs, no expiry, and Android too — see the iOS distribution matrix and TestFlight alternatives.