iOS user agent tokens
Browsers on iOS report an iPhone or iPad platform token with an iOS version and a WebKit/Safari structure. Because Apple requires browsers on iOS to use the WebKit engine, Chrome, Firefox, Edge, and others on iOS share a Safari-like user agent, distinguished only by an added product token where present.
What this means
On iOS and iPadOS, browsers report an iPhone or iPad platform token, an iOS version, and an AppleWebKit/Safari structure. Apple's App Store policy has required third-party browsers on iOS to use the system WebKit engine, so Chrome, Firefox, Edge, and others render with WebKit.
The practical effect: an iOS Chrome and an iOS Safari user agent share the same engine markers. Some apps append a product token (for example a CriOS or FxiOS marker), but the underlying engine is identical.
Why brands look alike
Because the engine is shared, you cannot tell iOS browser brands apart by engine version. If a distinguishing product token is absent, the request looks like Safari. Build detection around the product token where you need the brand, not around engine differences that do not exist on iOS.
Note that regulatory changes may allow alternative engines on iOS in some regions over time; do not hard-code the assumption that iOS always means WebKit going forward.
- Token: iPhone or iPad plus iOS version
- All iOS browsers historically use the WebKit engine
- Brand hints come from product tokens, not engine markers
Practical handling
Group iOS traffic by the device class (iPhone vs iPad) and OS family for analytics, and avoid claiming an exact device model, which the user agent does not provide.
For in-app browsers (web views inside other apps), the iOS user agent may carry additional app markers; treat those as embedded-browser sessions rather than the standalone Safari app.
How it appears in analytics and logs
An iPhone or iPad token with a WebKit/Safari structure indicates an iOS browser. Since all iOS browsers use WebKit, the engine markers are the same across brands; only an added product token (where present) hints at the specific app.
Diagnostic use case
Interpret iOS platform tokens for mobile analytics and understand why every iOS browser looks like Safari, so engine-based detection cannot separate them.
What WebmasterID can help detect
WebmasterID treats iOS tokens as coarse mobile-OS context and does not attempt to separate iOS browser brands by engine, since WebKit makes them identical, keeping mobile analytics honest and privacy-safe.
Common mistakes
- Trying to separate iOS browser brands by rendering engine.
- Reading an exact iPhone model from the user agent.
- Assuming iOS will always mean WebKit despite emerging regional changes.
Privacy and accuracy notes
iOS tokens are coarse OS and device-class context. Apple notably distinguishes iPhone from iPad but not exact models. WebmasterID records only the broad platform family, never an identity or exact location.
Related pages
- Safari user agent on iOS and macOS
Safari's user agent is built around WebKit and a Version token, and differs between macOS and iOS. A notable quirk is that iPadOS can present a desktop-class Safari user agent, which can make an iPad look like a Mac in logs. This page covers the pattern and the platform-specific behaviour.
- iOS in-app browser user agents
When a link opens inside an iOS app's embedded browser, the page renders with WebKit but the user agent often lacks the trailing Safari token that standalone Safari carries. That missing-Safari-token quirk, sometimes with an app-specific marker, is the clue that you are seeing in-app browsing on iOS rather than Safari.
- macOS user agent tokens
Browsers on macOS include a Macintosh; Intel Mac OS X platform token. The macOS version embedded in it is frozen or capped by modern browsers, so it confirms macOS but not the precise release, and it still says Intel even on Apple Silicon for compatibility. Use Client Hints for finer detail.
- WebmasterID docs
Coarse iOS platform context recorded without device fingerprinting.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.