Skip to the products
LCPanelLicence Center Panel

Browser Extension

A Chrome, Edge, Firefox and Opera extension built for your site: search files, copy links and download from the toolbar, signed in with the API keys. Premium.

Plugins Updated 6 Nov 2026 36 / 50

The Browser Extension plugin builds a toolbar extension for your site - for Chrome and Edge (Manifest V3) and for Firefox and Opera (Manifest V2) - and serves a page where members download it. From the toolbar a member searches their files, opens any folder, copies a file's link with one click, downloads, and jumps to My Files or the upgrade page. The extension is built on your server with your site's address and name inside, so there is nothing to code and nothing to publish unless you want a store listing.

It is for sites whose members share links all day - support teams, communities, anybody who pastes file links into chats and forums.

Switching it on

Browser Extension is a premium plugin: it needs the browser-extension addon on your licence. Buy it at lcpanel.com, press Check again now on Admin → Configuration → License, then switch Browser Extension on at Admin → Extensions → Plugins (Manage Plugins). The packages are built the moment it is switched on. Its page appears under Extensions as Browser Extension (/admin/plugin/browser-extension).

The extension talks to the site through the REST API (API and MCP): it signs in at api/v2/authorize with the member's API keys and lists files with folder/listing and file/search. So the member's package must have API Access on (Account packages), and Site Settings → API → Authentication method should be API Keys.

The admin page

Packages shows what the current build was made for (the site address and the time) and the two zips to download yourself - Chrome / Edge zip and Firefox / Opera zip - plus Rebuild now. Members fetch the same zips from the public page at /browser-extension. The files live in uploads/browserext/boxpuff-chrome.zip and boxpuff-firefox.zip, which must be readable from the web.

The settings:

SettingWhat it does
Show the front-end pagePuts Browser Extension in the public Features menu and Browser extension at the bottom of the file manager's left rail.
Extension nameThe name shown in the browser (empty = the site name).
Files per search pageResults per page in the popup (default 20).

Save & rebuild saves and builds both zips again. The build is also redone by itself when the site address changes - the public page checks that the packages were built for the address the site answers on, and rebuilds them if not.

What the member sees

/browser-extension (also linked from the Features menu) is the page Browser Extension: a short description, a Download extensions table with a Download (zip) button for Chrome/Edge and one for Firefox/Opera, a What it does list - Search your files and open any folder, Copy a file link with one click, Download files straight from the toolbar, Quick links to My files and the upgrade page - and the sentence that matters: Sign in inside the extension with your username and API key 1 from Account → Settings → API Access.

Clicking a browser name opens its guide, /browser-extension/<browser>-install:

BrowserThe steps the page gives
ChromeDownload the Chrome/Edge zip and unpack it; open chrome://extensions, switch on Developer mode; Load unpacked and choose the folder; pin it from the puzzle icon, open it and sign in with the username and API key 1.
EdgeThe same with edge://extensions (Developer mode on the left).
FirefoxDownload the Firefox/Opera zip, do not unpack it; open about:debugging#/runtime/this-firefox; Load Temporary Add-on… and pick the zip. For a permanent install the site owner signs the zip at addons.mozilla.org.
OperaUnpack the Firefox/Opera zip; opera://extensions, Developer mode, Load unpacked.

Inside the popup the member types their username, API key 1 and API key 2 (both from Account → Settings → API Access, see The file manager) and is signed in; the token is kept in the extension's storage and refreshed by every call. The popup then shows the root folder, a search box, and for each file a copy-link and a download button. The extension asks the browser for the storage, clipboardWrite and downloads permissions and for access to your site's address only.

Connecting it (1.1.0)

The popup of a browser extension closes the moment you click outside it, so typing the user id and the two keys by hand used to lose what was already pasted. Since 1.1.0:

  • Connect the extension to your account - a button on the member page /browser-extension (and the install pages). With the extension installed, one press copies the user id and both keys into it and signs it in; nothing to type. The site address is built into the extension, so it only reacts on this site.
  • Settings in a tab - the popup has an Open settings in a tab link (the browser's options page). That page stays open while you copy keys elsewhere, and it shares its values with the popup.
  • A draft that survives - every box of the popup saves what you typed or pasted as you go; when the popup closes and opens again, it is still there.
  • Paste both - paste userid:key1:key2 (or userid key1 key2) into any box and all three fill; the Paste both button reads the clipboard for you.

Members on 1.0.0 reinstall or reload the extension once to get this; the member page rebuilds the zip by itself when the version changed.

Store listings

The zips are unsigned developer builds, which is why the guides go through Developer mode. For a one-click install, publish the Chrome/Edge zip under your own developer account in the Chrome Web Store and Edge Add-ons, and sign the Firefox zip at addons.mozilla.org (its manifest already carries a Gecko id of the form boxpuff@your-host). The build does not change; only the place members get it from.

Tips

  • Rebuild after you change the site name or logo: the extension name and icons are baked into the zip.
  • A member who regenerates their API keys (Account → Settings → API Access → the regenerate button) must sign in to the extension again.
  • The rate limit of Site Settings → API → Rate limit per minute applies to the extension like any API client; the default 120 is plenty for a popup.
  • If the popup says the account may not use the API, the member's package has API Access off, or Site Settings → API → Access level leaves their package out.
Was this helpful?
Share this chapter