Broken images usually mean the Markdown is still requesting Feishu URLs that depend on a temporary signature, account permission or company network. Download the images locally, switch to relative paths, and test offline after moving the folder before treating the archive as portable.
The Markdown text opens, but every image is a broken icon. The editor is usually fine. The file is still asking Feishu for the images.
A link that works today may expire, require your account or depend on a company network. Find the dependency still attached to the export before choosing a repair method.
Three reasons images stop working
Temporary signed URLs
Some copy and export methods generate image URLs with a temporary signature. The address works for a limited period, then returns an error even though the Markdown file has not moved.
You will usually notice this as a collection that works immediately after export and starts breaking later.
Account-bound permissions
Some image requests require an active Feishu session. Signing out, switching accounts or sending the file to another person can cause the request to be rejected.
The symptom is simple: the image works only on the signed-in account that exported it.
Network restrictions
Company documents may be accessible only through an internal network or allowlisted IP range. The Markdown file is local, but the image is still fetched remotely, so it fails outside that environment.
A 30-second portability test
Copy the Markdown file and image folder to a new location, then:
- Disconnect from the network or use a device that is not signed in to Feishu.
- Open one exported document.
- Check images, tables and code blocks.
- Move the whole folder and open it again.
If the images disappear offline, the export contains references rather than a complete local archive.
Three ways to repair the files
Save images manually
Download each image, place it in an assets folder and edit every Markdown path. Fine for a few images; painful for hundreds.
Download and rewrite with a script
A script can retrieve the images and replace URLs, but it must handle authentication, hotlink protection and filename collisions. Developers can make it work; it is not a dependable everyday workflow.
Save images during export
The simplest long-term fix is to make image localization part of the export. The Markdown then uses relative paths to images in the same folder.
Feishu Toolkit’s Markdown with Images ZIP packages the document and its images together. Markdown export is free; image ZIP is a Pro tool and can be tried before purchase.
Three signs of a portable Markdown archive
- Images exist locally rather than only as remote Feishu URLs.
- References use relative paths and survive a folder move.
- The document opens offline with its images, tables and code blocks intact.
If one of those conditions is missing, importing the file into a note-taking app only hides the problem temporarily.
Files that should not be bundled
Export only content you are authorized to access and retain. A batch download tool does not change the original permission boundary.
Large scans, videos and oversized originals also do not belong inline in a Markdown archive. Keep them in a resource folder and refer to them by a clear filename.
The text was localized; the assets were not. Until both move together, the archive is incomplete.