Should you limit connections in a zettelkasten?

Limiting connections in a Zettelkasten is usually the wrong instinct. The system’s core strength comes from linking notes so ideas can be found through their relationships, not through rigid categories or artificial scarcity. When connections multiply, the real risk isn’t “too many links”—it’s clutter: lots of notes that aren’t organized in a way that makes them retrievable. Clutter happens when information is effectively unsearchable, like tossing paper notes into a box; the notes may exist, but they become unusable because there’s no structure to navigate them.

In a Zettelkasten, connections are what turn scattered notes into a navigable network. Even if a writer can’t recall a specific term, they can start from a related note and follow links until they reach the missing concept. That’s why the advice is to avoid managing connections by number. Instead, focus on making the notes themselves precise and findable. A note that expresses a single, specific, irreducible idea tends to have fewer connections than a broad note, and that specificity makes later retrieval faster and more reliable.

The practical method is “atomicity”: write notes so basic they contain only one idea, and when that idea can be reduced further, create the smaller note. This keeps the network meaningful rather than noisy. At the same time, broad topic notes aren’t automatically bad. A wide note with many links can help someone discover smaller, atomic notes beneath it. The problem arises when a broad note becomes too unwieldy—so the fix is to convert it into a hub note.

A hub note acts like an index or table of contents. It organizes subtopics and then points to the specific notes under each subtopic, so the main topic note doesn’t turn into one giant, exhausting list of links. If any subtopic still grows too large, it can be split into its own note, preserving navigability without forcing a connection limit.

Another major source of clutter is duplication—multiple notes that represent the same idea under different names. Instead of creating separate notes like “Sight Swap,” “Sight Swap Notation,” and “Juggling Notation” for what is essentially one concept, consolidate into one note and use aliases. Aliases let the single note appear under different search terms, including synonyms, common misspellings, or alternative phrases someone might use later.

So the answer to whether connections should be capped is straightforward: don’t manage connections by quantity. Manage note quality—atomic, non-duplicative notes with aliases—and use hub notes when broad topic areas become too dense to browse. With that approach, a Zettelkasten can stay searchable even as the network grows, without turning linking into a fear-driven exercise.