Do not send an entire wiki into a batch queue immediately after installing the extension. Start with one non-sensitive test document. It will reveal install, permission and image problems before they turn into a folder full of partial exports.
The test document does not need to be complex. A few heading levels, a table, several paragraphs and one image are enough.
Confirm that the extension sees the current page
Open the document in the Feishu web app, not the desktop client. Click the Feishu Toolkit icon and check whether the panel can read the page title and body.
If the icon does nothing, reload the extension from the browser’s extension manager. If it still fails, confirm that the extension is installed in the browser you are using and that the tab is not stuck on a login screen.
Once the panel reads the page, the install and page-injection path is working.
Pick the right first document
Do not use a contract, quotation or internal architecture diagram for the first test. Use a personal note with simple text and one image you are allowed to keep.
Before exporting, note three things:
- Whether the document contains a table or code block.
- The order of images in the article.
- Whether your account can open the document normally.
Those details determine what you should inspect after export.
Run the free Markdown export first
Choose Export Markdown without enabling image ZIP, PDF or batch export. Keep the first run as small as possible.
After saving the file, check:
- Heading levels.
- Table rows and columns.
- Code blocks and quotations.
- Image positions relative to the surrounding text.
If the body is missing content, open Cleanup Diagnostics and inspect the removed samples. That is more useful than reinstalling the extension immediately.
Then test image portability
Feishu images may already be local, may still point to the server, or may be unreadable because of permissions. Move the Markdown file and image folder to a new location, disconnect from the network, and open the document.
If images still load, the export is portable. If they disappear, test Markdown with Images ZIP. Image ZIP is a Pro tool with three free trials, so use the result of this test to decide whether you need it.
Add a small batch
After one document works, queue two or three related documents. Check:
- Folder hierarchy.
- One Markdown file per document.
- Images stored with the matching document.
- Clear errors for failed jobs.
Only then move to a larger archive.
Where to look when something fails
| Symptom | Check first |
|---|---|
| The icon does nothing | Feishu web app, extension enabled status |
| A paragraph is missing | Cleanup Diagnostics |
| A table is misaligned | Merged cells in the source |
| Images are broken | Whether URLs still point to Feishu |
| A batch job fails | Whether the document still opens and can be downloaded |
Classify the failure before changing tools. Most first-run issues are limited to one content type, not a broken installation.
When not to use the extension
Scheduled jobs, unattended server uploads and integration with an existing data pipeline belong in an API or command-line workflow. The test document is still useful there, but the browser extension should not become a background scheduler.
The purpose of the first export is not to move everything. It is to prove that permissions, text, images and folder paths work together before you rely on them.