How To Highlight Physical Books in Readwise
Based on Duddhawork's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Photographing one page at a time improves OCR reliability when importing physical-book highlights into Readwise.
Briefing
Readwise can turn physical-book highlighting into searchable, spaced-repetition notes—but doing it well depends on how the highlights are captured and tagged. The core workflow is to photograph a single page (not two tightly packed pages) so OCR can reliably extract the highlighted sentence, then save that passage as a Readwise highlight tied to the correct book. Once the text lands in Readwise, it becomes part of the app’s daily review system, which boosts recall and retention compared with manually flipping back through a physical copy.
The process starts with a practical problem: physical highlights are easy to mark but hard to review quickly. In the example, a hockey analytics book from 2020 had yellow highlighter notes, yet revisiting them required page-by-page searching—too slow to be useful. The workaround was earlier manual journaling with page numbers and thoughts, but the goal now is to migrate those insights into Readwise so they show up in reminders and benefit from space repetition.
In Readwise, highlights can be added either by typing the passage or by using the “photo” route. The photo route relies on OCR, so the transcript emphasizes a key capture rule: when photographing, include only one page per image when pages are close together. If two pages appear in the same photo, OCR may struggle and misread where the text belongs, even if it eventually guesses a page number. After taking a photo, the user selects the extracted sentence, saves it as a highlight, and optionally adds a note such as the page number or a brief interpretation.
Organizing notes inside Readwise also matters. The transcript demonstrates adding a title to structure the imported content: by using the tag “.h1” (and suggesting “h2.h” for lower-level headings), Readwise can treat that line as a header. In the browser view, the header then appears as a section label—effectively creating a table-of-contents-like structure for the book’s highlights.
There’s a tradeoff. OCR can be faster for long passages, but it can introduce typos and formatting issues (including spacing and posture-related alignment problems). Typing may be slower but can be more accurate. The takeaway is not a single “best” method; instead, it’s a repeatable approach—photo-based OCR for efficiency, manual typing for precision—so readers can test which workflow fits their reading habits and tolerance for cleanup.
Cornell Notes
The transcript lays out a workflow for importing physical-book highlights into Readwise using OCR and optional manual typing. To make OCR reliable, it recommends photographing one page at a time—especially when pages are close together—then selecting the extracted sentence and saving it as a highlight tied to the correct book. It also shows how to create structure in Readwise by adding headers using the “.h1” tag (and notes that “h2.h” can be used for subtitles). The main decision point is speed versus accuracy: OCR can be quicker for long passages but may produce typos or formatting glitches, while typing is slower but more precise.
Why does importing physical-book highlights into Readwise matter for review habits?
What capture rule improves OCR accuracy when photographing book pages?
What are the two main ways to add a highlight in Readwise from a physical book?
How can imported highlights be organized into sections inside Readwise?
When might manual typing be preferable to OCR?
Review Questions
- What specific photo-taking adjustment helps OCR avoid misreading when pages are close together?
- How does the “.h1” tag change how content appears in Readwise’s browser view?
- What tradeoffs does the transcript identify between OCR-based importing and manual typing?
Key Points
- 1
Photographing one page at a time improves OCR reliability when importing physical-book highlights into Readwise.
- 2
Use Readwise’s “add highlight” flow to save extracted sentences as highlights tied to the correct book.
- 3
After OCR extraction, verify and select the intended sentence before saving to avoid incorrect imports.
- 4
Add structural headings using the “.h1” tag so sections appear as headers in Readwise (with “h2.h” suggested for subtitles).
- 5
OCR-based importing can be faster for long passages, but it may introduce typos or formatting/spacing issues.
- 6
Manual typing is slower but can reduce OCR mistakes and preserve formatting accuracy.
- 7
The most effective workflow depends on whether speed or precision matters more for the reader’s review process.