Setup

How to Install Feishu Toolkit: Chrome, Edge and Offline Packages

Install Feishu Toolkit from the Chrome Web Store or Edge Add-ons, or manually in Chrome or Edge, update it safely, and troubleshoot loading errors, missing manifest files and unresponsive icons.

6 分钟6 min read 发布于 Oct 6, 2026Published Oct 6, 2026 更新于 Oct 19, 2026Updated Oct 19, 2026
本页结构 On This Page
直接回答Short Answer

Use the Chrome Web Store or Edge Add-ons for installation and automatic updates. If a store is unavailable, open the extension manager in Chrome or Edge, enable Developer mode, and load the extracted folder that contains manifest.json. Most failures come from choosing the wrong folder, a disabled extension, or trying to use the desktop client instead of the Feishu web app.

On company computers, the store may be unavailable even when the extension package has already been downloaded. Chrome, Edge and other Chromium browsers can still load a folder that is already on the machine.

Feishu Toolkit is available in the Chrome Web Store and Edge Add-ons. Use a store for automatic updates, or follow the manual steps below when a store is unavailable.

  1. Open the Chrome Web Store or Edge Add-ons.
  2. Select Add to Chrome or Get, then confirm the installation.
  3. Pin Feishu Toolkit to the toolbar and open an ordinary web page to use it.

If a store is unavailable, download the official offline package from the installation page.

Confirm that you have a complete unpacked build

Download the archive and extract it before installation. Do not try to load files from inside the compressed archive.

The extracted folder should contain:

  • manifest.json
  • The extension scripts and interface files
  • A stable folder such as feishu-toolkit-v1.8.7

Keep the folder somewhere that is not automatically cleaned. If it is stored in a temporary Downloads directory, deleting that directory will remove the installed extension with it.

Install in Chrome

  1. Open chrome://extensions/.
  2. Turn on Developer mode.
  3. Select Load unpacked.
  4. Choose the folder that directly contains manifest.json.
  5. Pin Feishu Toolkit to the toolbar.

When installation succeeds, Feishu Toolkit appears in the extension list. If the toolbar contains several unnamed extensions, pin the correct one from the extension manager.

Install in Edge

Open edge://extensions/ and follow the same steps. Edge displays its own developer-mode warning. That warning is normal for locally loaded builds.

Before signing in to Feishu, open an ordinary web page and try Copy Page as Markdown. If that works, the extension is loaded correctly.

Common errors

The browser cannot find manifest.json

You selected the parent folder. Open Load unpacked again and choose the directory that contains manifest.json directly.

Nothing happens after clicking the icon

First confirm that you are using the Feishu web app in a browser tab. A browser extension cannot read or control the Feishu desktop client.

If ordinary web pages also fail, open the extension manager, check that the extension is enabled, and click Reload.

The extension appears damaged or incompatible

Remove the old version, extract the full new archive, and load the new directory. Do not copy a new release over files from an older one.

Why does the browser warn me about developer mode

That is the standard warning for any locally loaded extension. Store-installed extensions do not show it. Switch to a store installation if you prefer to avoid this warning.

Updating a manual installation

Manual builds do not update themselves. To upgrade:

  1. Download and extract the new build into a new folder.
  2. Remove the old extension from the browser.
  3. Load the new folder.
  4. Confirm that the version shown in the extension matches the download.

Files that were already exported are independent of the extension version and do not need to be regenerated.

Run one small test before real documents

Export a non-sensitive test document, move the Markdown and image folder to a new location, and open it offline. Headings, tables, code and images all need to survive that move.

Only then should the extension be used on real files.

When manual installation is not appropriate

If company policy disables developer mode or permits only store-installed extensions, do not change device policy to bypass it. Use the store build or ask the administrator to evaluate the extension.

The installation method does not change where documents are processed. Conversion and packaging still happen locally in the browser.