How Trilium Notes Organizes Notes Without Folders

Trilium Notes replaces folders with a hierarchical tree of notes: any note can contain sub-notes, so the note itself acts as the container. The same note can also appear in more than one place in the tree, so a single piece of content doesn't have to be duplicated to live under two topics. This suits people building a personal knowledge base who want structure without maintaining a separate folder scheme, and it works whether you run Trilium locally on a desktop or sync it with a self-hosted server.

The note tree is the structure

In a folder-based system, structure lives outside the content: you create a folder, then put files in it. In Trilium, structure and content are the same object. A note about a project can hold sub-notes for meeting records, reference links, and drafts, and those sub-notes can hold their own children. There is no separate folder layer to keep in sync with what you actually wrote.

The practical consequence is that you can start writing first and organize later. Create a note, then decide where it belongs by placing it in the tree.

One note, multiple locations

A note can be added in multiple places in the hierarchy. This is the feature that most directly replaces the workarounds people use with folders — shortcuts, duplicate copies, or "see also" links.

For example, a note on a research paper could sit under both a "Reading list" branch and a "Project X sources" branch. Editing it once updates it everywhere it appears, because it is one note with several placements rather than several copies.

Labels, relations, and promoted attributes

Beyond position in the tree, Trilium adds metadata to notes:

• Labels attach categories or tags to a note for grouping and filtering.
• Relations connect one note to another by name, which is useful when the connection isn't parent-child.
• Promoted attributes let you enter structured information on a note and then use that information in tables and boards.

The distinction matters: the tree answers "where does this live," while labels and relations answer "what is this and what does it relate to." A note can be filed in one place but tagged and linked across many.

Workspaces and hoisting keep large trees manageable

A deep tree becomes noisy once it holds both personal and work material. Trilium addresses this in two ways:

• Workspaces group notes so that the tree shows only a specific set of notes — for example, separating personal notes from work notes.
• Hoisting focuses the tree on a chosen note and its descendants, so you work inside one branch without the rest of the tree in view.

Use workspaces when you want a persistent split between contexts, and hoisting when you want a temporary focus on one part of the tree.

What this means for choosing Trilium

The trade-off is that a note-tree model asks you to think about placement and metadata rather than dropping files into folders. If you prefer a strict single-location filing system, folders may feel simpler; if you keep returning to the same notes from different contexts, the multi-placement and labeling model removes the duplication.

To try it, start with a single branch for one active project, add sub-notes as the work grows, and add a label or relation only when you notice yourself wanting the same note in a second place.