How do Reader highlights reach Obsidian?
Readwise documents Reader as connected to its Highlights library. Highlights can then export to Obsidian through the Readwise Official plugin. Think of this as a pipeline with separate stages: the Reader document and annotation, the Highlights record, and the Markdown note in the intended vault.
Start by deciding what belongs in the destination. A reading archive, selected research highlights, and your own product decisions are different collections. For an illustrative founder research workflow, export only the material needed to support a decision, preserve the source context, and write the resulting analysis in a clearly identified section or separate note.
Choose plugin export or a deliberate manual handoff
The official Obsidian integration supports exporting new highlights into the vault and configuring the export's format. Reader also documents manual export options for a document's notes and highlights, including copying text or downloading Markdown. Choose the method that fits the job: ongoing capture or a bounded handoff you intentionally review.
Use a harmless document titled Research trial. Add one highlight, an explanatory note, and a topic tag. Export it using the chosen path and inspect the resulting title, source URL, annotation, and file location. This is an original proposed trial; it does not report that we connected a real reading library or changed an Obsidian vault.
| Question | Plugin workflow | Manual workflow |
|---|---|---|
| Where did the annotation originate? | Trace Reader, Highlights, and the vault note | Keep the source context in the exported document |
| What happens after another highlight? | Inspect the next export's append behavior | Decide when to make another export |
| What happens after editing old material? | Check the documented update boundary | Compare the newly exported version deliberately |
| Where does your analysis live? | Keep its meaning distinct from imported text | Keep its meaning distinct from imported text |
New highlights and edited highlights behave differently
Readwise describes its Obsidian integration as append-only: new highlights can be added to an existing note. It also states that later edits to already-exported highlights do not automatically propagate as a two-way update. Do not assume a successful later export means every old sentence in the vault now matches the source library.
In the fictional trial, add a second highlight and observe where it appears. Then edit the original annotation in the source and inspect the existing vault note. Record the expected behavior before attempting any refresh. If a refresh is needed, read the current procedure and preserve your own note content before changing existing files.
Keep filenames and personal analysis predictable
The Obsidian integration documents consequences of renaming or moving generated files while new highlights continue to arrive: later exports can create another file at the expected name or location. Treat generated-file naming as part of the workflow rather than reorganizing an active export folder without checking the result.
A practical research note can link to the imported document while recording your own question, interpretation, and next action separately. For example, distinguish a customer's quoted complaint from your hypothesis about which feature to build. Retaining source context makes later correction easier and prevents an imported passage from silently becoming your team's conclusion.
Is Reader export a backup of my complete reading library?
Define the export you actually created. A file containing selected highlights is different from a full-content library export, and a vault synchronization service serves a separate purpose. Reader documents multiple export types. Check the chosen archive's contents and the recovery need instead of treating any successful download as a complete backup.
Why are highlights missing or duplicated in Obsidian?
Follow one sample annotation through Reader, Highlights, and the export destination. Inspect the selected vault, export settings, plugin sync state, and whether a file was renamed or moved. Then distinguish a new highlight that has not arrived from an edit that is outside the documented update behavior. Avoid repeatedly refreshing the whole library before understanding the single-document case.
Sources and editorial method
Official product sources linked throughout this guide were checked on October 29, 2026. Comparisons and fictional exercises are editorial analysis, not hands-on benchmarks or customer results. Product versions, plans, quotas, and interfaces can change. Confirm current documentation before choosing a plan or implementing a workflow.