Get AI summaries of any video or article — Sign up free
Reading and taking notes on a Kindle and Obsidian thumbnail

Reading and taking notes on a Kindle and Obsidian

Nicole van der Hoeven·
5 min read

Based on Nicole van der Hoeven's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use Shortform (or reviews) to pre-screen books so time goes to titles worth reading.

Briefing

A streamlined workflow for Kindle highlights and notes can turn passive reading into a searchable knowledge base inside Obsidian—if the setup is tuned for tagging, formatting, and structure. The core idea is simple: highlight and annotate on a Kindle, let those annotations flow through Readwise, and land them in Obsidian with the right metadata so they become immediately linkable notes rather than scattered exports. That direct pipeline is presented as the reason reading and note-taking feel cohesive instead of duplicative.

The approach starts before a book is even opened. Rather than committing time blindly, the workflow narrows the “top of the funnel” using Shortform to screen books in advance. Shortform provides chapter-by-chapter guidance and lets the reader preview highlights, helping decide whether a book is worth reading rather than replacing the actual reading experience. If Shortform isn’t used, the alternative is to rely on reviews and summaries to filter choices.

The second and third pillars focus on the Kindle → Readwise → Obsidian integration. Using the Readwise Official Obsidian plugin, Kindle highlights are sent to Readwise and then exported into an Obsidian vault, creating a dependable link between what’s marked on the Kindle and what appears as notes. The workflow then tightens by adjusting Readwise export settings so imported books are tagged correctly. In Readwise’s Obsidian configuration (via readwise.io/export), the user can choose folder placement, file naming, and—most importantly—file format. Custom formatting is used so the book title consistently appears as a heading, with YAML front matter carrying tags like an inbox tag (TVZ), a “Readwise” tag, content type (book/podcast/tweet), and a date. There’s also control over how new highlights merge into existing notes and how personal Kindle notes are displayed (including quote formatting to distinguish user-written notes from author text).

From there, the system emphasizes behavior and structure. Multiple Kindle devices are encouraged—physical devices or apps across browser, mobile, and tablet—paired with the habit of always having at least one Kindle-ready option nearby to reduce mindless scrolling. The notes workflow also supports reading multiple books at once without guilt, letting readers switch to whatever mood fits rather than forcing completion of dense nonfiction.

On the note-taking side, the workflow pushes for capturing ideas while reading and pre-planning how they’ll connect later in Obsidian. Kindle notes can include terms that already have corresponding Obsidian pages, so synced highlights become clickable links. It also recommends delineating chapters by converting Kindle outline sections into Obsidian headings: adding notes with an h2 marker so chapter-level structure appears under the book’s h1 heading once synced. Finally, practical friction reducers—like a Kindle cover or pop socket for one-handed reading—are treated as part of sustaining the habit.

The workflow extends beyond private notes through Goodreads integration. Connecting Kindles to Goodreads marks completed books automatically and can surface Kindle highlights and notes on the social reading platform, enabling reading challenges and discovery while keeping annotations synced.

Cornell Notes

The workflow centers on turning Kindle annotations into structured, linkable Obsidian notes. Kindle highlights and notes are sent to Readwise and then synced into an Obsidian vault using the Readwise Official Obsidian plugin, creating a direct pipeline from reading to a searchable knowledge base. Readwise export settings are customized so imported notes land in the right folders, use consistent formatting (including YAML front matter tags), and preserve distinctions between author text and personal notes. The system also improves note usefulness by encouraging chapter headings (e.g., h2) and by writing Kindle notes that reference existing Obsidian pages. The result is reading that feeds an organized second brain rather than producing isolated highlights.

How does the workflow decide which books are worth reading before time is spent?

It narrows the “top of the funnel” using Shortform to screen books in advance. Shortform provides a chapter-by-chapter breakdown and lets the reader preview highlights, helping determine whether a book is worth reading rather than replacing the reading itself. If Shortform isn’t used, the alternative is to read or listen to reviews to filter choices.

What makes Kindle highlights become useful notes inside Obsidian instead of just saved marks?

The integration path is Kindle → Readwise → Obsidian. Highlights created on the Kindle are sent to Readwise, then exported into Obsidian through the Readwise Official Obsidian plugin. With this setup, everything highlighted on the Kindle is expected to show up in the Obsidian vault, making the notes immediately part of a connected system.

Why adjust Readwise settings after installing the plugin?

Because correct tagging and formatting determine how notes behave later. In Readwise’s Obsidian configuration (readwise.io/export → Configure), the user can set folder placement, file format, and how new highlights merge into existing notes. Custom formatting includes YAML front matter tags such as an inbox tag (TVZ), “Readwise,” content type (book/podcast/tweet), and a date, plus consistent heading structure so the book title appears as a heading.

How can chapter structure from a Kindle outline be preserved in Obsidian?

By converting outline sections into Obsidian headings during reading. The Kindle outline headings aren’t recognized by default, so the reader highlights a section and adds a note containing “h2.” With the book title mapped to h1, chapter-level headings become h2 in Obsidian after syncing. This keeps the book’s structure intact and provides context around highlights.

What reading habits are recommended to keep the system sustainable?

Use multiple Kindles/devices so there’s always a reading option nearby (Kindle Oasis, Kindle 2022, Kindle Paperwhite, or Kindle web/app/tablet). Also read multiple books at the same time without guilt, switching to whatever mood fits so dense nonfiction doesn’t stall the habit. The workflow also encourages making notes while reading with planned links to existing Obsidian pages.

How does Goodreads integration fit into the overall note-and-reading workflow?

Connecting Kindles to Goodreads automatically marks books as completed when finished on Kindle. Goodreads can also display Kindle notes and highlights, synced automatically, and supports social features like following readers with similar tastes and setting reading challenges. The user can view highlights and notes there, though they rarely make them publicly visible.

Review Questions

  1. What specific Readwise configuration changes help ensure imported Kindle notes are tagged and formatted in a way that supports later querying and linking in Obsidian?
  2. How does adding “h2” notes to Kindle outline sections affect the structure of the synced Obsidian file?
  3. What combination of device availability and reading strategy (single vs multiple books) is recommended to reduce friction and maintain consistent reading?

Key Points

  1. 1

    Use Shortform (or reviews) to pre-screen books so time goes to titles worth reading.

  2. 2

    Set up the Readwise Official Obsidian plugin so Kindle highlights flow into Readwise and then into an Obsidian vault.

  3. 3

    Customize Readwise export settings to control folder placement, file formatting, and YAML front matter tags (including inbox and content-type tags).

  4. 4

    Write Kindle notes that reference existing Obsidian pages so synced highlights become clickable links.

  5. 5

    Preserve book structure by turning Kindle outline sections into Obsidian headings (e.g., using “h2” for chapters).

  6. 6

    Keep reading friction low by using multiple Kindle devices/apps and ensuring at least one is always within reach.

  7. 7

    Read multiple books at once to match mood and avoid guilt-driven completion pressure.

Highlights

The Kindle → Readwise → Obsidian pipeline is positioned as the key to making highlights immediately actionable as notes.
Readwise export settings can be tuned so YAML front matter tags (like TVZ, Readwise, content type, and date) organize notes for later retrieval.
Chapter headings can be reconstructed in Obsidian by adding “h2” notes to Kindle outline sections during reading.
Multiple devices and always-having-one-nearby is treated as a practical anti-scroll strategy to keep reading momentum.
Goodreads integration can automatically mark completed Kindle books and surface synced highlights and notes.

Topics

Mentioned