Hide all the disabled UI in V2

[vdl-dsi-architecture]

We do not use login as we just want a public self hosted tool to manipulate pdf without storage or custom config. The new UI shows all the disabled settings grayed out, is there a way to actually hide them to reduce visual clutter and confusion?

For reference, this is the old UI and the new one, one is clearly easier to use for non technical (and technical) users (especially the settings):

---

[dosubot[bot]]

Hi @vdl-dsi-architecture! I'm Dosu and I’m helping the Stirling-PDF team.

You can now fully hide disabled tools (not just gray them out) in Stirling PDF V2 by enabling the "Hide unavailable tools" setting. To unlock this option in your self-hosted setup, set the environment variable DISABLE_ADDITIONAL_FEATURES=false—for example, add -e DISABLE_ADDITIONAL_FEATURES=false to your Docker run command or set it in your Docker Compose file under the environment section. After restarting, you'll see the "Hide unavailable tools" toggle in the General settings tab; turning it on will remove all disabled tools from the UI, making things much cleaner for your users docs PR #4916.

If you need even more control, you can override UI templates by enabling customHTMLFiles and editing the relevant files in the customFiles/templates directory docs.

To reply, just mention @dosu.

---

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

   

[vdl-dsi-architecture]

Hide unavailable tools is local to the browser, it doesn't affect all users.

[dosubot[bot]]

You're correct—the "Hide unavailable tools" setting is a UI preference stored locally in each browser, so it doesn't affect all users globally docs.

If you want to hide tools for everyone, you can use the ENDPOINTS_TOREMOVE or ENDPOINTS_GROUPSTOREMOVE environment variables to fully disable and remove specific tools or groups from the UI for all users. For even more control, you can enable custom HTML overrides (set SYSTEM_CUSTOMHTMLFILES=true) and edit the templates in customFiles/templates to hide or change how disabled tools appear. There isn't a built-in global toggle for the "Hide unavailable tools" feature at this time.

To reply, just mention @dosu.

---

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

   

[vdl-dsi-architecture]

ENDPOINTS_TOREMOVE is what grays out the tools, it doesn't remove them.

[dosubot[bot]]

You're right—according to the official documentation, ENDPOINTS_TOREMOVE disables the functionality but does not fully remove the tools from the UI; they may still appear but are grayed out for all users (docs). There isn't a built-in global setting to hide unavailable tools for everyone—only the per-browser "Hide unavailable tools" toggle, or by customizing the UI templates using the customFiles/templates override mechanism.

To reply, just mention @dosu.

---

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

   

[Frooodle]

Sorry please ignore the AI it's got a bit confused with the move to V2
Will provide the needed config for you later today !

DISABLE_ADDITIONAL_FEATURES=true is the flag
If it doesn't work I'll release a patch out either today or tomorrow

[vdl-dsi-architecture]

It works for the tools screen but the settings are still full of parameters that are not usable if login is disabled.

[Frooodle]

Gotcha I'll see what we can do

[vdl-dsi-architecture]

I see this mentioned in the 2.1.2 release notes (as Fix for admin ui showing for users (Although not usable)), but I couldn't pinpoint which commit it relates to and the settings are still full of unusable options.

[vdl-dsi-architecture]

I'd also like to retract my previous statement, the DISABLE_ADDITIONAL_FEATURES=true flag doesn't work, I had changed my settings locally using

If I start a fresh browser session, I still see all the unavailable tools :