How to Hide Grafana Version from the Login Page in Grafana OSS v13.1.0?

Grafana Dashboards
1

Hello Grafana Team,

I am using Grafana OSS v13.1.0 (b309c9bb3b) and am trying to completely white-label the login page for our internal deployment.

I have successfully customized several UI elements, including:

  • Login logo
  • Application name
  • “Forgot your password?” text
  • “New to Grafana?” text
  • Other login page branding

However, I am unable to remove or hide the version string displayed at the bottom of the login page:

Grafana v13.1.0 (b309c9bb3b)

I searched through the compiled JavaScript files under:

/usr/share/grafana/public/build

and inspected files such as:

LoginPage.234487fe7c10165b9dfd.js
LoginPage-react19.a44e40f1dee1a9eadea9.js

I also searched for keywords like:

Grafana
13.1.0
buildInfo
b309c9bb3b

but could not identify where this version information is rendered.

Could someone please advise:

  1. Which source file or React component renders the login page version?
  2. Is there a supported way to hide it in Grafana OSS?
  3. If not, what is the recommended approach for a fully white-labeled installation?

Any guidance would be greatly appreciated.

Thank you!

Best regards,

Kaushal Shriyan

2

LoginPage.tsx itself doesn’t render a footer → it only renders LoginForm, LoginServiceButtons, UserSignup, etc., wrapped inside LoginLayout.

The version string comes from a layout/wrapper component, not from LoginPage.tsx directly → which is why your grep of LoginPage*.js came up empty. I haven’t confirmed the exact wrapper file (likely LoginLayout.tsx or Page.tsx), so I won’t go further than that.

Supported OSS way to hide it: No.
hide_edition (removes the Grafana edition from the footer) is documented as Enterprise-only. [auth.anonymous] hide_version = true exists, but per the docs it only hides the version “for unauthenticated users” → it doesn’t apply to a standard login page.

Recommended approach: There’s no supported OSS path. For a real fix, Grafana Enterprise’s [white_labeling] block is the only officially supported, upgrade-safe option:

If Enterprise isn’t an option, the only alternatives are unofficial workarounds (reverse-proxy string substitution, or patching compiled assets) → both fragile, both liable to break on upgrades, and neither recommended by Grafana.