How to Move Highlights and Notes Out of Your Ebook Reader

An ebook reader is a good place to make a highlight. It is not automatically the best place for that highlight to live forever.

The moment annotations become research material, writing material, study notes, or part of a long-term personal archive, the important question changes from Can I see my highlights in the reader? to Can I take them somewhere else in a form I can still use?

Guten Premium's Notes Manager can search and filter highlights and notes across the library, then export either the current filtered set or all annotations. Filtered and full exports are available as Markdown, individual Markdown files in a ZIP, CSV, JSON, or plain text. That provides a direct path out. Other readers may offer their own export tools or, when copying is permitted, let selected passages travel through Android Share to a capture app such as Keep Clip.

The useful workflow begins by deciding what the annotations are becoming.

Do not export everything merely because you can

A highlight can be useful during reading without deserving permanent preservation.

Some marks are temporary orientation:

• a character name
• a sentence you wanted to reread in the next chapter
• an unfamiliar term
• a passage that looked promising but never became relevant

If you export every underline from every book, your external archive may become harder to use than the reader's own highlight list.

Export when the annotation has acquired a second life:

• evidence for an argument
• a quotation you expect to cite
• notes for a paper or research project
• a connection to another book
• material you want searchable across several reading platforms

The boundary should be usefulness, not completionism.

Choose an export format based on the destination

Guten offers several annotation export formats because no single representation is ideal for every next step.

Markdown works well for Obsidian, text-based notes, Git repositories, and archives you expect to edit by hand. Guten can export one Markdown file or individual Markdown files in a ZIP, and Markdown links can use Wikilinks or standard portable link syntax.

CSV works well when you want rows and columns for sorting, filtering, spreadsheet work, or analysis.

JSON preserves structured data for software workflows and migrations where machines, rather than humans, are the immediate reader.

Plain text is the least structured but easiest fallback to open almost anywhere.

If the annotations are entering an existing PKM system, use the format that system already handles cleanly. Do not pick JSON because it sounds more complete if your actual plan is to read and edit the notes in a text editor.

Preserve the source identity along with the quotation

A highlight detached from its book becomes an unattributed sentence surprisingly quickly.

The export should preserve enough information to answer:

• What book did this come from?
• Who wrote it?
• Which chapter or section was it in?
• Which translation or edition supplied these exact words, when that matters?
• What note did you attach to the passage?

This is particularly important for classics and translated works. Homer is not enough to identify the English wording of a quotation.

For formal citation, verify page, location, edition, and bibliographic details in the source you intend to cite. A reader export is a working research record, not necessarily a finished citation format.

Move notes by project when possible

A library-wide export is useful for backup or migration. A project-focused export is often better for actual work.

Guten's Notes Manager can search and filter across annotations. If you are writing about memory in Augustine and Rousseau, filter the Notes Manager down to the passages and notes that belong to that question, then use Export filtered to export that working set directly rather than exporting the entire annotation library.

This keeps the external archive aligned with the task.

The same principle applies when moving material from other readers. A capture inbox such as Keep Clip can be helpful precisely because it lets selected passages from several sources arrive in one place before they are promoted into a project archive.

Keep the original reader long enough to verify the migration

If the export is part of leaving an app or changing devices, test the destination before deleting the source.

Open the exported material and inspect a few awkward cases:

• a highlight containing quotation marks
• a long multiline passage
• a note attached to a highlight
• a book with a long title
• a translated work
• non-ASCII characters if your library contains them

Then search the new archive for something you know should be there.

Migration quality is not established by the existence of a file. It is established by being able to recover the information you expected to move.

Separate backup from portability

A proprietary reader backup may be excellent at restoring annotations to the same reader. That is not the same as having annotations in a form another system can use.

Both are valuable.

Use app-native backup when you want recovery. Use an open or commonly readable export when you want portability.

Guten itself illustrates the distinction: JSON backup and restore can preserve the app's reading state, while Notes Manager exports put annotations into formats intended to leave the reader and be used elsewhere.

A resilient reading archive often has both layers.

Be cautious with quotations from books that are not public domain

Moving your own notes and limited quotations for personal use is different from republishing substantial copyrighted text.

Copyright rules depend on jurisdiction and circumstances, and an export tool does not grant publication rights. If you plan to publish, distribute, or build a public corpus from copyrighted books, check the applicable rights rather than assuming that because your reader let you highlight or export text, you may redistribute it freely.

For Project Gutenberg books in Guten, the underlying texts are supplied through Project Gutenberg, but particular translations or editions outside that catalog can have different copyright status.

The reader should be a place to read, not a hostage situation

A good annotation workflow allows the reader to do what it is good at: display the book, let you mark passages, and keep you oriented while reading.

When the annotations become part of another kind of work, move them into the system designed for that work.

That may be a Markdown vault, a research folder, a spreadsheet, a writing project, or a local archive. The important thing is that the value you created while reading can outlive the interface where you created it.