What This Site Is
Beta Profiles has tracked Apple's pre-release software since 2022. The name is a leftover from an era that has ended: for roughly a decade, joining an Apple beta meant downloading a configuration profile, and that is what people searched for. Apple removed the mechanism in iOS 16.4, in 2023. We kept the name and changed everything behind it.
What the site does now is narrower and more useful. It records every build Apple ships to its beta channels, with the build number and the date; it answers, model by model, whether your specific device runs this year's release and which features it actually gets; and it documents what goes wrong afterwards and how to get back out. That is 157 pages of it, and none of it requires you to download anything from us.
The audience is people who have already decided to try a beta, or who are trying to decide. Not developers reading API diffs — Apple's own documentation does that better. The gap this site fills is the practical one: will it run, what breaks, and can I undo it.
How We Work
Release data comes from Apple's official developer release feed, polled every 15 minutes and written straight into the site. Nothing is retyped, which is the main reason our build numbers do not carry the transcription errors that spread between sites reposting each other. Our methodology page sets out exactly how the pipeline works and where it can fail.
Every build we record is kept permanently, even after Apple's own feed rolls it off. That archive is what makes the build history possible — the dates, the intervals, the cadence of a cycle — and it is the one thing here that genuinely cannot be found elsewhere.
Device compatibility is maintained by hand against Apple's published lists, and every model page states its chip, memory and storage tiers because those are what actually decide how a beta behaves. The compatibility checker runs off the same data, so it can never contradict the pages.
What We Don't Do
We do not publish rumours, leaks or unverified feature lists. When a new beta lands, its page says what the build number is, when it arrived, how long after the previous one and how to install it — because those are facts. It does not invent a changelog. If Apple publishes release notes, we quote them; if not, the section simply is not there.
We do not host, mirror or link to files that claim to be beta profiles. None of them work, and some of them are configuration profiles carrying proxy or device-management settings — see our piece on what those downloads actually contain. Enrolment is free and takes two minutes through Apple.
We do not tell you a beta is safe on your only phone when it is not. Several pages here argue against installing, and the main-device guide is the clearest example. A site that only ever says yes is a site optimising for something other than your device.
How the Site Is Funded
Advertising, through Google AdSense. That is the whole model — there is no affiliate arrangement with anyone whose products we discuss, no sponsored placement, and nothing on this site is sold. Apple has no relationship with us and no input into what appears here.
The tools are free and run entirely in your browser, which means nothing you test with them is uploaded anywhere. That is a consequence of how they are built rather than a promise you have to take on trust: open the network inspector while using one and you will see nothing leave your device.
Corrections
If something here is wrong, we would rather know. Build numbers, dates, device support and version history are all checkable, and errors in them are worth fixing quickly because other sites copy this kind of data. Write to hello@betaprofile.dev or use the contact page.
Where our records have gaps we say so rather than papering over them. The build history marks intervals as "not recorded" when a build predates the archive instead of measuring across the hole, because a plausible-looking number that is wrong is worse than an honest blank.