Kindle + KOReader OPDS eBook Transfer Setup
我在 Kindle 上主要用 KOReader 看书。
传书这件事以前一直不够顺手。常见方法是邮件推送、局域网传输,或者接数据线手动拷贝。它们都能用,但每次都要多走几步。
后来我把 OneDrive 目录接到了 OPDS。
KOReader 可以直接按书库方式浏览和下载,体验明显更好。
背景:为什么想做 OPDS
KOReader 自带 OPDS 客户端。
这意味着只要有一个 OPDS 服务端,Kindle 就能像访问在线书店一样管理自己的电子书。
我原来在用这个项目做 OneDrive 目录索引。它是一个基于 Cloudflare Workers 的轻量网盘目录服务:
lyc8503/onedrive-cf-index-ng
这个项目本身很适合做轻量目录服务。
它跑在 Cloudflare Workers 上,部署成本很低,访问也稳定。
问题是它之前并不支持 OPDS 输出。
方案:给 onedrive-cf-index-ng 增加 OPDS
我把 OPDS 支持补了上去,并提交了这两个 PR:
- https://github.com/lyc8503/onedrive-cf-index-ng/pull/77(先补齐 OPDS 相关能力)
- https://github.com/lyc8503/onedrive-cf-index-ng/pull/80(再完善后续细节)
改完以后,同一个 OneDrive 目录可以同时服务网页浏览和 KOReader 的 OPDS 取书。
这就把“网盘目录”变成了“可订阅书库”。
使用体验
实际使用时,流程会简单很多:
- 书放进 OneDrive 指定目录
- Workers 站点自动索引
- KOReader 里添加 OPDS 源
- 在 Kindle 上直接检索、下载、打开
和邮件推送相比,它更像一个持续在线的私人书库。
和局域网或有线拷贝相比,它不依赖同一网络,也不需要每次连线。
KOReader 侧配置要点
在 KOReader 里进入 OPDS 目录,新增一个目录源。
把你的 Workers 地址填进去即可。
如果你启用了 OPDS 路径,就填对应的 OPDS URL。
建议把书按作者或系列整理到不同目录。
这样在 KOReader 里浏览会更清晰,检索也更快。
小结
这套方案的核心价值不在“能不能传书”,而在“传书是否足够顺手”。
当 OneDrive + Workers + OPDS 接起来后,Kindle 上的取书动作会变成日常化操作。
对长期阅读来说,这个体验差异很明显。
I primarily use KOReader on my Kindle for reading.
Transferring books was never quite smooth before. Common methods include email push, LAN transfer, or manually copying via a USB cable. They all work, but each adds extra steps.
Later, I connected my OneDrive directory to OPDS.
KOReader can directly browse and download books as a library, which significantly improves the experience.
Background: Why OPDS?
KOReader comes with a built-in OPDS client.
This means as long as there’s an OPDS server, Kindle can manage its own ebooks like accessing an online bookstore.
I was previously using this project for OneDrive directory indexing. It’s a lightweight cloud drive directory service based on Cloudflare Workers:
lyc8503/onedrive-cf-index-ng
This project itself is well-suited for lightweight directory services.
It runs on Cloudflare Workers, has low deployment costs, and offers stable access.
The issue was that it previously didn’t support OPDS output.
Solution: Adding OPDS Support to onedrive-cf-index-ng
I added OPDS support and submitted these two PRs:
- https://github.com/lyc8503/onedrive-cf-index-ng/pull/77 (First, complete OPDS-related capabilities)
- https://github.com/lyc8503/onedrive-cf-index-ng/pull/80 (Then, refine the subsequent details)
After the changes, the same OneDrive directory can now serve both web browsing and KOReader OPDS book fetching.
This turns the “cloud drive directory” into a “subscribable ebook library.”
User Experience
In practice, the workflow is much simpler:
- Put books into a designated OneDrive directory
- The Workers site automatically indexes them
- Add the OPDS source within KOReader
- Search, download, and open books directly on the Kindle
Compared to email pushing, it’s more like a continuously available personal library.
Compared to LAN or wired transfers, it doesn’t rely on the same network and doesn’t require connecting a cable each time.
Key Notes for KOReader Configuration
In KOReader, go to the OPDS catalog and add a new catalog source.
Simply enter your Workers address.
If you have enabled the OPDS path, enter the corresponding OPDS URL.
It’s recommended to organize books into different directories by author or series.
This makes browsing cleaner and searching faster within KOReader.
Summary
The core value of this setup isn’t about “whether it can transfer books,” but about “whether the transfer is smooth enough.”
Once OneDrive + Workers + OPDS are connected, fetching books on Kindle becomes a routine, everyday operation.
For long-term reading, the difference in experience is quite noticeable.