Those four phrases describe different jobs: exporting one document, migrating a wiki, converting content to Markdown and keeping a long-term backup. Start from the job, then choose manual, batch or API workflows and verify permissions and local assets.
People looking for Lark docs export may actually be trying to download one document, move an entire wiki, convert notes to Markdown or create a long-term backup. The search phrases look similar, but the work is not.
If you use Lark in English and the tutorials you find use Feishu terminology, translate the search phrase into a task before looking for a button.
Lark and Feishu are two names for the same product model
The product uses different brand names in different markets, while docs, wikis, attachments and permissions follow a similar structure. For this article, treat Lark as the English-language product surface.
The larger difference is vocabulary. A Chinese interface may say knowledge base, cloud document and export, while the English interface says Wiki, Docs, Download and Export. Matching the language makes the right menu easier to find.
What the four search phrases really mean
| Search phrase | Actual task | What matters most |
|---|---|---|
| Lark docs export | Download one document | Permission and output format |
| Lark wiki export | Move a knowledge base | Structure, batch scope and assets |
| Lark to Markdown | Convert content for editing | Headings, tables, code and local images |
| Lark backup | Keep a durable copy | Frequency, versions and offline access |
Once these jobs are separated, the steps become clearer. One document is a quick download. A whole wiki is closer to a small migration project.
Choose the format after the task, not before
Common formats include Markdown, Word, PDF and HTML:
- Markdown works well for knowledge bases and long-term editing.
- Word works well for further layout work and delivery.
- PDF works well for a fixed version or printing.
- HTML can preserve a web-like reading experience.
Open the exported file immediately. Whether images are local, links work and tables survive matters more than the download finishing.
Wiki export starts with hierarchy
A wiki is a tree, not one document. Before exporting, list the root, child pages, page count and attachment locations.
A flat folder of Markdown files is technically an export but a poor migration. A better acceptance test is:
- The folder structure matches the source wiki.
- Every page becomes its own file.
- Images move with the matching document.
- A sample page opens offline.
For very large spaces, use a batch queue or API automation. Do not send sensitive content through a custom script before checking what it uploads or logs.
Markdown is not automatically a backup
Markdown is readable, portable and friendly to version control. It may not preserve complex layout, equations, comments or every attachment.
Use Markdown for the editable text layer, but keep protected spreadsheets, presentations and original attachments in their native formats when they matter. Separate the editing copy from the compliance copy.
How English users should verify the result
No matter which search phrase brought you here, finish with three checks:
- The file opens offline.
- Images and attachments travel with the folder.
- You are authorized to retain the content.
If you use a browser extension, confirm that it targets the web app rather than the desktop client. It operates within the permissions already exposed to your account and should not be used to bypass organizational controls.
Search in English, verify with the same rules
Use the English phrase to identify the task, then return to permissions and structure. A single document needs the correct format, a wiki needs hierarchy and assets, and a backup needs a repeatable verification process.
Lark docs export is the entry point. Lark backup is the outcome. Permissions, structure and local resources decide whether the result is usable.