PPlatformAppStores

Safari Extensions

Browser

Apple Inc. · Browser & OS extension stores

Best for: WebExtension developers targeting Safari and Apple platforms.

Overview

Safari Web Extensions are browser extensions for Apple's Safari, built on the cross-browser WebExtensions standard, so Chrome and Firefox extensions can largely be ported. Unlike other browsers, Safari does not have a standalone extensions store: every extension must be wrapped in a native macOS (and/or iOS/iPadOS) app and distributed through the Mac App Store / App Store, then enabled in Safari's settings.

This means distribution inherits the full Apple pipeline — an Apple Developer Program membership ($99/year), submission through App Store Connect, and mandatory App Review. Apple has reduced friction with a Safari Web Extension packager that converts a ZIP upload into a submittable package without needing Xcode, but the review gate and native-wrapper requirement still make this a higher-complexity surface than other browser stores. Because the container is a real App Store app, monetization can use standard Apple in-app purchases (Apple as Merchant of Record), whereas the extension logic authenticates users via the WebExtensions identity/OAuth2 APIs. The upside is reach into Safari's large macOS/iOS user base; the tradeoff is Apple's fees and review rigor.

How to build & ship

  1. 1Enroll in the Apple Developer Program (about $99/year)
  2. 2Build a Safari Web Extension with the WebExtensions API (HTML/CSS/JS), or convert an existing extension using Xcode's web-extension converter
  3. 3Wrap the extension inside a companion macOS/iOS app target in Xcode and sign it
  4. 4Configure the listing in App Store Connect
  5. 5Submit the containing app for App Review and distribute via the App Store

Key APIs & SDKs

WebExtensions API (browser.*)
Xcode Safari Web Extension converter
Swift/SwiftUI (host app)
App Store Connect
SafariServices

Integration types

Extension

Authentication & security

  • Primary auth: None
  • Also supports: OAuth 2.0
  • Security review: Required
  • Safari web extensions are distributed only through the App Store and undergo Apple App Review like any other app.
  • Standard Apple App Review of the containing app plus extension for guideline and privacy compliance, generally within about 24-48 hours.
  • No marketplace-wide rate limit; extensions run against the Safari WebExtensions APIs and any backend they call.
Auth docs Store policies

Monetization

Free
Paid app
Usage-based
Revenue share
Onboarding
$99/year Apple Developer Program membership
Commission
Standard App Store terms: 30%, or 15% under the Small Business Program
Merchant of Record
Apple is MoR for any paid app or in-app purchase

Pros & cons for builders

Pros

  • Reuses standard WebExtensions code
  • Distributes to Safari on macOS and iOS
  • Benefits from App Store trust and payments

Cons

  • Requires a paid Apple Developer account and Xcode/macOS
  • Must be wrapped in a native app, adding overhead
  • Smaller extension audience than Chrome

Frequently asked questions

How do I get my app approved on Safari Extensions?

Standard Apple App Review of the containing app plus extension for guideline and privacy compliance, generally within about 24-48 hours.

What authentication does Safari Extensions use?

Safari Extensions apps primarily authenticate with None, also supporting OAuth 2.0.

How is Safari Extensions monetized?

Safari Extensions supports Free, Paid app, Usage-based, Revenue share. Typical commission: Standard App Store terms: 30%, or 15% under the Small Business Program. Onboarding fee: $99/year Apple Developer Program membership.

Is a security review required to list on Safari Extensions?

Yes, Safari Extensions requires a formal security or listing review before apps go live. Safari web extensions are distributed only through the App Store and undergo Apple App Review like any other app.