The Apple Developer 100-Device Limit: How It Works and How to Stop Hitting It

Apple's 100-device limit is one of the most misunderstood constraints in iOS development. It's 100 devices per product type per membership year — 100 iPhones, 100 iPads, 100 Apple Watches, each counted separately. Disabling a device does not free a slot, and the count only resets once a year at renewal. Here's exactly how it works and how to stop hitting it.

The confusion costs teams real time: people disable old devices expecting a free slot, and it never comes.

How the limit actually works

• Per product type. iPhone, iPad, iPod touch, Apple Watch, Apple TV and Mac each have their own 100-device pool. 100 iPhones + 100 iPads = 200 registrations, and that's fine.
• Per membership year. The pool is tied to your Apple Developer membership year.
• Registration counts, not installs. A device counts the moment it's registered, whether or not an app is currently installed on it.

What counts against the limit

Any device you add under Certificates, Identifiers & Profiles → Devices counts — for both development and ad hoc distribution. Registering a tester's iPhone to send them an ad hoc build consumes one of your 100 iPhone slots. (See finding and registering a UDID.)

The annual reset — and the disabling trap

The single most common mistake: disabling a device does not return its slot. Disabling only stops it receiving new builds. The list resets once a year, at renewal, when Apple shows a one-time prompt to remove devices and start fresh.

Practical hygiene:

• Don't register throwaway devices you'll only use once.
• Keep a note of which registrations are stale, ready for the renewal prompt.
• Treat the annual reset as your only real cleanup window — plan for it.

Ways to stop hitting it

• TestFlight — external testers don't count against the ad hoc device limit; up to 10,000 of them. The trade-off is Beta App Review and a 90-day build expiry. See TestFlight vs ad hoc.
• OTA / managed tools — a distribution tool that manages devices for you keeps the pool tidy and automates registration, so you're not burning slots by hand.
• Device hygiene — only register what you need, and clean up at renewal.

Where a tool helps: Appisto collects UDIDs automatically and manages your tester devices in one place, so you register deliberately rather than accidentally — and because it also handles Android and OTA installs, you lean on the raw ad hoc pool less. For larger external groups, pair it with TestFlight. See how to distribute an iOS app without the App Store.

Frequently asked questions

Can I add more than 100 devices? Not within one product type per year — it's 100 iPhones, 100 iPads, etc., counted separately. Use TestFlight (up to 10,000 external testers) or an OTA tool for larger reach.

Does disabling a device free up a slot? No — disabling stops new builds but doesn't return the slot. The count resets only at annual renewal.

When does the Apple device limit reset? Once per membership year, at renewal, via a one-time prompt to remove devices. Skip it and registrations carry over.

Key takeaways

• The limit is 100 devices per product type per membership year, counted at registration.
• Disabling a device does not free a slot; the list only resets at renewal.
• Escape it with TestFlight (external testers don't count) or managed OTA tools, plus device hygiene.
• Appisto automates UDID collection and device management so you stop burning slots — see the iOS distribution matrix and Developer vs Enterprise Program.