How to Get a YouTube Summary to Google Docs

Notion and Obsidian are better places to keep a personal archive. Google Docs beats both for the case where somebody else has to read it, comment on it, and not have to create an account first.

That is a real distinction and it decides which destination you want. A summary you are keeping wants a database. A summary you are circulating before a meeting wants a Doc, and getting there is a paste — the Markdown export is the vehicle in both cases.

Three ways in, and which to use

The first row is the one to use and the second is the mistake people make. Docs does not interpret raw Markdown on paste the way Notion does, so pasting the export as text gives you a document full of hash symbols and square brackets.

Copying the formatted summary from the page carries the structure and the links across intact, because that is HTML rather than Markdown and Docs reads HTML on the clipboard.

Making the Doc worth sending

A pasted summary is raw material. Three additions turn it into something a colleague can act on, and they take about five minutes.

Put your conclusion first. The summary is organised the way the video was, which is almost never the order your reader needs. Two sentences at the top saying what this means for the thing you are working on is the part they will actually read.

Say what was checked. If you verified a figure at its timestamp, note it. If you did not, say that too. A reader who knows which claims are unverified can handle the document responsibly; one who does not will treat all of it as established.

Link the video at the top, not just in the timestamps. The first question anyone asks is "what is this from".

Where Docs is genuinely better

Comments. Someone can query a specific claim in the margin, which is exactly the interaction a summary needs. A paraphrase that nobody can challenge in place tends to harden into fact.

Suggesting mode. A colleague who watched the video can correct the summary directly, and you see what changed.

No account friction. Anyone with the link can read it, including people outside your organisation.

Version history. If the summary gets edited into something the video did not say, the record of that is automatic.

These are all collaboration properties, which is the pattern: summaries shared with a team want a Doc; summaries kept for yourself do not.

The risk that comes with sharing

Worth stating directly, because a Doc makes this failure easy in a way a private note does not.

A summary shared with ten people becomes ten people's understanding of what was said, and none of them heard it. That is fine for "this webinar covered X, Y and Z". It is not fine for a specific figure, a vendor's claim about performance, or anything someone will make a decision on.

The convention that prevents the problem is simple and worth agreeing before the first Doc goes out: anything anyone plans to act on gets checked at its timestamp by the person acting. The summary distributes attention; it does not distribute responsibility for being right.

Attribution deserves the same care. Automatic captions carry no speaker labels, so on any recording with more than one voice, who said what is inferred. A name next to a claim in a shared document should be verified before it gets there.

A structure that gets read

Most circulated summaries fail not because they are wrong but because nobody reads past the first screen. The order fixes that, and it is the inverse of how the summary arrives.

1. What this is. One line: the video, who made it, how long.
2. Why you are sending it. One line. If you cannot write this, do not send it.
3. The three things that matter. Your judgement, not the video's structure.
4. What you checked and what you did not. Explicitly.
5. The full summary. Below the fold, for anyone who wants it.

Point four is the one that makes the document trustworthy rather than merely informative. A reader who knows which claims were verified at the timestamp and which are unexamined paraphrase can use the document responsibly.

Without it, everything in the Doc carries the same apparent authority — and a summary is a paraphrase throughout, however confident the prose reads.

When a Doc is the wrong choice

Building an archive. Docs has no structure across documents. Two hundred summaries in Drive is two hundred files with no properties, no tags and no way to ask questions across them.

Anything confidential. Check your own policy before a summary of an internal recording goes into a document that is one sharing-setting mistake from public.

Notes you will extend over time. Docs is built for documents that get finished. A living note is better served elsewhere.

Anything you want searchable in bulk. Drive search reads inside documents, but a hundred summaries in a folder have no properties to filter on and no way to ask a question across the set. That is a database job.

Google's own documentation on sharing covers the permission model, and it is worth understanding before circulating anything, because the default in many organisations is more open than people assume.

Why there is no direct integration

There is no Google Docs connection here — no OAuth, no "send to Docs" button, no Drive permissions requested.

That is deliberate. A direct integration would mean asking for access to your Drive, which is a large permission for something a copy and paste already does in five seconds. The export exists so the summary is portable; where it goes is your decision and does not require us holding a token.

Frequently asked questions