Sunday, 22 November 2026

Trusted News Discovery โ€“ Powered by AI and Verified by Humans

iPhone browsers still run Apple's WebKit outside the EU and Japan under App Store rule 2.5.6

Apple's WebKit still powers Chrome, Firefox and every other iPhone browser outside the EU and Japan because App Store rule 2.5.6 requires it.

Produced with AI assistance and reviewed by the Badiyaa Editorial Desk. How we work.

Grok Fact CheckCheck it yourself in one tapVerify with Grok ↗Ask @grok on X ↗
A hand holds up an iPhone in a park in Paris.
Image: Lubo Minar, CC0 via Wikimedia Commons

Open Chrome, Firefox or Edge on an iPhone in the US, UK or Canada and the page is drawn by the same engine as Safari: Apple's WebKit. One line in Apple's rulebook makes that happen, and two short regional exceptions show exactly what it takes to break it.

The line is guideline 2.5.6 of Apple's App Review Guidelines: "Apps that browse the web must use the appropriate WebKit framework and WebKit JavaScript." The same entry now adds that developers "may apply for an entitlement to use an alternative web browser engine," and points to separate rules for the European Union and Japan.

Browser versus engine

A browser is the app you tap: the tabs, the address bar, the sync, the settings. The engine underneath is the part that reads HTML, CSS and JavaScript and turns them into a page. Mozilla explains the split in a March 2026 post on its policy blog, which counts only three widely used engines left in 2026, down from five in 2013: Apple's WebKit, Google's Blink and Mozilla's Gecko. The post describes WebKit as the engine "which companies are required to use to build on iOS."

So Chrome for iPhone keeps Google's interface and accounts, but not Blink. Wikipedia's WebKit entry says it plainly: Chrome for iOS uses WebKit "because Apple requires that web browsers on that platform must do so." WebKit itself traces back to KDE's KHTML code from 1998 and was started inside Apple in 2001.

The two doors Apple has opened

Apple now publishes two near-identical sets of terms for engines other than WebKit:

In both places the app must be distributed only in that region and must hold Apple's default-browser entitlement before it can ask for the Web Browser Engine Entitlement. That is the core reason a single global non-WebKit iPhone browser does not exist: an engine swap is allowed region by region, so a company that wants one would have to maintain a separate app for each permitted market and keep shipping WebKit everywhere else.

The test scores and the 30-day clock

Getting through the door is also a real engineering job. Apple's requirements, the same in both regions, ask the engine to pass 90% of the Web Platform Tests and 80% of Test262, the JavaScript conformance suite, and to keep hitting those numbers even when just-in-time compilation is switched off, for example in Lockdown Mode.

Security rules come next. The engine must use memory-safe languages or memory-safety features for all code that processes web content, use process separation, and publish a vulnerability disclosure policy. Actively exploited flaws in the simplest classes should be fixed in about 30 days. Third-party cookies must be blocked by default, and storage has to be partitioned per website.

Apple frames the rules as protection, writing that browser engines "are one of the most common attack vectors for bad actors." Mozilla frames the stakes differently, arguing that Gecko gives the web "an independent voice" beyond Apple and Google.

Badiyaa has tracked other Apple rulebook changes, including Apple's October update to its App Store rules on AI deepfakes, and the wider browser scene, from Cloudflare's open-source Kitesurf browser for AI agents to Winedroid running Android apps inside a web browser.

For anyone outside the EU and Japan, the rule to watch stays numbered 2.5.6. Until its first sentence changes, every iPhone browser in the rest of the world ships with WebKit inside.

Sources

Image: Lubo Minar, CC0 via Wikimedia Commons

This article was produced with AI assistance and reviewed by our Editorial Desk. How we work.

Grok Fact CheckCheck it yourself in one tapVerify with Grok ↗Ask @grok on X ↗