Run Chrome extensions in Safari.

Viaduct converts any Chrome extension into a native Safari Web Extension. You never have to open Xcode or a terminal.

Drop in whatever
you already have.

Viaduct reads any of these and hands back a signed Safari extension. You don't repackage anything yourself.

.crx
Packed Chrome build
.zip
Any zipped extension
Unpacked folder
Straight from source
Manifest V2 & V3
Both handled

“Add to Chrome” becomes “Add to Safari.”

Browse the Chrome Web Store in Safari and the green install button points at Safari instead. Click it once and Viaduct does the rest.

Drop. Convert. Done.

Packaging for Safari normally means wrestling Xcode and Apple's command-line signer. Here it runs behind one button.

1

Drop it in

Viaduct reads the manifest and shows the extension's own name and icon before anything runs.

2

Converted & signed

Viaduct rebuilds it as a native Safari Web Extension and drives the signing for you. You watch it happen live.

3

Live in Safari

Installed and ready, running in Safari's own engine. No second Chromium process eating your battery.

Converting isn't the hard part. Working is.

Safari implements dozens of chrome.* APIs differently, or not at all, so a converted extension installs fine and then quietly stops working. Viaduct ships a runtime layer that patches the gaps.

60+

chrome.* namespaces the runtime layer normalizes, so your extension keeps working after the move.

Dark Reader

BreaksPopup buttons go dead. Background ports route by an extension id that Safari reports differently.

FixedViaduct rewrites the id so the popup reaches the background.

Grammarly

BreaksIts own bundled resources fail to load. Safari's resource server is case sensitive.

FixedViaduct normalizes the casing.

Service workers

BreaksSafari omits onInstalled and parts of self.registration, so the worker throws at load.

FixedViaduct backfills what's missing.

Frozen namespaces

BreaksSafari exposes chrome.* as immutable native objects, so extensions that patch them crash at startup.

FixedViaduct makes them writable again.

Native conversion, done properly.

The extension runs inside Safari's own engine, with no second browser process riding along behind it.

01

Keeps Safari's battery life

Converted extensions run inside Safari's native engine, not a second Chromium process running in the background. Faster, and far easier on your battery.

2

engines running if you keep Chrome around for one extension

1

with Viaduct. The extension lives inside Safari

02

Auto-resign signing

Free Apple signatures lapse every 7 days. Pro silently re-signs before they do, so your extensions never vanish.

Without Signed 7 days Gone
Pro Signed Re-signed, day 6
03

Self-updating engine

The converter keeps itself up to date. New fixes arrive without you reinstalling anything.

04

Auto-updating extensions

Installed an extension from the Chrome Web Store? When it ships a new version, Pro rebuilds and reinstalls it for you.

05

MV2 & MV3 aware

Detects the manifest version and reports incompatibilities before converting.

06

Every option exposed

Output directory, bundle id, app name, macOS or iOS or both, signing choices, plus Analyze and Doctor checks. Developer mode hides nothing.

Start free. Go Pro when it sticks.

Free

$0
  • Convert up to 2 extensions
  • “Add to Safari” Web Store button
Download

Viaduct Pro

$19 onetime
  • Unlimited conversions
  • “Add to Safari” Web Store button
  • Auto resigning
  • Auto updating
Get Viaduct Pro

Requires Xcode for conversion.

Questions

Will my Chrome extension actually work?

Most do. Before converting, Viaduct checks the extension and reports anything that won't work, so there are no silent surprises. A few things (like some OAuth sign-in flows) can't survive conversion, and it tells you honestly when that's the case.

Do I need to know how to code?

No. Drop an extension in, get it in Safari. The only thing to install is Xcode (free). Apple requires it for signing, and Viaduct drives it for you.

Does it run on an Intel Mac?

Yes. Viaduct is a universal app, so the same download runs natively on Intel and Apple Silicon. There's one build, not two, and Rosetta never comes into it. You need macOS 13 or later either way.

Why does it keep my battery better than Chrome?

The converted extension runs inside Safari's own engine instead of a separate Chromium process humming in the background. One less browser engine running means less CPU and longer battery life.

What's the difference between Free and Pro?

Free gives you 2 conversions, and they lapse after about a week. Pro is unlimited and keeps your extensions signed so they never disappear. One-time $19, yours forever.

Why isn't this on the Mac App Store?

The build tools Viaduct drives aren't allowed inside the App Store sandbox, so it ships as a notarized direct download instead. Same Apple notarization, just outside the store.

Your extensions.
Safari's battery life.

Keep the extensions you rely on without keeping Chrome open for them.