Taking notes on podcasts with Snipd, Readwise, and Obsidian
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.
Snipd transcribes English podcasts and generates chapters, enabling timestamp-like skipping and transcript-based navigation.
Briefing
Snipd turns podcast listening into a skimmable, note-ready workflow by combining AI transcription, automatic chapters, and “snips” that export cleanly into Readwise and then Obsidian. The payoff is practical: instead of committing to an entire audio episode, listeners can jump to relevant sections, capture highlights in seconds, and later review everything with linked notes and AI-generated takeaways.
The core experience starts with mobile podcast playback on iOS and Android, where episodes can be transcribed in English and segmented into chapters—functioning like YouTube-style timestamps. For shows that haven’t been processed yet, Snipd can request AI features and return them after roughly 15 to 30 minutes. Once enabled, the transcript is interactive: while audio plays, words highlight in sync, and chapters make it easy to skip directly to the parts that matter.
Capturing notes is built around “snips,” which are essentially user-defined moments inside a transcript. A listener taps to create a snip, then can edit the exact boundaries of what gets captured, rename it, add a private note, and optionally tag it. Snipd also surfaces social proof by showing the most snipped highlights from other listeners—similar in spirit to Kindle’s highlighted sections—so users can quickly see what others found valuable and decide whether to continue the episode or revisit a specific segment.
A newer beta feature, “AI podcast notes,” adds another layer of automation. After marking an episode as completed, beta users receive an email containing a link that generates takeaways (six in the example shown) without requiring manual summarization. The link is portable: it can play back the relevant snipped portion and display the transcript, the two-minute snip details, and episode-level notes. Access is gated via a wait list, but an invite code (“Nicole”) is offered to jump ahead.
The second major reason Snipd fits into a knowledge-management stack is integration. Although Snipd can export highlights as Markdown for tools like Obsidian or Bear, its strongest path is through Readwise. Readwise’s plugin then brings Snipd content into Obsidian, preserving structure: updated titles, key takeaways tied to each highlight, and—when available—automatic linking to existing notes (for example, a “YouTube” note). This reduces the manual linking work that often breaks the flow from consumption to writing.
Still, there are clear limitations. Snipd is English-only, which pushes users toward English podcasts. Fiction-heavy shows—especially narrative formats like Dungeons & Dragons actual plays—don’t always map cleanly onto “takeaway” summaries, and the AI can misname entities or miss details. The transcript-to-knowledge pipeline also lacks some wishlist items: chapters don’t currently appear in the Readwise export, there’s no public API for developers, and a sustainable business model hasn’t been finalized (Snipd is free now, with “premium” being explored).
Even with those gaps, the workflow directly addresses three early frustrations with podcasts: slow consumption, limited skimming, and awkward note-taking. By turning audio into searchable text, then into snips that flow into Readwise and Obsidian, Snipd makes podcast learning feel closer to reading—fast to scan, easy to capture, and ready to revisit later.
Cornell Notes
Snipd makes podcast listening skimmable and note-friendly by using AI transcription and chaptering (English-only) plus “snips” that capture exact transcript moments. It can generate AI podcast notes in beta after an episode is marked complete, delivered via a shareable link with takeaways and transcript context. The captured highlights can export to Markdown or—more powerfully—sync with Readwise, which then routes content into Obsidian through its plugin, including key takeaways and links to existing notes (like a “YouTube” page). The result is a repeatable loop: listen, snip, review later with an outline instead of starting from scratch. Limitations include imperfect transcription, no multi-language support, and a mismatch between “takeaways” and fiction-style storytelling.
How does Snipd make podcasts easier to skim before committing to the full episode?
What exactly is a “snip,” and how does it turn listening into structured notes?
What does “AI podcast notes” do, and why is it useful even if it’s not a deep summary?
How does Snipd connect to Obsidian in a way that reduces manual work?
What are the main shortcomings that could affect different podcast types or expectations?
Review Questions
- What mechanisms in Snipd allow a listener to navigate an episode without listening end-to-end?
- Describe the full workflow from creating a snip to seeing it inside Obsidian.
- Which limitations (language support, fiction fit, accuracy, export/API gaps) could change how you’d use Snipd?
Key Points
- 1
Snipd transcribes English podcasts and generates chapters, enabling timestamp-like skipping and transcript-based navigation.
- 2
“Snips” let users capture precise transcript moments, edit their boundaries, and attach private notes that can match existing Obsidian pages.
- 3
AI podcast notes (beta) generate takeaways after an episode is marked complete and deliver them via a shareable link with transcript and snip context.
- 4
Snipd’s strongest workflow is syncing with Readwise, then using Readwise’s Obsidian plugin to import highlights with key takeaways and often automatic note linking.
- 5
Snipd exports to Markdown as an alternative, but the Readwise integration is the main path for structured knowledge capture.
- 6
Limitations include English-only transcription, occasional AI errors in names/details, and a “key takeaways” format that may not suit fiction-heavy shows.
- 7
Snipd is free now, with premium and additional integrations under consideration, including a wishlist for Readwise-export chapters and a public API.