Argon for OpenWrt LuCI: install the theme, then configure it
Argon is a clean and tidy OpenWrt LuCI theme that allows users to customize their login interface with images or videos. It also supports automatic and manual switching between light and dark modes.
At a glance
- What is it?
- Argon is a LuCI theme for OpenWrt and ImmortalWrt. It swaps the stock admin look for a cleaner layout, adds light and dark modes, and lets the login page use an image or video background. Here is what the repository actually documents, and where it stays quiet.
- Who is it for?
- Adopt Argon if you run a modern OpenWrt or ImmortalWrt build on the master branch and want a lighter admin interface with dark mode and a custom login background; the README gives both opkg and apk paths, so check which package manager your build uses before downloading. Skip it if you are on an older LuCI tree, since only the master branch is maintained now, or if you need a theme with a documented rollback procedure, because the README does not describe one.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 8 days ago.
- What is it written in?
- Mainly Less, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 25, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What Argon changes in the LuCI admin interface
LuCI is the web interface that ships with OpenWrt, and it is themeable. Argon replaces the default look with what the README calls a clean and tidy design, and it is aimed at people who administer a router through the browser often enough to care about how that interface reads. The repository topics line up with that audience: lede, luci, openwrt, theme.
The feature list is short and specific. Desktop and mobile layouts are both adapted. Light and dark modes can switch automatically or manually. Theme colors are customizable, with adjustable blur and transparency. The login page accepts a local image, a video, or an online wallpaper as its background. The last item is the one that gets quoted most often, and it is also the one that needs the companion app to be useful.
That companion is luci-app-argon-config, a separate repository listed under Related Projects and described as the configuration plugin for the Argon theme. The README says Argon works with it for a more complete theme configuration experience. Read that as a boundary: the theme package renders the interface, the config app is where the options live.
How the theme is packaged and wired into a build
The repository is not a standalone application. The top-level entries tell you what kind of project this is: htdocs/ for the web assets, less/ for the stylesheet sources, root/ for files that land in the device filesystem, ucode/ for the ucode components, and a Makefile that follows the standard OpenWrt package layout. The primary language is Less, which matches the stylesheet directory and means the CSS you eventually get is compiled from Less sources during the build.
The Makefile is short and worth reading before you file a bug. It pulls in $(TOPDIR)/rules.mk and $(TOPDIR)/feeds/luci/luci.mk, declares the package title as Argon Theme, and sets LUCI_DEPENDS to +USE_APK:wget-any +!USE_APK:wget +jsonfilter. That conditional syntax is the interesting part: depending on whether the target uses apk, the package pulls wget-any or plain wget, and in both cases jsonfilter. The version is pinned at 2.4.7 with PKG_RELEASE 20260824, and CONFIG_LUCI_CSSTIDY is emptied, which disables CSS tidying for this package.
The practical consequence is that Argon is a buildroot package first and a downloadable artifact second. Both routes exist, but the Makefile is the one the repository is organized around.
Installing luci-theme-argon from release packages
The README documents two install paths for release packages, one for opkg and one for apk, plus a build-from-source path. Start with the package manager your build uses, because the artifacts differ: an .ipk for opkg, an .apk for apk.
For opkg builds, the README gives this sequence. It downloads the theme and the config app at version 2.4.7 and installs both in one command:
wget https://github.com/jerrykuku/luci-theme-argon/releases/download/v2.4.7/luci-theme-argon_2.4.7-1_all.ipk
wget https://github.com/jerrykuku/luci-theme-argon/releases/download/v2.4.7/luci-app-argon-config_2.4.7-1_all.ipk
opkg install ./luci-theme-argon_2.4.7-1_all.ipk ./luci-app-argon-config_2.4.7-1_all.ipkFor apk builds, the filenames and the install command change. Note the --allow-untrusted flag, which the README includes as part of the command:
wget https://github.com/jerrykuku/luci-theme-argon/releases/download/v2.4.7/luci-theme-argon-2.4.7-r1.apk
wget https://github.com/jerrykuku/luci-theme-argon/releases/download/v2.4.7/luci-app-argon-config-2.4.7-r1.apk
apk add --allow-untrusted ./luci-theme-argon-2.4.7-r1.apk ./luci-app-argon-config-2.4.7-r1.apkIf you build your own image, the README's source route is to clone into the package directory, select the theme in menuconfig, and build:
cd openwrt/package
git clone https://github.com/jerrykuku/luci-theme-argon.git
make menuconfig #choose LUCI->Theme->Luci-theme-argon
make -j1 V=sThe README does not describe what to do after installation to select the theme in LuCI, and it does not document an uninstall or rollback step. Treat the first login after install as the point where you find out whether your build's LuCI version matches.
Where Argon stops being the right choice
The compatibility section is blunt: only the master branch is maintained now, and support is focused on modern LuCI environments based on Official OpenWrt and ImmortalWrt. If your router runs an older LuCI tree, or a vendor fork that diverged from it, the theme is outside its stated support surface. That is a bigger constraint than it looks, because themes touch layout templates, and a mismatch shows up as broken pages rather than a clean error.
The login background feature is the second place to be careful. The README says the login page supports local images, videos, and online wallpapers. A video background on a login page is served from the router itself, and the README gives no guidance on file size, format, or where the files should be placed. It also does not discuss what happens when an online wallpaper URL is unreachable. If your router has limited flash or a slow link, that is your problem to size, not something the documentation resolves.
Finally, the README does not document rollback. If a theme change leaves the interface unusable, the documented material gives you no recovery procedure. Anyone administering a remote router should weigh that before installing.
Argon against the other LuCI themes people compare it with
The related searches that bring people here name several alternatives, and the repository itself credits one of them. Under Credits, the README links luci-theme-material, and the search list includes both Luci-theme-material and Luci-theme spectra, along with Luci-theme-edge and Luci-theme-openwrt-2020. The README does not compare Argon to any of them, so the differences below come from what Argon's own documentation claims about itself.
The distinction is the login page. Argon's stated feature set centers on customizing the login interface with images or videos, plus automatic and manual light and dark switching. A theme that does not offer a media background on the login page is solving a different problem: it is restyling the admin pages and stopping there. If your reason for changing themes is the login screen, Argon is aimed directly at that. If your reason is density, table layout, or how configuration forms read on a small screen, the README makes no claims in that direction, and you should compare screenshots rather than feature lists.
The second difference is the companion app. Argon splits rendering from configuration: the theme package plus luci-app-argon-config. Some themes keep everything in one package. The split is convenient for updates, since the config app can move independently, but it also means an install that fetches only the theme gives you the appearance without the controls.
Maintenance, licence and the cost of keeping up
The repository is not archived, and the last push was on 2026-09-14. Releases are frequent: v2.4.5 on 2026-07-18, v2.4.6 on 2026-07-31, and v2.4.7 on 2026-08-24. The README points to RELEASE.md and RELEASE_ZH.md for the full version history, so the changelog lives in the repository rather than only in release notes.
Upgrade cost depends on how you installed it. If you built Argon into your image, you rebuild and reflash, and the Makefile pins PKG_VERSION 2.4.7 with PKG_RELEASE 20260824, so a version bump means editing the package or pulling a newer tree. If you installed the .ipk or .apk, you repeat the wget and install step with the new filenames. The README does not document an upgrade path that preserves settings, so whether your theme configuration survives is something to confirm on your own build.
The licence is Apache-2.0, stated in the LICENSE file and in the Makefile header, which reads "This is free software, licensed under the Apache License, Version 2.0 ." Apache-2.0 permits commercial use and modification and includes a patent grant, with the usual conditions around preserving notices and stating changes. It is a permissive licence, not a copyleft one, so redistributing a modified Argon inside a firmware image does not oblige you to publish the rest of the image. This is a description of the licence text, not legal advice; read LICENSE and, for a commercial product, involve counsel.
Editorial conclusion
Adopt Argon if you run a modern OpenWrt or ImmortalWrt build on the master branch and want a lighter admin interface with dark mode and a custom login background; the README gives both opkg and apk paths, so check which package manager your build uses before downloading. Skip it if you are on an older LuCI tree, since only the master branch is maintained now, or if you need a theme with a documented rollback procedure, because the README does not describe one. Verify first that your build's package manager matches the release artifacts you fetch, and that luci-app-argon-config is installed alongside the theme if you want anything beyond the default appearance.
Frequently asked questions
How do I install luci-theme-argon on OpenWrt?
Download the theme and the config app for your package manager and install both. For opkg the README uses wget to fetch luci-theme-argon_2.4.7-1_all.ipk and luci-app-argon-config_2.4.7-1_all.ipk, then opkg install on both files; for apk it fetches the -r1.apk artifacts and uses apk add --allow-untrusted.
What is LuCI on OpenWrt?
LuCI is the web interface that ships with OpenWrt, and it is themeable. Argon is one such theme, described in its README as a clean and tidy OpenWrt LuCI theme.
Is luci-theme-argon the best LuCI theme for OpenWrt?
The repository makes no such claim and does not compare itself with other themes. What it does state is its own feature set: desktop and mobile layouts, automatic or manual light and dark switching, customizable colors with blur and transparency, and login backgrounds using local images, videos or online wallpapers.
How do I change the theme in OpenWrt after installing luci-theme-argon?
The README does not document the post-install selection step. It covers the build-from-source route, where you pick the theme through make menuconfig under LUCI->Theme->Luci-theme-argon, and the package install route, but it stops before describing what to do in the LuCI interface afterwards.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/jerrykuku-luci-theme-argon)