You install the beta, and by evening your iPhone is at 40% with barely two hours of screen time. It's warm in your pocket. Every year this triggers the same wave of "is my battery ruined?" posts, and every year the answer is almost always the same: no, this is what a beta looks like on day one, and it's temporary. That doesn't mean beta battery life bad enough to notice is always fine to ignore — some of it is a real, fixable problem — but most isn't, and confusing the two leads people into "fixes" that don't help.
This guide draws on how every recent iOS beta cycle has behaved, written to be useful the moment iOS 28 beta 1 lands: why the drain happens, where the line sits between normal and abnormal, how to read the diagnostics Settings already gives you, and which fixes are worth your time versus which are folklore.
Why every beta drains more at first
The moment a new iOS version finishes installing, your phone starts rebuilding itself around it. Spotlight rebuilds its search index across your apps, messages, and files. Photos re-runs on-device analysis over your library to refresh face groupings, scene detection, and the data behind Memories and search. iCloud reconciles anything that changed format between versions and re-syncs it. None of this is optional or something you triggered; it happens to every device that updates, beta or not, and a beta just makes it more visible because you're watching everything else closely too.
That workload is genuinely CPU- and radio-intensive, which is why the phone runs warm and the battery percentage seems to fall in front of your eyes on day one. It's not a leak or a fault, and it's not something you need to interrupt — it's the same background maintenance a stable-release update triggers, just felt more sharply because beta software layers its own overhead, covered below, on top of it.
Normal vs. abnormal: where the line is
One clear rule so you're not second-guessing your phone all week: settling within two to three days is normal; still severe after a full week is a real problem. The typical trajectory is rough on install day, noticeably better by day two as indexing finishes, and back near your usual baseline by day three. Day-to-day variance after that is just normal usage, not a beta problem.
If you're a week in and the drain hasn't budged, indexing is not the explanation anymore — that job finishes in hours, not days. You're looking at one of two things instead: a specific app that hasn't adapted to the beta, or an actual regression in that build. Both are diagnosable next.
How to actually diagnose it
Open Settings → Battery and give it a minute to load. You're looking at two things: the app-by-app breakdown and the Activity chart above it.
The app list shows each app's share of battery use, split into "screen on" and "background" time. A single app sitting well above the others — especially with most of its usage in the background rather than while you were actively using it — is your rogue app. That's a targeted problem with a targeted fix.
The Activity chart tells a different story. Drain spread thinly across many apps with a large "Other" or system-level share, lining up with the hours right after you installed, points to system-wide reindexing rather than one app misbehaving. Check the 24-hour and 10-day views for whether the curve is already flattening — that alone answers most of "is this normal."
| Symptom | Likely cause | What to do |
|---|---|---|
| Hot phone, fast drain in the first 24–48 hours | Post-update reindexing (Spotlight, Photos, iCloud sync) | Let it finish — charge overnight on Wi-Fi and leave it alone |
| One app eating 20%+ mostly in the background | App not yet updated for this beta, stuck retrying or crashing | Update it if a fix is available, or limit it below |
| Steady drain spread across many apps, none dominant | System-wide beta overhead — logging and unoptimized code | Normal on early builds; expect it to ease with the next update |
| Signal icon flickering, battery falling with cellular use | Network settings conflicting with the beta's radio firmware | Reset Network Settings |
| Still draining fast after a full week, no clear cause | A genuine bug in this specific beta build | Consider downgrading to the stable release |
Fixes that genuinely help
Let indexing finish
The single most effective fix is doing nothing: plug the phone in overnight on Wi-Fi and let the background jobs finish uninterrupted. Interrupting them with airplane mode or forced restarts doesn't skip the work — it just delays it and makes the drain last longer once you turn things back on.
Find and deal with the rogue app
If Settings → Battery points clearly at one app, check the App Store for an update first — developers push beta-compatibility fixes quickly once they see crash reports. If no update exists yet, remove the app until one does, or use the next fix instead.
Turn off Background App Refresh for the offender
Settings → General → Background App Refresh lets you disable the behavior per app rather than system-wide. This stops that one app from working in the background without touching anything else — which keeps your ability to tell what actually fixed the problem intact.
Reset Network Settings if cellular is thrashing
If drain tracks with a flickering signal icon or constant network searching, go to Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings. This clears carrier and Wi-Fi configuration that can conflict with new radio firmware, at the cost of re-entering your Wi-Fi passwords afterward.
Fixes that are myths
Force-quitting all your apps
The most common bad advice in every beta cycle, and it's counterproductive. A suspended background app uses close to nothing. Force-quitting it just guarantees a cold relaunch next time you tap it — which costs more energy than resuming would have.
"Battery calibration" full-drain cycles
Running the battery to 0% and back up to "recalibrate" it isn't a real maintenance step on modern iPhones. Deep discharge adds wear rather than removing it, and there's no calibration process a full drain triggers. Skip it.
Disabling every feature at once
Turning off Background App Refresh, Wi-Fi calling, widgets, notifications, and location services all in one pass might reduce drain — but you'll never know which change did it, and you've given up most of what makes the beta worth running. Change one thing at a time, starting with whatever Settings → Battery pointed at.
Why beta 1 is always the worst build for battery
Early developer betas aren't just less polished — they're built differently. Apple ships extra logging, diagnostic hooks, and instrumentation in the first few builds so crash reports and performance data flow back from testers' devices with enough detail to act on. That instrumentation runs constantly and costs real battery. The code is also compiled without the optimization passes a release candidate gets, so it runs less efficiently on beta 1 than it will by September.
That overhead gets pulled back build by build as Apple's telemetry needs shrink — the reason beta 1 is reliably the roughest build of the year, with each later beta feeling a little lighter even before your own apps catch up. Track which build you're on with our beta build tracker.
When to just downgrade
If you've checked the app-by-app breakdown, ruled out a misbehaving app, given indexing a few days, and drain is still severe a week in, you're dealing with a bug in that build. The fastest path back to normal battery is downgrading to the current stable release rather than waiting out future betas. Our downgrade guide walks through it, and it only works cleanly with an archived backup made first — see our backup guide if you skipped that.
If battery anxiety is what's holding you back from installing at all, joining later sidesteps most of this — see our developer vs. public beta comparison and whether the beta is safe to run.
Common questions
How long should iOS 28 beta battery drain last?
Expect the worst of it in the first 24 to 48 hours, while the phone finishes reindexing Spotlight, Photos, and iCloud data in the background. Battery life should visibly improve by day two and be near normal by day three. Still severe after a full week means it's no longer the indexing — it's something else.
Does force-quitting apps help battery life on the beta?
No, and it can make things slightly worse. iOS already suspends apps you're not using, so they draw almost no power sitting in the app switcher. Force-quitting them just means the next time you open one, it has to fully relaunch from scratch, which costs more battery than resuming would have.
Will a later beta build fix the battery drain?
Usually, yes. Early betas ship with extra logging and debugging instrumentation that Apple strips out as the cycle progresses, so beta 1 is reliably the worst build for battery and it improves with each update. If a specific build introduced new drain earlier builds didn't have, that's a regression worth watching for a fix in the next release.
The verdict
Bad battery life for the first day or two after updating isn't a sign anything is wrong — it's maintenance your phone has to do once per update, beta or not. Give it two to three days and check Settings → Battery before touching a single toggle. If a rogue app shows up, deal with that app specifically. If nothing does and a full week passes with no improvement, stop troubleshooting and read the downgrade guide instead. For everything else about getting set up, the main iOS 28 beta guide is the place to start.