How to disable mobile apps banner from the bottom?

I want to remove the bottom banner that has links to app stores.

1 Like




if one disables the DISPLAY_WELCOME_FOOTER -> the “previous conferences” box breaks in position then -> ends up on the bottom of the page, even partially leaving the screen on some browsers it seems

hmm is there a (hacky) workaround to make the footer empty instead?

@snek I can give you hacky :slightly_smiling_face:

Using Ansible, you can modify the CSS file inplace (won’t survive upgrade, but if you are lucky enough you’ll be able to re-apply after next upgrade without issues – test it before).

The task boils down to a simple replace, replacing CSS property for the footer by display: content (ie do not display content):

- name: Remove footer altogether
    path: /usr/share/jitsi-meet/css/all.css
    replace: >
      \1.welcome .welcome-footer{display:content}\3
    regexp: '^(.*)(\.welcome \.welcome\-footer\{background:.*)(\.welcome \.welcome\-footer\-centered\{.*)$'
    backup: yes

You can also add custom css, for example just put the following in plugin.head.html:

div.welcome-cards-container {
    padding-bottom: 180px;

And with DISPLAY_WELCOME_FOOTER disabled, the recent conferences box will go up around in the middle.

In order for this to survive upgrades, just copy this file in /etc/jitsi/meet/ and add a custom location for it in nginx:

location = /plugin.head.html {
    alias /etc/jitsi/meet/plugin.head.html;

Restart nginx to make this new location live.
And from then on edit the file /etc/jitsi/meet/plugin.head.html and it will take effect.
You can use this file there to put other custom CSS (and/or JS for that matter)

thanks @Kohl @yasen

footer is enabled in the config + using plugin.head.html to override css settings:

.welcome .welcome-footer {
    visibility: hidden;

Of course, this is also a way to do it - just have in mind that with “visibility: hidden” the code is still there, the links are still present in the html code of the page. It is just not being displayed by the browser, but stays in the code. If that’s not a problem for you - yes, this totally is a way to do it.