An extension inside an app

Safari Web Extension Development: Converting a Chrome Extension With Apple's Packager, Xcode and the App Store

Safari is the only major browser that wants your extension to arrive inside an app. The code is mostly the JavaScript you already wrote for Chrome. The wrapper, the Apple account and the App Store are what is new, and they are where Chrome developers stall.

November 17, 2026 · 9 min read

acmeinvoicing.com · safari packager report
A billing extension, run through Apple's packager
Two manifest keys to sort before the estimate
  • PassXcode project created with a macOS app
  • PassContent scripts and options page carried over
  • PassiOS target added with --rebuild-project
  • WarnManifest keys Safari does not support2 keys
  • WarnAccount connection tested in Safaripending
  • PassApple Developer Program in the client's name
Illustrative: a sample packager report for a fictional invoicing company's extension

The short answer

Safari web extension development means packaging a WebExtensions extension inside a macOS or iOS app. Apple's tool, xcrun safari-web-extension-packager (formerly safari-web-extension-converter), creates the Xcode project from an existing extension. App Store distribution requires the Apple Developer Program, 99 USD per membership year as of November 2026. DataCram builds and converts Safari extensions from $1,500, depending on complexity.

On this page
  1. Why Apple ships every Safari extension inside an app
  2. Apple's packager, the tool formerly called the converter
  3. Two roads to Safari users: the App Store or your own download
  4. The Apple account, the yearly fee and a review we will not time
  5. GatorCrawl Keywords, run through Apple's packager
  6. How DataCram delivers a Safari extension
  7. Whether Safari earns a place in your budget

Why Apple ships every Safari extension inside an app

Somewhere a product manager has just been told the Safari version is "basically a rewrite." It is not. Apple's Safari web extensions documentation says such an extension "adds custom functionality to Safari using JavaScript APIs and common file formats from extensions for Google Chrome, Mozilla Firefox, and Microsoft Edge browsers." Your content scripts, your options page and your manifest mostly come along. For a SaaS companion extension, the account logic on your server does not change at all.

What changes is the container. The same Apple page says "You implement a Safari web extension as a macOS, visionOS, or iOS app extension to provide a safe and secure distribution and usage model." Users install an app, and the app installs the extension. That model is why Safari extensions go through Xcode and App Store Connect rather than a browser store's upload form.

The payoff is reach. Apple says "Safari web extensions are available in macOS with Safari 14 and later, visionOS 1 and later, and iOS 15 and later." If your users work on MacBooks and check things on iPhones, Safari is where they already are, and an extension that skips it skips them. Apple's Safari extensions page adds that Xcode "includes a porting tool to make it easy to bring your extensions to Safari." Easy is Apple's word. Mostly true, in our reading, with the exceptions below.

Apple's packager, the tool formerly called the converter

Apple renamed the tool. Its packaging guide, read in November 2026, gives the command as xcrun safari-web-extension-packager /path/to/extension and notes: "This tool used to be named safari-web-extension-converter." Older tutorials use the old name. Same idea, new label.

Turning an existing extension into a Safari release, per Apple's documentation as of November 2026
StepWhat you useWhat you get
Packagexcrun safari-web-extension-packager, pointed at the extension folderAn Xcode project configured "with a macOS app or iOS app that installs the extension in Safari"
Read the reportThe packager's outputA list of "any manifest keys that the current version of Safari doesn’t support"
Add iPhone and iPadThe packager's --rebuild-project option on an existing projectAn iOS target beside the macOS one
No Mac in the officeUpload a ZIP of the extension to App Store ConnectApple converts and packages it "for testing", with no Mac or Xcode needed
PublishApp Store ConnectA listing on the App Store, in the Extensions category
Ship outside the Mac App StoreA Developer ID, signed and notarizedA Mac app you distribute yourself

The report is the most useful page of the whole process. It tells you, before anyone writes a line of Safari code, which parts of the manifest Safari will ignore. We read it first and write the estimate second. Sources: Apple's packaging guide, its Safari extensions page for the App Store Connect upload, and its distribution guide for Developer ID.

Two roads to Safari users: the App Store or your own download

Warm shallow-focus desk with an open laptop showing a blank glowing screen, a phone face down, a notebook and a coffee cup, hands near the keyboard
A Safari extension is packaged and tested at a desk in Xcode, then shipped inside an app.

Apple offers two ways out of Xcode. The App Store is the obvious one. The distribution guide describes the other: "you can sign and notarize your extension’s app with a Developer ID to distribute it outside the Mac App Store." Which suits you depends on who installs it.

The App Store suits

  • A public extension that strangers should be able to find
  • Anything that needs to run on iPhone or iPad
  • Products where an App Store listing is part of the trust story
  • Customers who expect to find software in the App Store

Developer ID suits

  • A Mac-only tool for your own staff or partners
  • A company that already distributes its own Mac software
  • Cases where a public listing would confuse customers
  • A pilot you want in a few hands before any store sees it

The Apple account, the yearly fee and a review we will not time

Apple's Safari extensions page sets the gate: "To distribute Safari Extensions, you need to be a member of the Apple Developer Program." Apple's program page prices it: "The Apple Developer Program is 99 USD per membership year, or in local currency where available," and "Eligible nonprofit organizations, accredited educational institutions, and government entities can request a fee waiver." The enrollment page adds that "Prices may vary by region." All as of November 2026.

