"Don't run the beta on your main iPhone" is the single most repeated piece of advice in every beta-season thread — and almost nobody follows it up with how. Which phone qualifies? Do you need a phone plan for it? Which Apple Account should sign in? This guide answers the part everyone skips.
The short version: an old, currently-supported iPhone, set up fresh rather than restored, connected to Wi-Fi with no SIM required, is all it takes. The details below cover exactly what that means and where the real trade-offs sit.
Any iPhone that still appears on the current supported-devices list can serve as a second iOS 28 beta phone — an unsupported one is useless for this regardless of condition. You do not need a SIM card or cellular plan; Wi-Fi handles enrollment, downloads, and almost all app testing. Set the device up as new rather than restoring your main backup, sign in with either your real Apple Account (for realistic testing) or a separate one (for clean isolation), then enroll it at Settings → General → Software Update → Beta Updates.
What actually makes an old iPhone usable for this
Before anything else, confirm the phone is eligible. Apple has never restored support for a chip generation it already dropped from the current cycle, so if a phone can't run this year's iOS release, it will not run next year's beta either — an iPhone too old for iOS 28 is simply not a candidate, no matter how good its battery or how much free storage it has.
Eligibility tracks the chip, not the launch date. The iPhone 11 and the iPhone SE (2nd gen) both run the A13 and remain supported through iOS 27. The site's current projection for iOS 28 — reasoning from Apple's historical pattern, not a confirmed cut — is iPhone 13 and newer expected, with the iPhone 12 uncertain. The full breakdown, updated as the picture sharpens, lives on our supported devices page, and you can check a specific model against it on the compatibility checker.
Before you commit a specific unit, confirm its exact model under Settings → General → About — "iPhone 13" and "iPhone 13 Pro" run the same silicon, but generation labels get misremembered constantly once a phone has spent a couple of years in a drawer. Don't worry about whether it also qualifies for Apple Intelligence; that needs an iPhone 15 Pro or newer this cycle, and the more advanced on-device features need even more recent hardware. None of that matters for a spare test device — you're checking for baseline iOS 28 eligibility, not the top tier of features.
Do you need a SIM card or a cellular plan?
No — and this is the misconception that stops most people from ever setting up a second device. A test iPhone doesn't need an active phone number, a carrier, or even a SIM tray filled. Wi-Fi alone lets you complete Setup Assistant, sign into an Apple Account, enroll in the beta program, download every build over the air, and install and run whatever apps you're checking for compatibility.
The only reason to want cellular is if you're specifically testing carrier-dependent behavior — VoLTE call quality, 5G band handling, a carrier's own settings app — which is a narrow slice of what most testers actually care about. If your goal is "does my banking app still open," "does this game still launch," or "does the new OS feel stable," Wi-Fi is the entire infrastructure you need. A retired iPhone with no line on it is not a limitation here; it's the normal setup.
Real Apple Account or a separate one — the honest trade-off
This is the decision with no universally correct answer, because it depends on what you're actually trying to learn. Signing in with your real Apple Account gives you a phone that behaves like your daily driver — your apps, your purchase history, your subscriptions. Signing in with a separate Apple Account gives you a clean, isolated test bed that tells you very little about your own life on iOS 28.
| Dimension | Real Apple Account | Separate Apple Account |
|---|---|---|
| App compatibility testing | Your actual purchased and installed apps, exactly as configured | Only what you manually add — usually free apps, from scratch |
| iCloud data exposure | Your photos, contacts, and messages sync onto a beta OS | None — your real data never touches the device |
| Two-factor prompts | Your main phone gets approval requests every time the beta device signs in or updates | No cross-device prompts at all |
| Realism of the result | High — mirrors what will actually happen on your daily driver | Low — an empty phone tells you little about your real usage |
| Setup effort | Minimal — sign in and everything is already there | Higher — new Apple ID, apps re-added and re-subscribed individually |
| Best suited for | Deciding whether your actual daily life survives the upgrade | Judging raw OS stability and UI without any personal data at risk |
Most people land in the middle: use the real Apple Account for App Store and iCloud so the phone reflects reality, but skip syncing anything you'd mind losing to a rough beta build. There's no wrong choice here — just a trade-off worth making on purpose instead of by default.
Setting it up from scratch — not from a backup
The instinct is to restore your main iPhone's backup onto the spare so it "matches." Resist it. A beta test device works best lean, and restoring a full backup defeats most of the point of having a second phone at all.
Why restoring your main backup is the wrong move
A full restore drags over years of accumulated apps, login sessions, configuration profiles, and cached junk — turning your spare into a miniature copy of your main phone rather than a clean testing surface. It also makes the device slower to reset, and resetting cleanly is exactly what you'll want to do at the start of every new beta build. A phone loaded with everything you own is harder to wipe and start over than a phone loaded with just what you need to test.
Erase it and go through Setup Assistant fresh
If the phone has old data on it, go to Settings → General → Transfer or Reset iPhone → Erase All Content and Settings first. When Setup Assistant starts, choose "Set Up as New iPhone" rather than restoring from any backup — iCloud or computer-based. Sign in with whichever Apple Account you decided on above, set up Face ID or Touch ID, and connect to Wi-Fi when prompted.
Add only what you actually need to test
Install the specific apps you want to verify against iOS 28 — the ones you actually rely on daily, not your entire App Library. Sign into each account only as needed. A test phone with ten deliberately chosen apps tells you more than one cluttered with two hundred you'll never open during the beta.
Skip the paid iCloud storage plan
A second iPhone doesn't need its own iCloud+ subscription. If you signed in with your real Apple Account, it shares whatever plan your main devices already use. If you went with a separate Apple Account, the free tier is plenty — you're not archiving a photo library on this phone, just running apps and checking whether they behave.
Enrolling the second device in the beta
Once the phone is set up, enrollment itself is the easy part. For the developer beta, create a free account at developer.apple.com using the Apple Account signed into the phone, then turn it on under Settings → General → Software Update → Beta Updates. For the public beta, you'll instead install the configuration profile from beta.apple.com once it opens in July. Our developer beta install guide and public beta install guide walk through each path step by step, and the developer vs. public beta comparison helps you pick between them if you're not sure which track suits a spare device.
Because this is a spare phone rather than your daily driver, you can safely take the roughest entry point — developer beta 1, the first day it exists — with none of the downside that makes that choice risky on a primary phone. If you'd rather understand the full risk picture before deciding, our beta safety guide lays out exactly what does and doesn't go wrong.
What a second iPhone can and can't meaningfully tell you
A spare device is genuinely useful for some things and close to useless for others. Knowing which is which saves you from drawing the wrong conclusion from your own testing.
What it's good for
App compatibility is the headline use case — does a given app launch, does it crash, does it render correctly, does a banking or work app refuse to run on a beta OS at all. It's also a solid way to explore new features, judge general day-to-day stability, and catch obvious UI bugs before they'd surprise you on your main phone.
What it can't tell you
Your real daily battery life is the biggest blind spot. Battery behavior depends on that exact device's battery health, its age, and your specific usage pattern — a spare phone sitting mostly idle on a desk tells you nothing about how iOS 28 will drain your actual daily driver. Our battery drain guide covers what's normal for early builds if you want that context anyway. Cellular-specific issues, CarPlay pairing you rely on, and anything tied to your real routine are similarly out of reach unless you go out of your way to replicate them on the spare.
Notifications and background behavior are a smaller, easy-to-miss gap. A phone you don't carry around and check all day won't surface the same push-notification timing quirks or background-refresh issues a beta can introduce on a device that's actually in your pocket. Treat a spare phone as a compatibility and stability check, not a substitute for eventually running a build on the device you actually use — once the rough edges are gone.
Where to find a cheap, supported device
You don't need to buy anything new, and in most cases you don't need to buy anything at all. The most common source is the phone that's already sitting in a drawer — last year's or the year-before's iPhone, retired when you upgraded but never wiped or given away. A hand-me-down from a family member who just upgraded works the same way. If neither exists, a refurbished older model through any general, reputable channel fills the gap — the only requirement is that the specific model still appears on the current supported-devices list.
Storage capacity and battery health matter far less here than they would for a daily phone. Since you're not testing real-world battery life on this device anyway, a well-worn battery is a non-issue; a smaller storage tier is fine as long as it fits the beta download and the handful of apps you actually plan to test. The one thing that isn't negotiable is chip generation — check the supported devices page before you commit a drawer phone or a refurbished purchase to this role.
Before pressing it into service, do a quick sanity check regardless of where it came from: make sure it powers on and holds a charge long enough to get through Setup Assistant, that the screen is intact enough to actually use, and that it isn't still tied to someone else's Apple Account through Activation Lock. That last one is the only real dealbreaker — a locked phone can't be set up as new no matter how good a candidate it otherwise is, so confirm it's been signed out and erased by its previous owner before you rely on it.
Putting it together
The advice to keep the beta off your main iPhone has always been sound — the missing piece was just the how. Confirm the phone is on the current supported list, skip the SIM entirely, decide deliberately between your real Apple Account and a separate one using the trade-off above, set the device up fresh instead of restoring a backup, and enroll it through Settings once it's ready. Do that, and the worst-case outcome of any beta bug is an afternoon spent on a phone you weren't using anyway — while your actual daily driver never sees a beta build at all.