Trilium allows you to share selected notes as publicly accessible read-only documents. This feature is particularly useful for publishing content directly from your Trilium notes, making it accessible to others online.
To use the sharing feature, you must have a server installation of Trilium. This is necessary because the notes will be hosted from the server.
Enable Sharing: To share a note, toggle the Shared
switch within the note’s interface. Once sharing is enabled, an URL will appear, which you can click to access the shared note.
Access the Shared Note: The link provided will open the note in your browser. If your server is not configured with a public IP, the URL will refer to localhost (127.0.0.1)
.
When you share a note, you actually share the entire subtree of notes beneath it. If the note has child notes, they will also be included in the shared content. For example, sharing the “Formatting” subtree will display a page with basic navigation for exploring all the notes within that subtree.
You can view a list of all shared notes by clicking on “Show Shared Notes Subtree.” This allows you to manage and navigate through all the notes you have made public.
Shared notes are published on the open internet and can be accessed by anyone with the URL. The URL’s randomness does not provide security, so it is crucial not to share sensitive information through this feature.
To protect shared notes with a username and password, you can use the #shareCredentials
attribute. Add this label to the note with the format #shareCredentials="username:password"
. To protect an entire subtree, make sure the label is inheritable.
The default shared page is basic in design, but you can customize it using your own CSS:
Custom CSS: Link a CSS code note to the shared page by adding a ~shareCss
relation to the note. If you want this style to apply to the entire subtree, make the label inheritable. You can hide the CSS code note from the tree navigation by adding the #shareHiddenFromTree
label.
Omitting Default CSS: For extensive styling changes, use the #shareOmitDefaultCss
label to avoid conflicts with Trilium’s default stylesheet.
You can inject custom JavaScript into the shared note using the ~shareJs
relation. This allows you to access note attributes or traverse the note tree using the fetchNote()
API, which retrieves note data based on its ID.
Example:
const currentNote = await fetchNote();
const parentNote = await fetchNote(currentNote.parentNoteIds[0]);
for (const attr of parentNote.attributes) {
console.log(attr.type, attr.name, attr.value);
}
Shared notes typically have URLs like http://domain.tld/share/knvU8aJy4dJ7
, where the last part is the note’s ID. You can make these URLs more user-friendly by adding the #shareAlias
label to individual notes (e.g., #shareAlias=highlighting
). This will change the URL to http://domain.tld/share/highlighting
.
Important:
/
) within aliases to create subpaths is not supported.All shared notes are grouped under an automatically managed “Shared Notes” section. From here, you can view, share, or unshare notes by moving or cloning them within this section.
To customize the favicon for your shared pages, create a relation ~shareFavicon
pointing to a file note containing the favicon (e.g., in .ico
format).
You can designate a specific note or folder as the root of your shared content by adding the #shareRoot
label. This note will be linked when visiting [http://domain.tld/share](http://domain/share)
, making it easier to use Trilium as a fully-fledged website. Consider combining this with the #shareIndex
label, which will display a list of all shared notes.
#shareRaw
label to share a note without any HTML wrapper.#shareDisallowRobotIndexing
label to prevent search engines from indexing the shared page by including a noindex, follow
meta tag and X-Robots-Tag: noindex
header.#shareIndex
label, the content will display a list of all shared note roots.While the sharing feature is powerful, it has some limitations:
Some of these limitations may be addressed in future updates.