Deck Help Center

Add extensions to profiles

Add an extension once to your library, then load it into the profiles that need it, from the Web Store, a ZIP or the Marketplace.

Updated · 6 min read

On this page

Extensions live in a library: you add each one once, then assign it to the profiles that should load it. That way a wallet or an ad-blocker gets updated in one place instead of thirty.

Chromium profiles only

Firefox profiles keep their assignments but don't load extensions: "Chromium profiles only. The Firefox engine takes extensions through its own signed-XPI path, which this build does not drive". See Chrome or Firefox.

🧩 Add an extension to your library#

  1. In the left sidebar, click Extensions.
  2. Click + Add extension.
  3. Pick an Add method:
    • Chrome Web Store: paste the extension's store address into Extension URL, or just its 32-letter id. LoginDeck downloads the build the store serves today.
    • Package Upload: drop a .zip or .crx on Drop a ZIP or CRX file here, or click to choose (up to 200 MB). For an unpacked extension, use Choose a folder and pick the folder holding manifest.json. Then give it an Extension name, and optionally an Extension icon and Description.
  4. Choose an Extension group, or make one with + New group….
  5. Click Confirm. You'll see "Added MetaMask 12.9.3".
Adding an extension from its Chrome Web Store URL, then assigning it to profiles.

You can also drag a .zip or .crx anywhere onto the Added extensions list to open the dialog with the file already picked.

The Marketplace#

The Marketplace tab is a curated list of Web Store extensions, sorted into Popular, Common, Marketing, Translation, Social Media, Security, Automation, Developer, Wallets and Others. Click Add on a card and it's downloaded from the store into a group named after the category. Cards you already have show Added.

If what you want isn't listed: "Nothing in the catalogue matches "x". Paste its Web Store URL into Add extension instead."

What's accepted#

WorksDoesn't work
Chrome Web Store URL or 32-letter idFirefox .xpi files
.zip and .crx packagesEdge Add-ons store links
An unpacked folder with manifest.jsonExtensions above manifest version 3 or below 2

🎯 Give profiles an extension#

Three ways, whichever suits:

  • From the library: on the extension's row, click ⋯ → Assign to profiles…, tick the profiles, then Apply.
  • From a profile: row ⋯ → Extensions…, tick the extensions, then Apply.
  • In the editor: open the profile's Extensions tab and click a pill to switch an extension on or off.

To do many profiles at once, tick the rows and click Extensions in the bar at the bottom. Rows read on all or on 3 of 12, and only the boxes you actually change are applied.

A profile can load up to 32 extensions.

Assigning takes over the profile's extensions

Once a library extension is assigned, that assignment becomes the profile's complete extension set — anything installed from inside the browser is switched off while it's assigned. Decide which way you want to manage a profile and stick to it.

🔁 Auto-sync, groups and turning one off#

  • Auto-sync: row ⋯ → Auto-sync to every profile loads an extension into every Chromium profile without assigning it. The Used by column then reads All profiles. Turning it on switches off in-browser-installed extensions on every Chromium profile, so use it only for something you genuinely want everywhere.
  • Enabled toggle: turning an extension off keeps the assignments but stops it loading ("… disabled — assigned profiles launch without it").
  • Groups: Group settings creates, renames and deletes groups. Deleting a group keeps its extensions and moves them to Ungrouped. Groups only sort and filter the library.
  • Remove from library: tells you how many profiles load it. They keep the assignment and launch without it on this computer until it's added again.

👀 What pages can notice#

The What pages can notice column tells you how visible each extension is to the sites you visit:

  • "3 content scripts run in pages"
  • "2 web-accessible resource rules — probeable under its id"
  • "nothing in pages — background only"
  • "carries its Web Store key, so its id is the store id"

An extension that runs content scripts is something a site can look for. That's fine for a wallet you'd expect a real person to have, and a problem for anything unusual.

✍️ Paste as human#

Every Chromium profile gets a Paste as human item in the right-click menu of text fields. It types the clipboard in at that profile's own typing rhythm instead of pasting it in one lump, which is what a paste into a password or a long message looks like to a site.

  1. Copy the text.
  2. Right-click the field in the profile's browser.
  3. Click Paste as human.

It handles up to 20,000 characters. There's nothing to install and nothing to switch on: it's not in your library, it can't be seen by pages, and Firefox profiles don't have it.

❓ Common questions#

Do crypto wallet extensions work?

Yes. Add the wallet from the Web Store or as a package, assign it to the profile, and set it up inside that profile's browser. Each profile has its own storage, so each one has its own wallet.

I installed an extension inside a profile's browser and it disappeared.

That happens when a library extension is assigned to the profile, or when auto-sync is on for any extension: the library becomes the profile's whole extension set. Add the extension to the library instead, then assign it.

How do I update an extension?

Add it again from its Web Store URL. A new version is a new library entry, so reassign your profiles to it and remove the old one. The Marketplace shows Added as long as any version is there.

Do my extensions appear on my other computers?

The assignment travels with the profile, but the extension files stay on the computer that added them. On another computer the pill reads "… not on this computer" until you add it there too.

Why won't my extension add?

The dialog says why. Common ones: "no manifest.json — this is not an unpacked Chrome extension", "manifest.json is not valid JSON", "manifest_version 1 — only Chrome extensions (v2 or v3) can be loaded", "that is not a Chrome Web Store URL or id", "the Chrome Web Store has no extension under abc… — check the URL, or the listing may have been removed", "that extension is over 200 MB", "not a zip or .crx file".

I edited the folder I imported an unpacked extension from, and nothing changed.

The folder is copied into the library when you add it. Add it again to pick up your edits.

ℹ️ Good to know#

  • Assigned extensions are loaded unpacked from the library on every launch.
  • The same build added twice is one entry. A different version is a separate entry.
  • Extensions that click, like or follow for you aren't in the Marketplace by policy. For that kind of work, use Flows.