The iOS 28 developer beta is expected to go live on June 7, 2027, within hours of the WWDC keynote ending — and if past years are any guide, several million people will try to install it that same evening. The process itself is genuinely simple. The problems people run into are almost never about the install; they're about the preparation they skipped. This guide walks through the whole thing in order: what to do now, what to do on keynote day, and what to do when something doesn't behave.
One thing to be clear about up front: everything below uses Apple's official beta channel. There is no legitimate "iOS 28 IPSW download" floating around ahead of Apple's own release, and any site claiming otherwise before June 7 is somewhere between wrong and dangerous. The official path is free, takes minutes, and doesn't involve trusting a stranger's server with your phone.
What you need before you start
Three things, none of them expensive:
- A supported iPhone. We expect iOS 28 to run on the iPhone 13 and newer, with the iPhone 12 genuinely on the bubble. The full breakdown — including which Apple Intelligence features need which chip — is on our supported devices page. If your phone can run iOS 28, it can run the beta; there's no separate hardware bar.
- An Apple Account. The same one you already use for iCloud and the App Store. You do not need the paid $99/year developer program — since 2023, Apple has offered developer betas to anyone who signs in at developer.apple.com and accepts the developer agreement. The paid tier is for shipping apps, not for running betas.
- A computer for one backup. Any Mac or Windows PC, borrowed is fine. You'll need it for ten minutes, and those ten minutes are the difference between a bad beta experience being an anecdote or a disaster.
Step 0: Make an archived backup (the step everyone skips)
Here's the trap that catches beta testers every single year. iCloud backs your phone up automatically, so it feels like you're covered. But a backup made while running iOS 28 cannot be restored to a phone running iOS 27 — backups don't restore backward onto older software. If you install the beta, hate it, and downgrade, every backup your phone made during the beta period is useless to you. The only complete road back is a backup made before you upgraded, preserved so nothing overwrites it.
That's what an archived backup is:
- Connect your iPhone to a Mac (it appears in the Finder sidebar) or a Windows PC (use the Apple Devices app).
- Select the phone, tick "Encrypt local backup" and set a password you'll remember — encryption is what lets the backup include Health data, saved passwords, and call history.
- Click Back Up Now and let it finish.
- On a Mac, open Manage Backups, right-click the backup you just made, and choose Archive. That padlocks it: future backups get written alongside it, never over it.
Done. You can now experiment with a clear conscience.
Step 1: Enroll your Apple Account at developer.apple.com
You can do this today — enrollment carries forward, so getting it out of the way now means one less queue to sit in on keynote day.
- Go to developer.apple.com in any browser and click Account.
- Sign in with your Apple Account and complete the two-factor prompt on your phone.
- Read and accept the Apple Developer Agreement when asked. That's the whole ceremony — no payment screen, no application, no review period.
The critical detail: the Apple Account you enroll here must be the same account your iPhone is signed into (check Settings, then tap your name at the top). If your phone uses a family member's account, the beta toggle in Step 2 won't appear, and this mismatch is quietly responsible for a huge share of "the beta isn't showing up" complaints.
Step 2: Turn on beta updates on your iPhone
From here everything happens on the phone:
- Open Settings → General → Software Update.
- Tap Beta Updates. (If the row is missing, revisit the account mismatch above — it's almost always that.)
- Select iOS 28 Developer Beta from the list.
- Go back one screen. The beta now sits where a normal update would.
Step 3: Download and install
Tap Download and Install, agree to the terms, and let the phone do its thing. Practical notes for day one:
- Stay on Wi-Fi and power. First betas are large — typically well over 10 GB once expanded — and installing on a low battery is asking for trouble.
- Expect the download to crawl on June 7. Millions of devices hammer Apple's CDN in the first hours after the keynote. A download that stalls at 90% isn't broken; it's queued. Waiting an hour beats restarting it five times.
- Budget 30–60 minutes total from tap to lock screen, including the "verifying update" pause that always feels longer than it is.
The first 24 hours: what's normal and what isn't
Normal: the phone running warm for an evening while Spotlight and Photos reindex; battery life noticeably worse for the first few days; a handful of third-party apps crashing until their developers ship updates. Worth acting on: cellular data or CarPlay failing outright, or a banking app you depend on refusing to launch — those are the moments you'll be glad the archived backup exists. Our downgrade guide covers the way back, and the honest pre-install decision framework is in the main iOS 28 beta guide.
Quick troubleshooting
- Beta Updates row missing? Account mismatch between the phone and developer.apple.com, nine times out of ten. The tenth time: the device isn't supported.
- "Unable to Verify Update"? Server congestion. Toggle Wi-Fi, wait, retry. Deleting the downloaded update in Settings → General → iPhone Storage and re-downloading is the reliable fix.
- Stuck on the Apple logo after install? Rare, recoverable: force-restart (volume up, volume down, hold side button). If it loops, connect to your computer and restore — then that archived backup earns its keep.
And when can you actually do all this?
Steps 0 and 1 — today. Steps 2 and 3 unlock the moment Apple flips the switch, which we project for the afternoon of June 7, 2027, Pacific time; the full reasoning is on our release date analysis. If you'd rather not refresh Settings all day, the newsletter sends exactly one email when the build is live. If you're still deciding between tracks, read developer beta vs public beta first — for most people with one phone, July's public beta is the smarter entry point.