Reading through workflow threads here and on r/ObsidianMD, I keep noticing a pattern.
Most heavy clippers end up with default folders like Readwise/Books/, Clippings/, or Glasp/ — created once during setup, then quietly forgotten as graveyards. The clipping tool helps with the transport (web → vault, with metadata), but not with the organizational decision (where does this actually fit in what I already have?). That decision gets postponed, and the postponed decisions never come back.
A line from a PKM thread that stuck with me: someone described forgetting where they saved a note and what they named it, with the original folder structure turning chaotic over time. Search eventually works, but the sense of where things live is gone.
Looking at the popular capture tools — Obsidian’s Web Clipper, Readwise, Glasp — they all share the same structural assumption: pick a target folder and filename template once during setup, every clip lands there. None of them read existing vault content first.
Two questions I’m chewing on:
- For heavy clippers here: how do you actually handle this? Manual sorting after the fact? Templates routing by domain or tag? Or have you embraced the graveyard?
- More structural: has anyone seen a workflow where the destination folder and filename are proposed from existing vault content — something like “this looks similar to your existing note on
[[Cold Outreach]], suggested folder:02_Projects/Marketing, filename: X”? Or is there a reason this doesn’t exist that I’m missing?