Question: Was external custom.css support intentionally removed in 0.101.3?

[pyz0123-cpu]

Description

Hi — I may be misremembering, but in older versions of Trilium (e.g., 0.67 and earlier) I recall being able to place a custom.css file in the data directory to override UI styles.

In 0.101.3 this no longer seems to work. A custom.css file placed next to document.db is ignored, even when using very high‑visibility CSS (global outlines, background changes, etc.). There are also no log messages indicating that theming has been removed or deprecated.

Was this feature intentionally removed during the rewrite, or is this an unintentional regression?

I’m just trying to understand whether external theming is expected to return in future versions, or if the new architecture no longer supports it.

Thanks for any clarification.

TriliumNext Version

0.101.3

What operating system are you using?

Other Linux

What is your setup?

Local (no sync)

Operating System Version

Windows 11 and Linux Mint-Cinnamon (using on both)

Error logs

No response

[dosubot]

External custom.css support was intentionally removed as part of Trilium's architectural changes and is no longer supported as of 0.101.3. The current and only supported way to apply custom styles or themes is by creating a CSS code note with the #appCss or #appTheme attribute inside the app. Placing a custom.css file in the data directory is not recognized or loaded in recent versions. This approach is documented in the official guides for custom app-wide CSS and creating a custom theme. There’s no indication that external custom.css support will return; all theming should now be done through the internal note-based system.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}