Lobe Theme for Stable Diffusion WebUI: What the Extension Actually Changes

The problem: Gradio's stock WebUI is functional but visually flat

AUTOMATIC1111 Stable Diffusion WebUI ships with a Gradio interface that is built for function, not for long sessions. Lobe Theme targets users who spend hours in that interface and want the surrounding chrome to be configurable. The README describes it as "a modern interface framework designed for Stable Diffusion WebUI" with a customizable UI and efficiency features. The audience is narrow and specific: people already running the AUTOMATIC1111 WebUI who are willing to add an extension that replaces the look of the front end. It is not a diffusion engine, not a model manager, and not a replacement for the WebUI itself. If you run a different front end, such as ComfyUI, this extension does not apply to you at all, because it is packaged as an extension for the AUTOMATIC1111 extension system.

How the extension works: a React bundle loaded by preload.py

The repository layout shows the split clearly. There is a preload.py at the top level, which is the hook the AUTOMATIC1111 extension loader looks for, and a javascript/ directory listed in package.json under "files", with "main": "javascript/main.js". The source lives in src/ and is TypeScript, built with Vite (vite.config.ts, and a build script of vite build). So the flow is: the WebUI loads the extension through preload.py, and the built JavaScript bundle takes over the presentation layer, while the Python side stays thin. The README's feature list confirms what that presentation layer adds: light and dark themes, a primary color choice from 13 schemes, 6 neutral gray levels, a logo that can be the default Lobe or Kitchen mark or a custom img url, base64 image, or emoji, and a customizable site title. The package.json also carries "sideEffects": false, which is a bundler hint for tree shaking rather than anything a user sees.

Installing Lobe Theme in Stable Diffusion WebUI

The README gives two installation paths. The first is the built-in extension market: open Stable Diffusion WebUI, go to the extension market, search for "Lobe Theme", and click install, then reload the UI. The second path, which the README marks as recommended, is a git clone into the extensions folder. Run it from the root directory of Stable Diffusion WebUI:

git clone "https://github.com/lobehub/sd-webui-lobe-theme" extensions/lobe-theme

After the clone finishes, the extension is in place and takes effect after the UI reloads. Before either path, the README states a minimum environment requirement of gradio-3.41.2 and sd-webui 1.6, so check those first. The README also carries a warning that Lobe Theme v3 is compatible with SD WebUI v1.6 and is not backwards compatible, and that versions below 1.6 should move to the legacy-sd-webui-1.5 branch. For a first real use, the theme switch is the fastest thing to verify. The README documents URL parameters for it:

http://localhost:7860/?__theme=light
http://localhost:7860/?__theme=dark

If the interface changes appearance when you load those URLs, the extension is loaded and the front end has taken over. To make dark mode the default instead of switching per session, the README shows a startup argument, `--theme=dark`, and a Windows example that appends it to webui-user.bat:

set COMMANDLINE_ARGS= --theme=dark

Everything beyond that, including the color schemes and the logo options, is reached through the gear icon in the upper right corner of the page.

Version coupling is the main limitation

The README's warning is the most important line in the document: v3 is tied to SD WebUI v1.6 and is not backwards compatible, and users below 1.6 are told to use the legacy-sd-webui-1.5 branch. That means the extension does not degrade gracefully across WebUI versions. It is a fork in the road, and you have to know which side you are on before you clone. This is a real constraint for anyone pinned to an older WebUI because of another extension that has not been updated. The second thing to weigh is release cadence against repository activity. The most recent releases listed are v3.5.4 on 2024-05-24, v3.5.3 on 2024-05-16, and v3.5.2 on 2024-05-15, yet the last push to the repository was on 2026-09-14. The release tags and the commit history are telling different stories, and the README does not explain the gap. If you need a tagged, versioned artifact to pin, the newest one you can name is v3.5.4. Finally, because the theme rewrites the interface layer, any other extension that injects its own controls into those panels is a compatibility question the README does not address. There is no documented rollback procedure either; removing an extension folder is the obvious move, but the README does not spell it out.

Alternatives: Kitchen Theme and the ecosystem around it

The package.json keywords include sd-webui-kitchen-theme and kitchen-theme, which points at the theme this project grew out of, and the README's logo options still offer a Kitchen mark alongside the Lobe one. The difference in approach is packaging and scope: Lobe Theme is a React and TypeScript front end built with Vite and distributed as a WebUI extension, rather than a stylesheet layered over Gradio's own markup. That choice is what makes the color schemes, neutral levels and logo substitution possible, and it is also what creates the version coupling described above. If your goal is only a darker interface, a CSS-level theme carries far less risk of colliding with other extensions. If your goal is a configurable front end with its own component layer, Lobe Theme is the more ambitious option and accepts the tighter version requirement in exchange. The related searches around this project also name Segment Anything, Openpose Editor, Regional Prompter, Additional Networks and Dynamic Prompts, but those are separate extensions with separate purposes, not substitutes for a theme.

Licence and the cost of staying current

The licence is AGPL-3.0, identified in package.json as "AGPL3" and in the repository as AGPL-3.0. For someone installing the extension into their own WebUI, that is the ordinary case of running the software. The obligation becomes worth reading carefully if you fork the code, ship a modified build, or expose it as a network service, because AGPL-3.0 attaches source-availability conditions in those situations. This is a description of the licence, not legal advice; read the LICENSE file in the repository and talk to counsel if you plan to redistribute. On upgrade cost, the practical burden is the version gate rather than the code volume. Upgrading the WebUI past 1.6 is what keeps you on the v3 line; staying below it means tracking the legacy-sd-webui-1.5 branch, which is a separate line of development. The repository also carries a full toolchain for contributors (eslint, stylelint, prettier, vitest, husky, semantic-release, and a lobe-i18n script for locales), which raises the bar for anyone who wants to send a patch.

Editorial conclusion

Adopt Lobe Theme if you run AUTOMATIC1111 Stable Diffusion WebUI 1.6 or newer and want a restyled, React-based front end with light and dark modes and color customization. Do not adopt it on WebUI 1.5 or older, where the README points to the legacy-sd-webui-1.5 branch instead, and do not treat the v3.5.4 release of 2024-05-24 as the state of the code: the repository's last push was on 2026-09-14. Before installing, confirm your gradio version is at least 3.41.2, because the README states that as a minimum requirement, and check whether any other extensions you rely on inject their own UI into the panels the theme rewrites.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. lobehub/sd-webui-lobe-theme on GitHub
3. Project website
4. README
5. Releases