Apple Intelligence has daily limits, and Apple has published almost none of the numbersApple Intelligence has daily limits, and Apple has published almost none of the numbers

Some Apple Intelligence features in iOS 27 stop working for a period once a daily limit is reached, according to a support document Apple published on 9 September.

Apple says the affected features are the ones that rely on server-side models rather than running on the device, and gives image generation as an example. The document says a feature that hits its limit becomes available again after a time out, that limits may vary by feature, request complexity, system demand and other factors, and that increased access will be available for a fee. It does not say how large any limit is, how long a time out lasts, or what the fee will be.

One set of numbers is published. For Apple Intelligence video summaries of HomeKit Secure Video cameras, Apple lists up to one camera on the 2TB iCloud+ plan, two on 6TB and five on 12TB. 9to5Mac reported on 17 September that iCloud+ subscribers also get higher daily limits for other server-backed features, quoting Apple's line that increased access comes with most iCloud+ plans, and noted that Apple has not said which plans the word most excludes. MacRumors reported the Home camera tiers in August, before Apple's page appeared.

What Apple has published, and what it has not

Our take

Metering server-side AI is reasonable. These features run in data centres, they cost real money per request, and a cap is a more honest response to that than quietly making the model worse at busy times. Apple saying out loud that heavier use will eventually cost money is better than the alternative of discovering it later.

Publishing no numbers is the problem. A limit a user cannot see is indistinguishable, from the inside, from the feature being broken. Someone editing photos who suddenly cannot generate another image has no way to tell whether they have hit a cap, whether the servers are busy, or whether something has gone wrong, and Apple's own wording, that limits vary by system demand, means the honest answer may be that today's limit is not the same as yesterday's.

It also makes the iCloud+ upsell hard to evaluate. The Home camera tiers are a specification: one, two or five cameras, for a plan you can price. The rest is an unspecified quantity of something. We would not advise anyone to move from 2TB to 6TB for AI headroom that has never been quantified, and we would expect Apple to publish figures before it starts charging a separate fee, if only because a fee for an undefined allowance is the kind of thing consumer regulators read carefully.

There is a smaller discrepancy worth noting for anyone who read the earlier coverage. In August, MacRumors relayed a developer's observation from the iOS 27 beta of eligibility for as many as fifteen cameras on a large combined plan. Apple's published table tops out at five on the 12TB plan. Beta behaviour is not a promise, and the support document is the one to trust.

For anyone building on these APIs, the design lesson is the one that always applies to metered capacity. Treat a limit as a normal state rather than an error: say which feature is unavailable, say it will return, and keep a path that works without it. An app that presents a cap as a failure teaches people the feature is unreliable, and they stop trying it long before the time out expires.

• Server-backed features can fail on a perfectly healthy device, so never put one on the critical path of a task.
• A shared household plan means one person's use can affect what another has left, and nothing in the interface shows that.
• The limits are Apple's to change at any time, and the support document says as much in its list of factors.