Why You Should Use Block References in Logseq: A Beginner’s Introduction

Block references in Logseq let users link to a specific block of text—using a unique block ID—so notes can be reused without copying the underlying content. That matters because Logseq users often write in a Daily Journal, then later need to reference the same idea elsewhere; copying text creates duplicates that drift out of sync.

In practice, block references behave like page references but target a block instead of an entire page. Each block gets a unique ID, and linking uses that ID inside normal brackets. When someone copies a block reference (for example by pressing Ctrl C without selecting text), pasting elsewhere inserts a “weird number” reference; pressing Enter turns it into a clickable link. Users can also rename the link text while keeping it pointed at the same block, effectively creating a custom label for the underlying block ID.

A key distinction is between a block reference and a block embed. A block reference creates a link to the block, while a block embed pulls the block content (and its substructure) into the destination. The transcript highlights two ways to embed: searching for “block and bat” (via slash commands like /embed) and selecting the block by its unique ID, or copying with Ctrl e to create an embed that pastes the full block. This difference becomes important when users want to display context versus simply point readers to the source.

Removing or editing references requires care because references are lightweight pointers, while embeds can be tied to the source content. If someone edits the embedded content in the wrong place, they may accidentally change the original source block; later, the “missing” content appears to “come back” because the source was modified. The safer approach is to ensure the correct line is selected before deleting the reference text, typically by selecting the whole reference line and then using Backspace.

Block references also provide a built-in way to audit where a block is used. Clicking the reference indicator on a block reveals all incoming references. The transcript notes a layout difference: page links tend to appear at the bottom, while block references show their incoming references at the top, reflecting that they relate to the block itself rather than sub-elements.

Real-world uses range from navigation to knowledge management. Block references can power a table of contents that jumps to individual scene blocks in a script. They also help assemble coherent narratives by collecting journal blocks into a single place via embeds. Because embedded blocks stay connected to their sources, updates propagate to every location that references them—supporting “just in time note-taking,” where users summarize first and refine later.

The workflow extends to research and task tracking. “Slip notes” organize journal entries into ordered block embeds for deeper topic work. For mini-projects, users create a small to-do block and then add time-stamped journal entries that reference that project; clicking the project later reveals all related work and subtasks across days. The result is a practical way to keep small tasks from fragmenting, while preserving a clear history for handoffs or follow-up work.