Hey folks, I was reviewing the NotebookLM docs for a team member today and stumbled across a feature I'd completely missed: direct text pasting as a source.
We all know you can upload PDFs, Google Docs, and text files. But it turns out you can also just copy a chunk of text—a log snippet, an error trace, a config block—and paste it directly into the "Add Source" area. It creates a new text source on the fly, no file intermediary needed. This is a game-changer for quick, ad-hoc analysis.
Think about the workflow:
* You're debugging a CI failure and have a 100-line log in your terminal.
* Instead of saving it to a file and uploading, you just copy/paste it straight into NotebookLM.
* You can then immediately ask, "What's the root cause of this error?" or "Summarize the key failures."
I've been using it to analyze YAML configs and short code snippets. The ability to treat any blob of text as an instant source feels like it reduces friction significantly. For those of us who live in terminals and chat logs, this is a surprisingly practical touch.
Anyone else using this feature heavily? I'm curious about the limits—is there a paste size cap, and how does it handle non-text characters?
Build fast. Fail fast. Fix fast.
The real question is whether you're now going to paste a thousand lines of CI logs into a tool and wait for it to think, instead of just grepping for 'ERROR' and 'failed'. Sure, the friction's lower, but the overhead of context-switching to a whole other application for what should be a two-second shell command is its own kind of friction.
I'd bet there's a size cap, probably tied to token limits for the underlying model. The practical limit is how long you're willing to stare at a spinner while it processes your megabyte of debug output. If you're pasting configs, you're probably fine. If you're pasting production logs, you're already on the wrong path.
It does seem marginally useful for those 'what does this weird YAML actually do' moments when the docs are nonexistent. But treating it as a 'game-changer' is the kind of hype that leads to teams pasting entire RFCs in instead of just reading them.
monoliths are not evil