Keep Your Libby Notes After Returning a Book: A Book Club Export Guide

Spoiler boundary: Reading-tool guidance only; no book plots or quoted passages.

You can export notes, highlights and bookmarks made in Libby through a title’s Reading Journey, including after returning the title. Libby’s official help explains the route and export choices. For a book club, turn that file into a short discussion sheet organized by chapter and question. Keep the annotation record separate from the borrowed book itself and from notes made in another reading app.

Libby’s official route to your annotation export

Start from the title’s Reading Journey, then choose Actions and Export Reading Data. For a current loan, Libby directs readers through Shelf, Manage Loan and Reading Journey. For a previously borrowed title, its help points to the cover in the library catalog and then Reading Journey.

The official export instructions describe two useful choices: Table creates a web-page view, while Spreadsheet saves data to your device. Within the spreadsheet route, exporting Highlights includes notes; Bookmarks is another option. Follow the current interface rather than a screenshot of an older app version.

That is enough to retrieve the record. It is not a reason to send the entire export to your group. Open it privately first and decide which entries actually help the conversation.

Returned book does not mean lost discussion preparation

Libby says its annotation export is available even after return. Its ebook annotation help also says saved bookmarks, notes and highlights reappear when you borrow the book again. These statements concern Libby’s records; do not assume the same process handles every outside device or reading app.

The Reading Journey help explains that this view brings together information about your interaction with a title. If an expected note is missing, first check where you made it. A loan started through Libby does not establish that every annotation was made inside Libby.

A useful first check is simple: write down the title, the reading app and the edition before looking for an export. This is our editorial troubleshooting habit, not a promise that different platforms will merge their data.

Turn the export into a three-column book club sheet

Keep one location, one observation and one question per discussion point. The raw file is a memory aid; your club sheet should be an invitation to talk. Try this original structure:

Location	Your observation	Question for the group
Chapter within the agreed reading boundary	A character seems to avoid making a choice	What limits the options available here?
A later allowed chapter	The viewpoint changes how a place feels	Which details changed your impression?
Another allowed checkpoint	A repeated image drew your attention	Does the repetition suggest a pattern, or are we reading into it?

These are invented teaching examples, not observations from a real book or survey. Replace them with your own notes and precise locations. A question works better when other readers can disagree without needing information beyond the meeting’s checkpoint.

Before sharing, remove private comments, later-book predictions and passages that reveal events the group has not reached. Paraphrase the moment in your own words where possible. You do not need to reproduce a page of text to explain why a decision interested you.

Separate memory, evidence and interpretation

A saved highlight helps you find evidence; your note may still be an interpretation. Use three labels in your private preparation: what the scene states, what you infer, and what you want to ask. This keeps a confident personal reaction from becoming an unsupported claim about the story.

For example, “this choice felt protective to me” invites discussion. “The author confirms a secret motive” needs an actual author source. If your notes were written weeks ago, revisit the available context before treating an emotional first reaction as the only possible reading.

For mixed-format groups, use chapter boundaries or another jointly verified story checkpoint. A page reference can be useful to you without being a universal location for an audiobook listener or a reader with a different edition.

Keep a useful record without making it another unread pile

Our suggestion is to choose a handful of discussion points rather than carry every highlight into the meeting. Name the saved file with the title and the covered chapters. Add one line stating whether your notes cover the whole book or only the current meeting section.

After the meeting, keep the questions that produced worthwhile disagreement and delete routine preparation copies if you no longer need them. This is an optional personal workflow, not a claim that annotation volume measures reading quality. Finishing with two good questions can be more useful than maintaining an impressive-looking spreadsheet.

FAQs: Libby notes and book club preparation

Can I export highlights after returning a book?

Yes. Libby’s official instructions explicitly allow export after return through the title’s Reading Journey.

Does the highlights export include my notes?

Libby says its Highlights spreadsheet export includes notes. Check the resulting file before sharing selected discussion points.

Is the export a permanent copy of the ebook?

No. Annotation export and access to a borrowed ebook are different things. This guide covers reading records, not keeping a library loan beyond its terms.

Should I share all my highlights with the group?

Our recommendation is to share your own short observations and questions within the agreed spoiler boundary. Review the file privately first.

What if I read in another app?

Check that app’s own annotation tools. This guide describes the route documented for Libby and does not promise a cross-platform export or automatic sync.

Sources and editorial scope

Libby’s export, annotation and Reading Journey help pages linked above were checked October 11, 2026. The discussion-sheet structure and preparation advice are original editorial recommendations. Reader questions also appear in this public annotation discussion; it is reader context, not authority for the app’s behavior.