If you browse the web on an iPhone or iPad, your experience is governed by a single, unyielding rule: every web page you see is drawn by Apple’s own technology, WebKit. On iOS and iPadOS, all store-distributed browsers must use Apple’s rendering engine and JavaScript stack. Familiar names like Chrome, Firefox and Edge are present, but on Apple’s mobile platforms they are WebKit-based shells rather than their Blink- or Gecko-based desktop counterparts.

For most of the world, including Canada and the United States, that remains the status quo. Apple created a path for authorised non-WebKit engines in the European Union with iOS 17.4 via a new framework called BrowserEngineKit; elsewhere, the WebKit requirement still applies. Japan has passed legislation that will require Apple to permit third-party browser engines by December 2025.

The digital gatekeeper: Apple’s WebKit requirement

At the heart of any browser is an engine that interprets HTML, CSS and JavaScript to render the modern web. On iOS and iPadOS, Apple’s App Store Review Guideline 2.5.6 states that apps which browse the web “must use the appropriate WebKit framework and WebKit JavaScript,” with alternative-engine use allowed only under Apple entitlements (EU-only at present). The result is a monoculture in which iOS browsers inherit the same capabilities and constraints as Safari.

Apple’s rationale: a fortress of security

Apple argues that a single, centrally controlled engine simplifies patching and reduces platform risk. Historically, just-in-time (JIT) compilation on iOS has been reserved for WebKit; the EU entitlements extend engine and related capabilities (subject to Apple’s conditions) only within the EU. Outside those jurisdictions, third-party engines cannot ship with their own JIT.

Critics counter that the rule also limits competition and weakens Progressive Web App capabilities on iOS. The United Kingdom’s competition regulator concluded that the supply of mobile browsers and browser engines is not working well, with Apple’s controls harming competition and innovation. Using the regulator’s language keeps the analysis focused on competitive effects rather than motives.

Implementation in the EU and Japan

To comply with the EU’s Digital Markets Act, Apple introduced BrowserEngineKit in iOS 17.4, allowing authorised non-WebKit engines for EU-distributed apps under specific technical and policy requirements. In Japan, enforcement guidance indicates a December 2025 deadline for lifting the engine ban. These developments do not change the Canadian position today.

Fortifying Safari: what changed in iOS 26

With iOS 26 (announced June 2025; feature notes published in September 2025), Apple expanded Safari’s privacy posture with documented changes that affect day-to-day browsing:

  • Advanced Fingerprinting Protection for all browsing. Previously limited to Private Browsing, this now applies across Safari, reducing passive signals (such as fonts or device metrics) that can contribute to unique identification.
  • Web app behaviour. “Add to Home Screen” now lets any page open as a full-screen web app and appear in the App Switcher.
  • Tab layouts. New Compact, Bottom and Top designs (a user-interface change rather than a privacy control).

Related protections that pre-date iOS 26 remain available, including Locked Private Browsing (Face ID, Touch ID or passcode) introduced in iOS 17. Apple has not announced new default-on changes to cookie partitioning or IP-address hiding beyond the fingerprinting update above.

A challenger appears: Orion browser

Orion, from Kagi Inc. (the privacy-focused, subscription-funded Kagi search company founded by Vladimir Prelovac), is a WebKit-based browser for macOS, iOS and iPadOS with a zero telemetry policy and built-in ad and tracker blocking. Orion also documents preliminary support for Chrome and Firefox extensions on iOS and iPadOS, within Apple’s platform constraints. On iPhone and iPad, Safari and Orion share the same engine class; differences are in product choices, defaults and extension packaging.

The field of alternatives on iOS

All of the following browsers use WebKit on iOS and iPadOS outside the EU alternative-engine programme.

Opera: integrated services

Opera for iOS includes a built-in ad blocker, a free no-log VPN, and Aria AI features available on mobile.

DuckDuckGo Privacy Browser: the privacy simplifier

DuckDuckGo offers tracker blocking, Cookie Pop-up Protection (automatically selects the most private option and hides banners), and the Fire Button to clear recent on-device browsing data.

Brave: default blocking and optional VPN

Brave on iOS provides Shields (ad, tracker and fingerprinting protections) and an optional Firewall + VPN powered by Guardian. Brave does not offer Tor windows on iOS.

Where this is headed

  • European Union: Apple authorises alternative engines via BrowserEngineKit under defined terms (iOS 17.4 and later).
  • Japan: Enforcement guidance targets December 2025 to lift the engine ban.
  • Canada, United States and most other regions: The WebKit requirement remains in force.

Bottom line

On iOS and iPadOS, users can choose among many browsers, but—outside the EU (and Japan from late 2025)—they cannot choose among browser engines. iOS 26 raises Safari’s privacy floor by enabling Advanced Fingerprinting Protection across all browsing. Competitors differentiate through policy, packaging and features (for example, Orion’s zero telemetry and extension support; Opera’s free VPN and Aria; DuckDuckGo’s consent handling and Fire Button; Brave’s Shields and optional Guardian-powered VPN). The engine rule still determines the bounds of competition on Apple’s platforms; regulation, not technology, is what changes that picture.

Keywords: #iOS #iPadOS #Safari #WebKit #BrowserEngineKit #DigitalMarketsAct #EU #Japan #SmartphoneAct #CMA #Privacy #Security #AdvancedFingerprintingProtection #LockedPrivateBrowsing #ProgressiveWebApps #JIT #WebBrowsers #OrionBrowser #Kagi #DuckDuckGo #BraveBrowser #OperaBrowser #AdBlocking #TrackerBlocking #Fingerprinting #FirewallVPN #CookiePopupProtection #AppStore #Guideline256 #CanadaTech #MobileWeb #iPhone #iPad #Regulation #Competition