Notice the word membership year. Chrome's developer fee is one-time; Apple's renews. That makes the Apple account a running cost of owning a Safari extension, and it is one more reason the account should be in your company's name. If the membership lapses while it sits in a contractor's name, so does your control of the listing.

On review, Apple says this: "Apple reviews all extensions and updates to ensure they work reliably." That is the whole of what we can tell you. We did not research App Store review times for this page, so we state none, and we promise no approval. What we control is a submission that works on the first run, describes itself plainly and asks for no more access than its job needs, the habits our permissions and privacy page lays out. Google's store words its review differently, as the Chrome Web Store review page shows, and Mozilla's signing is covered under Firefox extensions.

GatorCrawl Keywords, run through Apple's packager

DataCram built GatorCrawl Keywords, a keyword research web app, and a Chrome extension for it. The extension shows keyword numbers on Google's results pages, adds a right-click lookup, keeps settings on an options page and connects to the user's account through the web app. Here is how we would approach a Safari version of it.

  1. 1.Point the packager at the extension folder and keep the Xcode project it creates under version control from the first minute.
  2. 2.Read the unsupported-keys report line by line. The manifest is small: a service worker, one content script on Google's results pages, two permissions, an options page and one host permission for the GatorCrawl app.
  3. 3.Test the account connection first. The extension accepts a token from the web app's connect page only from the configured app origin, and that hand-off is the first thing we would prove works in Safari.
  4. 4.Test the content script's bar under the search box and the right-click lookup window on a Mac, then decide with the owner whether an iPhone target earns its keep.
  5. 5.Submit under the owner's own Apple Developer Program membership, not ours.

We would not guess which keys Safari ignores. The packager says, and the test runs confirm. That habit, read the tool's report before quoting, is the difference between an estimate and a hope. The Chrome build itself is documented part by part in how we built the GatorCrawl extension.

How DataCram delivers a Safari extension

  1. 1

    Scope the job

    One purpose, the sites it touches, the permissions it needs, and whether iPhone matters to your users.

  2. 2

    Build or adapt the shared code

    New extensions start cross-browser. Existing Chrome extensions are read first and quoted after.

  3. 3

    Package and read the report

    Apple's packager creates the Xcode project, and its list of unsupported keys becomes the Safari work list.

  4. 4

    Test on real devices

    Safari on macOS, and on iOS if it is in scope, covering sign-in, the main job and saved settings.

  5. 5

    Submit and hand over

    App Store Connect under your Apple account, with the Xcode project, source and notes handed to you.

If the extension needs a full companion app, more than the thin wrapper Apple's packager makes, that is iOS app work, and our iOS app development team handles it as a separate conversation. Most extensions do not need it. The wrapper exists to install the extension, and that is often all it should do.

Whether Safari earns a place in your budget

Build for Safari when your users are on Macs and iPhones and you can see it in your analytics or your support inbox. Skip it, for now, when every user sits at a company-managed Windows PC with Chrome or Edge, or when the idea has not yet proved itself on one browser. The extension versus web app page asks the earlier question: whether you need an extension at all.

Custom browser extensions from DataCram start at $1,500 to build, depending on complexity, with a fixed written estimate before work starts. Safari adds packaging, device testing and App Store submission, and those show up as lines in the estimate. Store submission, privacy disclosures and the permission plan are part of the build. Updates after launch are quoted, and extension maintenance covers what each new Safari and macOS release can ask of you.

You own the code, the Xcode project and the App Store listing. Connections to your own systems go live the same day through API integrations. For the build itself, see custom Chrome extension development, what moves the number on the extension pricing page, and every page in the custom browser extensions section. DataCram is a web studio in San Antonio, Texas, building for the web since 1999. See our work or call (210) 346-0848.

Questions owners ask about custom browser extensions

Usually, yes. Apple says Safari web extensions use the JavaScript APIs and file formats of Chrome, Firefox and Edge extensions. Apple's packager, xcrun safari-web-extension-packager, creates an Xcode project from your extension folder and reports any manifest keys Safari does not support. The report tells you how much work remains.

Apple renamed it. Apple's packaging guide gives the current command as xcrun safari-web-extension-packager and says the tool used to be named safari-web-extension-converter. Older guides and forum answers still use the old name.

Not for a first test. Apple says you can upload a ZIP of your extension to App Store Connect to have it converted and packaged for testing, without a Mac or Xcode. For ongoing development, device testing and releases, we work in Xcode on a Mac.

Distributing Safari extensions requires the Apple Developer Program, which Apple prices at 99 USD per membership year, or in local currency where available, as of November 2026. Eligible nonprofits, accredited educational institutions and government entities can request a fee waiver. The fee renews each year.

Apple says Safari web extensions are available in iOS 15 and later, as well as macOS with Safari 14 and later and visionOS 1 and later. Apple's packager can add an iOS target to an existing project with its --rebuild-project option.

We do not quote one. Apple says it reviews all extensions and updates to ensure they work reliably, and we have not researched review times for this page. We make the submission easy to review and promise no approval or date.

Keep reading

Free · No obligation

See what Safari will need from your extension

Send the Chrome extension or describe the idea. Someone at DataCram replies with what Apple's packager is likely to flag, whether iPhone is worth adding, and a fixed written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote