The first 48 hours are always the worst
The moment a major update finishes, several heavy jobs start at once: Spotlight rebuilds its index of everything on the device, Photos re-runs face and scene analysis across your entire library, and iCloud reconciles what changed. On a large photo library that work can run for a day or more, and it is CPU-bound the whole time.
During that period a warm phone is normal, not a fault. Keeping the device on power and on Wi-Fi with the screen off actually speeds it up, because iOS schedules more of that work aggressively when it is charging and idle.
How to tell normal from broken
Normal beta heat tapers. If day three is cooler than day one and day four is cooler again, the system is finishing its work and you should leave it alone. Persistent heat that has not improved after four or five days is a different signal — usually a single app or system process stuck in a loop.
Settings → Battery, switched to the last 10 days and sorted by activity, will identify it. A single app holding a large share of background activity while you were not using it is the thing to remove or force-quit.
Things that make it worse
Restoring a large backup immediately after installing a beta doubles the work: the device is indexing new content while still reindexing the old. Where possible, let the beta settle first and restore afterwards.
Charging while running the device hard compounds heat from both sources. If the phone is uncomfortably warm, take it off the charger and put it down rather than continuing to use it — iOS will throttle performance and dim the display to protect the battery, and fighting that only extends the period.
When heat is a real warning
A phone too hot to hold comfortably, a temperature warning screen, or a device that shuts down on its own is past the point of normal beta behaviour. So is heat that appears immediately on wake, before you have done anything.
At that stage stop using the beta. Turn off Beta Updates and, if the finished release is not close, restore to the previous version from the archived backup you made — our downgrade guide covers the sequence. Sustained heat is the one beta symptom that can genuinely age the battery.
Reporting it is worth the five minutes
Thermal bugs are among the hardest for Apple to reproduce internally, because they depend on a specific combination of apps, data and usage. A Feedback Assistant report from an affected device is disproportionately valuable, and it is the mechanism by which these get fixed before the public release.
Include a sysdiagnose captured while the device is hot — the Feedback Assistant app prompts for it — and note which app the Battery screen implicates. Our bug reporting guide covers what makes a report actionable.
Frequently Asked Questions
Is it normal for an iPhone to get hot after installing a beta?
Yes, for the first two to three days. Spotlight indexing and Photos analysis run continuously after a major update, and both are CPU-intensive.
How long should beta overheating last?
It should taper noticeably by day three and be gone by day four or five. Heat that has not improved after that points to a specific app or process rather than to normal indexing.
Can a beta damage my iPhone's battery?
Sustained high temperatures accelerate battery ageing, which is why persistent overheating is worth acting on rather than waiting out. Normal first-week warmth does not.
Should I downgrade if my iPhone keeps overheating?
If it has not settled after five days and the Battery screen does not identify a single culprit app, yes — restore the previous version from the backup you made before installing.