Cross-Browser Support

The Visual Editor ships as a browser extension. We publish to the Chrome, Firefox, and Edge stores. Other Chromium-based browsers can side-load the Chrome build.

Supported browsers

Each supported browser has its own published listing. Open the appropriate link below and click Add to browser.

Google Chrome — chromewebstore.google.com/detail/avsb-dev-tools
Mozilla Firefox — addons.mozilla.org/firefox/addon/avsb-dev-tools/
Microsoft Edge — microsoftedge.microsoft.com/addons/detail/avsb-dev-tools

Each store listing displays the A vs B logo, publisher name "A vs B Inc.", the current version number, and an Add to browser (or Geton Edge) button. After install, the A vs B icon appears in your browser's toolbar — pin it for one-click access.

Side-loading on other browsers

If you use Brave, Arc, Vivaldi, Opera, or another Chromium-based browser, you can side-load the Chrome build directly. This is also the path to take for installing pre-release builds that haven't shipped to the store yet.

Download the unpacked extension

From your A vs B dashboard, go to Settings → Visual Editor and click Download Chrome build (.zip). Unzip the archive into a folder you won't accidentally delete.

Open your browser's extensions page

In Chromium-based browsers, navigate to chrome://extensions (or the equivalent address — brave://extensions, edge://extensions, etc.).

Enable developer mode

Toggle Developer mode on in the top-right corner of the extensions page. New buttons will appear above the extension list.

Load the unpacked extension

Click Load unpacked and select the folder you unzipped earlier. The extension installs immediately and the A vs B icon appears in your toolbar.

Pin and sign in

Pin the extension to your toolbar, click the icon, and sign in with your A vs B credentials. You're now ready to edit.

Store builds update automatically. Side-loaded builds do not — you will need to download a new zip and re-run Load unpacked whenever a new version ships. For long-term use we strongly recommend the store build wherever it's available.

Firefox developer mode

Firefox uses a different format. For unpublished or development builds, open about:debugging#/runtime/this-firefox, click Load Temporary Add-on, and select the manifest.json file from the unzipped folder. The extension remains active until you close Firefox.

Unsupported browsers

Safari does not currently have a published build of the Visual Editor extension. You can still preview variations on Safari via preview links — only the authoring experience requires Chrome, Firefox, or Edge.

The runtime that applies your variations is part of the A vs B snippet, which works in every modern browser including Safari and all mobile browsers. The browser-extension restriction only affects authoring, not your visitors.