YouTube Notes Logseq-Style: Video Summaries as Blocks

Keeping YouTube notes Logseq-style is mostly a matter of respecting the outline. In Logseq every bullet is a block, and a block can be referenced, embedded, tagged and queried on its own. A summary made of bullets fits that model with almost no rework.

There is no integration between this tool and Logseq, and no plugin. You export the summary as Markdown, copy it, and paste it into a page. What follows is how to make that paste land well, and what to add afterwards.

Why an outliner changes the note

In a document-based app, a video note is one page you open and read top to bottom. In Logseq, the page is only a container. The unit that matters is the single takeaway, because that is the thing you will link to from somewhere else.

That changes what makes a good note. A takeaway that makes sense only in the context of the bullets around it is weak in Logseq. One that stands alone — a specific, checkable claim — can be pulled into a journal entry or a topic page and still read correctly.

Our key takeaways are written to be checkable claims, which helps. The work you add is making each one refer to something you already know.

Getting the summary in: copy and paste

1. Summarize the video and export or copy the Markdown.
2. Create a page for the video in Logseq, named for the channel and title.
3. Paste into an empty block with the normal paste shortcut.
4. Check the nesting once, then fix any bullet that landed at the wrong level.

The paste shortcut matters. Logseq's copy and paste documentation describes two modes. The default "enhanced" paste handles structure, and if it detects HTML in what you copied, it pastes the HTML. A raw paste — add Shift to the shortcut — inserts all the copied text into the current block without any formatting.

So use the normal paste, and copy the Markdown rather than selecting the rendered summary on our page. A raw paste gives you one giant block, which defeats the point of an outliner.

Where the page goes is up to you. Some people keep one page per video and link it from the journal. Others paste straight into the day's journal under a single parent block, and let the properties and tags do the filing. Both work; pick one and keep to it.

Page properties for YouTube notes Logseq can query

Logseq's properties documentation says page properties go in the first block of the page, written as name:: value. Any other block can carry its own block properties.

Four are enough for video notes. Add them by hand after the paste, since our export does not write Logseq properties for you.

• source:: the video URL, so every note keeps its evidence.
• channel:: who made it, which is your proxy for trust.
• watched:: the date, for "around when I was working on X".
• tags:: two or three topics, separated by commas.

The docs note that comma-separated tags values become page references automatically, so each tag links to its own page. They also note a property value cannot contain a newline, so keep each one on a single line.

Timestamps as links

Each takeaway in the export carries a link to the moment in the video it came from. In Logseq that stays an ordinary Markdown link inside the block, and clicking it opens YouTube at that second.

This is what makes a block safe to reuse. When a takeaway turns up in a journal entry six months later, the link travels with it, and you can check the claim before you build on it. Logseq's docs also list a separate YouTube timestamp feature for the desktop app; our links do not use it, and they do not need to.

One paste behaviour to know: the same docs say enhanced paste wraps some video URLs, including YouTube ones, in a video macro. Paste a bare link on its own and you get an embedded player; inside a property or a Markdown link, it stays a link.

Referencing takeaways from your journal

The payoff of blocks is that you can reference one takeaway without copying it. Logseq gives every block an id you can reference, so a journal entry can point to the exact claim that prompted it.

Take a single takeaway such as a claim about pricing. Referenced from a journal entry about your own pricing decision, it sits next to the thinking it influenced, and it still links back to the video it came from.

That is where video notes stop being an archive and start being useful. Instead of a page per video that nothing links to, you get single claims threaded into the days and topics where you used them. Our general video notes workflow covers the habit side; Logseq just makes the linking cheap.

Roam works the same way

Roam Research is also block-based, so the same approach applies: paste the Markdown bullets, check the nesting, and add attributes at the top with the same double-colon syntax. There is no integration with Roam either.

Paste one summary and check the result before you do a batch. Outliners differ in how they handle headings and nested lists, and ten seconds of checking saves fixing twenty pages.

Where this breaks down

It is manual. Every summary is a copy and a paste. There is no sync, no import folder and no plugin from us.

Five exports a day. The free tier gives five summaries a day — TL;DR, takeaways, timestamped chapters and full notes, all of it — and the count resets at midnight UTC. Nothing else is capped: any length, any caption language.

Paraphrase travels too. A referenced block looks just as authoritative in your journal as it did on the video page. If a takeaway is going to carry weight in a decision, click its timestamp and hear the sentence first.

Text only. We read captions, never the frames or comments. A diagram that was never described aloud will not be in any block. If you prefer plain files and a document-shaped note, Obsidian takes the same export as a file instead.

Frequently asked questions