Documents and notes decision
Kaptex - NotebookLM Extension
A capable developer can reproduce the core capture-and-send workflow in about a week using existing OSS NotebookLM implementations, but matching Kaptex's cross-site coverage, polish and any private NotebookLM integration details would be costly.
Visit website↗Built by Jon Kraayenbrink, who ships 7 products in this index
$3/mo
$36/yr
Read off the official pricing page.
$100one-off40 h to build
$10/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 7 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Kaptex - NotebookLM Extension alternatives, with the arithmetic →
What a replacement has to do
- Open page → click extension button or injected 'Add to notebook' → choose notebook → send captured source to NotebookLM
What it still won’t have
- Polished cross-site capture coverage and edge-case parsing for many AI sites
- Official support and priority feature requests
- Lifetime deal pricing and built-in user trust/brand
- Possible private NotebookLM integration behaviors or undocumented endpoints
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 7 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal Chrome extension with a small Node/Express background service (host on a $5/mo VPS) and a React popup: implement OAuth via Google to enumerate NotebookLM notebooks; content scripts for YouTube, Reddit, ChatGPT/Claude/Perplexity pages to inject an 'Add to notebook' button; popup UI to pick notebook and send captured source; backend endpoints to accept normalized sources (URL, text, file uploads .txt/.md/.csv/.html/.json) and forward them to the user's NotebookLM account (or to an open-source NotebookLM-compatible backend). Out of scope: polished multi-site edge-case parsing, extensive retries/rate-limiting, analytics dashboard. Include error handling, retries for failed sends, and unit tests for key capture and send flows.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score67
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productKaptex homepage
- official pricingKaptex pricing
- open sourcewebclipper/web-clipper
- open sourcemika-cn/maoxian-web-clipper
Integrity checks
What held up, and what did not.
