Before exporting from NotebookLM, separate these three things

NotebookLM export questions become confusing when every output is treated as the same thing.

I use three buckets:

1. Native exports offered by the NotebookLM interface.
2. Content that can be copied from a chat or Studio artifact.
3. Additional formats created by another tool, such as a BibTeX file, an APKG deck, or Markdown, PDF and HTML copies of saved material.

The destination decides what matters. A reference manager needs structured citation fields. Anki needs front, back and source fields. A document archive needs readable text and stable filenames.

NotebookBloom's export guide had 478 impressions but only one click in the September 22 GSC snapshot. I rewrote it to answer the destination question first instead of opening with a long feature list.

Implementation check

Before publishing or shipping this workflow, I verify it against a real notebook, keep the limitation visible, and make sure the next action returns to evidence.

Related workflow: https://notebookbloom.com/blog/notebooklm-export-limitations/?utm_source=devto&utm_medium=content&utm_campaign=ops13_export_boundaries