Exact iPhone and iPad model
iOS Safari hides the exact device model.
The UA says only iPhone or iPad with a frozen OS string. Proxies: screen size (390x844 etc.) and DPR narrow to a generation, and WebGL renderer says Apple GPU. Exact model such as iPhone 15 vs 16 is often ambiguous, about 2 to 3 bits.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- See that it is an iPhone or iPad
- Guess a generation from screen size and pixel density
- See a generic Apple GPU name
- Tell Safari on iPhone from Chrome on Android
It cannot
- See the exact model, like iPhone 15 versus 16
- See your iOS version in detail; it is frozen in the text
- Get a clean answer; some models look the same
- See your serial number or phone ID
Browser support
How a site asks for it
| API | none |
| How access is granted | not-exposed |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | not applicable |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: none
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
proxy: screen width x height, dpr | string | None | pins a size class (e.g. 390x844 at 3x is iPhone 12 to 16) | Not listed |
proxy: WebGL renderer | string | None | Apple GPU, no model | Not listed |
proxy: Sec-CH-UA-Model | string | None | not sent by Safari | Not listed |
Technical limits
- Model fingerprint reduces anonymity set
The story
What it is
iPhone Safari hides the exact iPhone or iPad model from sites.
For you
A site knows you are on an iPhone, but not whether it is an older or a new one. It can still guess from your screen size, which narrows it down a lot.
For makers
Apple freezes the details so all iPhones look alike. Developers must use screen size and graphics hints, which still narrow it to a generation. That keeps tracking weaker but not zero.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game wanted the exact iPhone model for settings and uses screen size and a quick benchmark. | None named |
| developer | A support team wanted the model for bug reports and asks the user or logs screen size. | Sentry |
| ads | An advertiser wanted to target iPhone Pro owners and guesses from screen size. | None named |
| shopping | An accessory shop wanted the model to show the right case and asks you to choose. | None named |
| security | A fraud tool wanted the true model and compares screen and graphics hints. | None named |
| video | A streaming site wanted the model to pick HDR and uses media capability checks. | Netflix |
| analytics | A product team wanted model counts and uses screen sizes as a stand in. | None named |
Risks
- Screen size still narrows it down
Good uses and abuse
Legitimate uses
- None: the browser deliberately withholds it
Known abuse
- Sites attempt proxies to recover it
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | 0 | Rough identifying entropy, when known |
Related capabilities
Related
- Client Hint: device model. Can see the model name of your Android phone or tablet when it asks
Sources
How well checked: Inferred from related behavior.