AI 产品解读Batch export Yuque knowledge base content to local files
Solves the difficulty of backing up or migrating Yuque documentation locally. Yuque does not provide a native bulk export feature, making it hard for users to archive their data or migrate to other platforms like Obsidian.
User logs into yuque.com -> Opens extension popup -> Extension detects login via cookies -> User selects knowledge bases/repos -> Extension fetches metadata -> User clicks 'Start Export' -> Extension downloads documents, images, and attachments locally in selected format -> User receives completed local files.
Batch export of knowledge bases, folders, and bookmarksMultiple format support (Markdown, HTML, Word, Excel, PDF)Automatic image and attachment downloading with local path replacementIncremental export to save time on updatesScheduled automatic backupsSupport for team spaces and collaboration libraries
- 目标用户
- Yuque users needing local backups / Users migrating from Yuque to Obsidian/Notion/Feishu / Team administrators archiving team knowledge bases
- The background script is heavily minified/obfuscated (1.3MB), making deep inspection of the exact API call logic difficult without decompilation. However, the localization strings and manifest permissions provide sufficient evidence for the core decisions.
付费分析未识别到付费功能
The extension is free and open-source. There are no paywalls, subscription gates, or premium feature locks within the extension. It includes a 'Sponsor' section asking for voluntary donations ('Buy me a coffee'), but this does not restrict functionality. The extension works fully for any user who has access to the content on yuque.com.
- 置信度
- 95
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 是
- 登录理由
- The extension relies entirely on the user being logged into yuque.com in their browser. It reads yuque.com cookies to authenticate requests to the Yuque API. The popup explicitly checks login status ('Checking login status...', 'Not logged in. Please log in to Yuque first') and provides a link to 'https://www.yuque.com/login' if the user is not authenticated. The extension does not implement its own account system; it acts as a client for the destination service's auth.
