What the iOS 28 beta is — and the two flavors of it
Every June, Apple previews its next major iPhone software at WWDC and immediately opens a months-long public test cycle. For iOS 28, that cycle is expected to begin on June 7, 2027 and run until the final release in September. During those months, Apple ships two parallel tracks:
- Developer beta — the bleeding edge. New builds roughly every two weeks, first in line for new features, and first in line for new bugs. Free to anyone with an Apple Account enrolled at developer.apple.com.
- Public beta — the same software, one step behind. It usually launches in July alongside the third developer build, once the worst issues are shaken out. Enrollment is free at beta.apple.com.
Both are official Apple releases, installed over the air through Settings. There are no IPSW downloads from third-party sites involved — and there never should be. If a site offers you an "iOS 28 download" before Apple's own channels have it, close the tab.
When does the iOS 28 beta come out?
Apple hasn't announced iOS 28 yet — the projections below are built from Apple's remarkably consistent beta cadence over the past decade. For the full reasoning, see our iOS 28 release date analysis.
| Build | Expected | Who gets it |
|---|---|---|
| Developer beta 1 | June 7, 2027 | Enrolled developers (free) |
| Developer beta 2 | Late June 2027 | Enrolled developers |
| Developer beta 3 + Public beta 1 | Early–mid July 2027 | Everyone enrolled |
| Betas 4–8 | July–August 2027 | Both tracks, roughly biweekly |
| Release candidate (RC) | Early September 2027 | Both tracks, after the iPhone event |
| Final release | Mid-September 2027 | All supported iPhones |
Before you install: the 10-minute checklist
Beta installs go wrong in boring, predictable ways, and every one of them is survivable if you prepare. Do these three things first:
1. Confirm your iPhone will run iOS 28
We expect iOS 28 to support the iPhone 13 and newer. Check the full list — including which Apple Intelligence features need which chip — on our supported devices page.
2. Make an archived backup on a computer
This is the step people skip, and it's the only one that matters when things break. An iCloud backup made on the beta can't be restored to a phone running the older iOS — you need a local backup from before you upgrade:
- Connect your iPhone to a Mac (Finder) or Windows PC (Apple Devices app).
- Select your iPhone and choose Back Up Now, with "Encrypt local backup" enabled so health data and passwords are included.
- Crucially: right-click the backup in the device list and choose Archive. This prevents it from being overwritten by newer backups made on the beta.
3. Audit your must-work apps
Banking apps, work MDM profiles, and CarPlay are the classic early-beta casualties. If any of those are non-negotiable in your daily life, wait for the public beta.
How to install the iOS 28 developer beta
Once the beta is live on June 7, the whole process takes about five minutes plus download time:
- Go to developer.apple.com, sign in with your Apple Account, and accept the Apple Developer Agreement. No payment is required — the free tier includes beta access.
- On your iPhone, open Settings → General → Software Update → Beta Updates. (Make sure you're signed in with the same Apple Account.)
- Select iOS 28 Developer Beta.
- Go back one screen — the beta now appears as an available update. Tap Download and Install.
- Keep the phone on Wi-Fi and power until it reboots into iOS 28.
How to install the iOS 28 public beta
The public beta is the better choice for most people — same features, several weeks more polish:
- Enroll free at beta.apple.com with your Apple Account.
- Open Settings → General → Software Update → Beta Updates and select iOS 28 Public Beta.
- Install the update that appears, and you're in. Future public beta builds arrive over the air automatically.
Troubleshooting: when the beta won't cooperate
The same handful of problems show up every single beta cycle, on every version of iOS. None of this is specific to iOS 28 yet — it can't be, since iOS 28 doesn't exist — but these patterns have repeated for years and are worth knowing before you run into them.
Beta Updates doesn't appear in Settings
This is the single most common complaint on beta day. Three things cause it, roughly in order of likelihood: you're signed into a different Apple Account on the device than the one you enrolled with at developer.apple.com or beta.apple.com; the enrollment hasn't fully registered yet and the device needs a restart; or the iPhone itself isn't on the expected supported devices list. Check Settings → [your name] to confirm the signed-in account matches your enrollment, restart the phone, and check again after a few minutes — enrollment sometimes takes longer to propagate than people expect.
The download stalls or crawls
On beta 1 day, Apple's update servers take a beating as a huge share of enrolled devices try to pull the same multi-gigabyte file within the same few hours. If the progress bar barely moves, that's almost always the cause — not your Wi-Fi. Let it run in the background and check back in an hour; restarting the download repeatedly just puts you back at the end of the queue rather than speeding anything up.
"Unable to verify update"
This error means the downloaded file is incomplete or the connection dropped mid-verification — it's rarely a sign of anything actually wrong with your iPhone. Go to Settings → General → iPhone Storage, find the iOS 28 beta update, tap it, and delete it, then go back to Software Update and download it again from scratch on a stable Wi-Fi connection.
Not enough storage
Betas need more free space than the listed download size suggests, because iOS stages the new system files alongside the old ones before it can install and clean up. As a rule of thumb, keep at least twice the listed download size free. Offload unused apps (Settings → General → iPhone Storage → Offload Unused Apps), clear out large videos, and empty Recently Deleted in Photos, which quietly holds onto storage for 30 days after you "delete" something.
Stuck on the Apple logo / boot loop
A brief pause at the Apple logo during a beta install is normal — migrating data for a new major version takes longer than a routine point update. Give it 15–20 minutes before you worry. If the phone restarts repeatedly without progressing, force-restart once (press volume up, press volume down, then hold the side button until you see the Apple logo), and if that doesn't clear it, move straight to a recovery-mode restore rather than trying more force-restarts — see the downgrade section below for the exact steps.
Should you install the iOS 28 beta?
An honest framework, from years of running betas on day one:
- Spare iPhone? Install developer beta 1 the moment it drops. This is what spare phones are for.
- Daily driver, and you like tinkering? Wait for developer beta 3 or the public beta in July. The difference in stability between beta 1 and beta 3 is usually dramatic.
- One phone, and you depend on it? Wait for the September release, or at minimum the late-August betas. A beta phone that can't run your banking app is a genuinely bad week.
What typically breaks in early builds: battery life (often 20–30% worse until beta 3–4), third-party apps that haven't been updated, occasional overheating during reindexing in the first day, and — rarely — cellular or CarPlay regressions that take a full build cycle to fix.
What the first 48 hours actually feel like
Most of what feels alarming right after a beta install is completely normal and temporary. Knowing which is which saves you from panic-restoring over something that would have settled by dinner.
Battery drain is the big one. Expect noticeably worse battery life for the first day or two — Spotlight is re-indexing your content, apps are rebuilding caches, and background analysis (including anything Apple Intelligence-related on eligible devices) runs harder than normal while the system settles in. This typically improves substantially by the second full day.
Apps that refuse to launch are the second most common surprise, and banking and authentication apps are the usual culprits — they often check the OS build against an approved list and simply decline to open, sometimes with no error message at all. This isn't something you can fix on your end; it resolves once the app's developer updates for the new OS, which for major apps is often within the first couple of weeks of the public beta.
UI glitches — a laggy animation, a misaligned button, a widget that needs a respring — are cosmetic bugs typical of early builds and almost always get patched within a build or two.
What should not be waved off: a phone that won't hold any charge at all, apps crashing on every single launch rather than just refusing to open, or a build that never finishes setup. Those are signs to downgrade rather than wait out. For a fuller breakdown of what's a normal beta rough edge versus a real problem, see our guide on whether the iOS 28 beta is safe to install.
Reporting bugs so they actually get fixed
Posting a complaint about a bug on social media feels productive, but it accomplishes nothing — no Apple engineer is triaging posts on X or Reddit. The only channel that reaches the people who can actually fix the bug is Feedback Assistant, Apple's dedicated tool for beta testers. It's preinstalled on every beta build and also available at feedbackassistant.apple.com.
A report that gets acted on looks different from a one-line complaint. Include:
- Exact steps to reproduce — numbered, specific, starting from a known state ("1. Open Camera. 2. Switch to Portrait mode. 3. Tap the shutter twice quickly.").
- What you expected to happen versus what actually happened, described separately.
- How often it happens — every time, intermittently, or just once.
- A sysdiagnose when Feedback Assistant prompts for one. This is a system-level snapshot of logs from around the time of the bug, and it's often the difference between a report an engineer can act on and one they can't reproduce. Trigger it as close to the bug happening as possible — Apple's own guidance is within a few minutes — since the logs it captures are time-limited.
Screen recordings help enormously for anything visual — attach one whenever the bug has a UI component. Duplicate reports aren't wasted effort either: Apple's internal tooling uses report volume on a given issue as one signal for prioritization, so a well-written duplicate of an existing bug still counts for something.
How to downgrade from the iOS 28 beta
Changed your mind? You have two exits, depending on how fast you need out:
The patient way (no data loss)
Turn beta updates off in Settings → General → Software Update → Beta Updates → Off. Your iPhone simply stays on its current build and rejoins the public release track with the next official update — usually iOS 28.0 in September.
The immediate way (restore required)
- Connect the iPhone to your computer and put it in Recovery Mode (press volume up, volume down, then hold the side button until the recovery screen appears).
- In Finder or the Apple Devices app, choose Restore. This erases the phone and installs the current public iOS release.
- During setup, restore the archived backup you made before installing the beta. Backups made on iOS 28 will not restore onto the older version — that archived backup is your only complete path back.
Beta questions that affect your warranty and data
A few things are worth settling upfront, since they shape how you should treat a beta install:
Your hardware warranty is unaffected. Apple distributes betas through its own official enrollment channels, and installing one does not void AppleCare or your standard hardware warranty.
Apple does not provide support for beta-specific software issues. If a beta build itself is misbehaving, Apple support's standard first step is asking you to restore to the current public release before troubleshooting further — the beta isn't a supported product the way a shipped iOS version is.
Data created on the beta is a one-way door. Messages, photos, notes, and settings created after you install the beta live in a database format tied to that beta. If you downgrade, none of that new data comes with you — only a pre-beta archived backup restores cleanly. This is why the backup-before-you-install guide exists as its own resource: it's the single highest-leverage thing you can do before tapping install.
Don't put beta software on a phone you depend on. If losing app access, battery life, or a day of use for troubleshooting would actually disrupt your work or your life, run the beta on a secondary device instead — or wait for a later, more stable build.