TronBrowser Home Browse Install guide Publish

Installing store extensions

TronBrowser gives you a real one-click install. Other browsers actively block third-party extension installs, so they need a sideload step — here's the honest path for each.

TronBrowser
Chrome
Edge
Firefox

TronBrowser — one click

Because TronBrowser is our own Chromium build, store extensions install and auto-update directly — no developer mode, no warnings.

  1. Open the extension's page in the store and press Install.
  2. Confirm the permission prompt. Done — it auto-updates via the store's update_url.

Chrome — sideload (developer mode)

Chrome disables extensions installed from outside the Web Store on Windows/macOS. Use developer mode (works everywhere) or enterprise policy / Linux for the auto-updating .crx.

Unpacked (.zip) — any OS

  1. Download the .zip from the listing and unzip it.
  2. Go to chrome://extensions and toggle Developer mode (top-right).
  3. Click Load unpacked and select the unzipped folder.

Auto-updating .crx — Linux / enterprise

On Linux, or via the ExtensionInstallForcelist / ExtensionSettings enterprise policy, point Chrome at the listing's .crx and its update_url (shown on each listing) for silent auto-updates.

Edge — sideload (developer mode)

Edge is Chromium too, so it mirrors Chrome.

  1. Download and unzip the bundle.
  2. Open edge://extensions and enable Developer mode.
  3. Click Load unpacked and choose the folder.

Firefox

Release Firefox only runs add-ons signed by Mozilla. Two paths:

Temporary (any build) — until restart

  1. Open about:debugging#/runtime/this-firefox.
  2. Load Temporary Add-on… and pick the manifest.json from the unzipped bundle.

Permanent — needs Mozilla "unlisted" signing

For a permanent install in release Firefox the .xpi must be signed by Mozilla's AMO (the "unlisted" path — no public listing/review). Developer Edition / Nightly / ESR-unbranded can disable signing and install the .xpi directly via about:addons → Install Add-on From File.

Publishing via a PR (alternative to the upload form)

The store DB is the source of truth, but every published listing is also mirrored to a public git registry. If you prefer git, open a PR adding registry/<your-slug>/listing.json (name, MV3 manifest, bundle/CRX URLs). The vu1nz.com scan runs as the PR's CI check; once the $1 fee clears, it merges and goes live.