Second Brain: Your QUICK START guide | Logseq (and Roam)

A fast path to building a “second brain” in Logseq hinges on one practical idea: start writing notes immediately as separate, atomic pages, then let cross-linking and tagging emerge as the library grows. Logseq’s core strength is how easily it turns text into interconnected pages—type a page name using double square brackets, and a new page appears. From there, the system becomes a living network rather than a static document collection, with links and hashtags serving as navigational structure.

The setup begins with choosing where the notes live. Logseq uses a “graph” (folder-based workspace) to store everything locally, which keeps the knowledge base secure on the user’s computer. To reduce the risk of losing that local folder, the workflow recommends backing it up through services like iCloud, Dropbox, or Google Drive. If using the browser version, the browser must be granted permission to read and write files in the chosen folder.

For capturing knowledge, the quickest entry point is the journal. Starting from the journal page reduces friction because it’s already the home base for new writing. As notes accumulate, the journal also provides a simple timeline view: scrolling back through previous days shows what was worked on. Logseq supports embedding rich media directly into notes—tweets, videos, and images. On desktop, PDFs can be imported into the app. For video-based learning, a YouTube embed command (using a forward slash “YouTube embed” workflow) lets the video play inside a Logseq page; then notes can be organized by using the video’s main themes as page titles and writing observations in the user’s own words beneath each title.

The “atomic” method is the next step: each idea becomes its own node. One approach is to create pages from highlighted subtitles—highlight text, create a new page with double square brackets, then open that page in the sidebar (Shift-click) to write the idea at a granular level. To connect thoughts, the workflow recommends searching for related notes already in the slipbox and inserting links into the new note. Adding a short sentence that states the relationship between ideas helps make the connection explicit, not just structural.

As the slipbox grows, linking becomes easier because search surfaces more relevant pages. At that point, hashtags can add another layer of retrieval. In Logseq, hashtags and links both create navigable pages: a hashtag page automatically lists notes containing that tag, making it easy to browse similar ideas. The guidance on tagging emphasizes future usefulness over present categorization—following advice attributed to Sönke Ahrens in “How to Create Smart Notes,” tags should be keywords the user would likely search for later, while avoiding an excessive number of tags that can scatter nodes and reduce specificity.

Overall, the method is intentionally lightweight at the start: write note after note to populate the second brain, then refine with linking and tagging once there’s enough material to connect. The hardest part is simply beginning—details can come later once the system is producing real content.