35 / Extract · Kobo/Kindle → MD / CSV

annotation sync

One library, every annotation.

Highlights tend to end up in two places: a Kobo database on the e-reader and a My Clippings.txt file from a Kindle. This tool reads both, matches annotations to books and chapters, and merges the two libraries into one list. A highlight that appears in both is kept once and marked as merged, with both sources shown. You can search it, narrow it by book, type or date, correct a passage or a note inline, and delete an annotation you no longer want. Four exports cover the usual destinations: one Markdown file per book for Obsidian, a Readwise-compatible CSV, a Notion-flavoured CSV and a plain CSV. Everything is read and written in this browser; the Kobo database is never written back to and nothing is uploaded.

All tools
Opening your workspace…

From file to finished

How to use this tool

  1. Choose KoboReader.sqlite, My Clippings.txt, or both. A Kobo database loads the SQLite reader only when you select it.

  2. Review the merged library, search or filter it, and edit or delete individual annotations. Duplicates keep both source labels.

  3. Pick an export: Obsidian Markdown, Readwise CSV, Notion CSV or plain CSV. Use the ZIP button for one file per book.

Kobo database, read directly

The KoboReader.sqlite content and Bookmark tables are parsed in the browser with sql.js. Each bookmark is matched to its book and chapter, with title, author, chapter, position, date, text and note. The database is opened read-only and never modified.

Kindle clippings, merged in

My Clippings.txt goes through the same parser as the Kindle clippings tool, including its duplicate removal. Kobo and Kindle annotations are then merged by book title and text, so a passage highlighted on both devices appears once and is marked as merged with both sources.

The whole library is editable

Search title, author, chapter, text and note; filter by book, type and date range; edit a passage or note inline; delete an annotation and restore it later. Counts and the export scope follow the filtered set, and every export uses your edits.

Four exports, one ZIP

Obsidian Markdown writes one file per book with YAML frontmatter and blockquoted annotations. Readwise CSV starts with the exact seven Readwise columns; Notion CSV and plain CSV use their own headers. When there is more than one book, the ZIP button downloads one file per book in any format.

A little more detail

Frequently asked questions

Where do I find KoboReader.sqlite?

Connect the Kobo over USB. On most models the database is in .kobo/KoboReader.sqlite (on some older models it is .kobo/Kobo/KoboReader.sqlite). Copy it to this device, then choose it here.

Where is My Clippings.txt?

Connect the Kindle over USB and open the documents folder. My Clippings.txt sits there; copy it to this device and choose it as the second import.

Does it write to my Kobo database?

No. The file is opened in the browser with a read-only SQLite reader and is never modified. Your original KoboReader.sqlite stays as it was.

What counts as a duplicate?

An annotation with the same book title and the same text. The first copy is kept, both source labels are shown, and the row is marked Merged. A highlight with no text falls back to type, position and date for matching.

Which export should I use?

Obsidian Markdown gives one note per book with frontmatter and > blockquotes. Readwise CSV has the exact Highlight, Title, Author, URL, Note, Location, Date columns Readwise imports. Notion CSV and plain CSV are general-purpose spreadsheets with the same annotation data.

Does it upload my highlights?

No. Nothing is sent to a server and no account is needed. The Kobo database and Kindle file stay in this browser tab. The SQLite reader is loaded only after you choose a Kobo database, so the page does not download it just to browse.

Are my edits permanent?

They apply to the library in this session and to every export you make from it. They are not written back to KoboReader.sqlite or My Clippings.txt. Reloading the page or starting over clears them; use Restore all to undo edits and deletions without reloading.