How To Use Obsidian: Canvas Plug-In For Writers, Designers, and Everybody Else Too

Obsidian’s Canvas turns note-taking into a visual workspace: an “infinite canvas” where writers, designers, and presenters can place cards, connect them with labeled arrows, and keep everything organized without generating a separate markdown note for every card. Built into Obsidian’s core (not a third-party add-on), Canvas is designed for people who think in pictures or need a flexible way to map arguments, outlines, and creative structure.

Getting started is straightforward. Users create a new canvas from Obsidian’s command palette, choose a folder for where canvases live, and then navigate the workspace by zooming in and out and dragging around the space. Each card functions like a self-contained sticky note: it can contain markdown and familiar writing elements, but it doesn’t automatically create a new note in the vault for every card added. That distinction matters for workflow—Canvas becomes a staging area for ideas and relationships, while the vault stays cleaner and more intentional.

Cards can be arranged freely, including in custom “flows” that match how someone thinks—left-to-right, downward, or sideways. The layout supports selection and movement of multiple cards at once, and it also allows grouping. Grouping lets users move clusters together while still keeping internal cards movable, provided the cards remain inside the group boundaries.

Canvas becomes even more powerful when it pulls in existing vault content. Users can drag notes from the sidebar onto the canvas, making those notes visible directly in the workspace. For database-backed notes, Canvas can display the live results of a Data View query, so the information shown on the canvas stays synchronized with the underlying query. Media can also be embedded: an example workflow pastes YouTube embed code into a card, and Obsidian automatically renders the video preview inside the card. If needed, users can open the underlying note without leaving the canvas, keeping the visual context intact.

Connections are where Canvas shifts from “whiteboard” to “argument builder.” Users draw arrows between cards and can refine each connection with descriptors/labels and arrow styles—such as changing whether the arrow has one or two pointed ends or altering arrow color. These annotations help clarify what a relationship means (for example, which idea supports another, or what a reference is meant to justify).

The practical takeaway is how Canvas supports iterative writing and planning. A central hub model works well: one core concept sits in the middle while related ideas radiate outward, forming a map of associations. Many users keep a canvas open over days, adding new cards as new thoughts appear so details don’t get lost. Canvas effectively becomes a living organizational layer for brainstorming, outlining, and building a coherent structure from scattered notes and references.