A free, MIT-licensed admin dashboard template. It's a set of HTML, CSS, and JavaScript files built on top of Bootstrap 5.3 — not a framework, not an npm component library. You drop it into your project, modify the markup to suit your app, and ship.

No. The Getting Started guide shows the CDN-only approach — copy four <link> tags and four <script> tags into your HTML and you're done. The npm-based workflow is there if you want to customise SCSS variables or tree-shake the JavaScript.

Bootstrap 5.3.x. The current package.json pins 5.3.8 — older 5.3 minors should work but aren't tested. Bootstrap 5.0 / 5.1 / 5.2 will not work (the color-mode and data-bs-theme system landed in 5.3).

You don't need jQuery — AdminLTE 4's JavaScript is vanilla. If your existing app already uses jQuery, it'll coexist fine. But none of AdminLTE 4's own plugins call into jQuery, and there are no $.fn.xxx() plugin shims.

The v3 plugins/ folder is gone too. Every widget it bundled has a vanilla-JS successor — see the plugin replacement table for the full mapping (Select2 → Tom Select, DataTables → Tabulator, Summernote → Quill, and so on).

AdminLTE 4 recommends Tom Select instead. It covers everything people reach for Select2 to do — searchable dropdowns, multi-select, tagging, clearable selections, AJAX-backed options, virtual scrolling over large datasets, keyboard navigation — in roughly 20 kB gzip, against Select2's ~50 kB once jQuery is counted. forms/advanced.html demos all of it, including a paginated remote-data field with request cancellation, and there's a line-by-line API mapping if you're porting existing code.

Select2 itself is still maintained (4.1.0 shipped in 2026), but it is still a jQuery plugin — its UMD wrapper hard-requires jQuery and there is no jQuery-free build. Bundling it would put jQuery back into a framework whose entire v4 premise is not needing it, and none of the official Vue/React/Django/Laravel ports could consume it.

If you're locked into Select2 anyway, AdminLTE ships an optional styling-only compatibility sheet — see Select2 compatibility theme. You bring the plugin; it makes Select2 match Bootstrap 5.3, dark mode and modals included. No jQuery is added to AdminLTE.

Yes — it's just HTML/CSS/JS. The typical path is to build a custom WordPress theme that wraps AdminLTE's markup around wp_head(), wp_footer(), and WordPress's loops. AdminLTE doesn't ship a WordPress-specific build; the work of porting nav-walker classes and authentication forms is yours.

All workable. AdminLTE is a server-rendered template — copy the demo pages into your views/templates, replace static content with your framework's template variables, and wire up routes/auth as usual. Community Composer/Packagist packages exist for Laravel and Symfony, though they typically lag the upstream version — verify they ship v4 before you depend on them.

Workable but less natural. AdminLTE's JavaScript plugins use DOM lifecycle hooks (DOMContentLoaded, MutationObserver patterns) which fight with framework reconciliation. If you're using a SPA framework, consider:

• Using AdminLTE only for CSS — keep the visual style, but write your own React/Vue components for the interactive parts.
• Or pick a component library built for your framework (PrimeReact, Vuetify, etc.).

We don't recommend wrapping AdminLTE's jQuery-era plugins in SPA framework components — it's a maintenance burden that outweighs the visual win.

Override --bs-primary (and its RGB counterpart) on :root:

:root {
  --bs-primary: #6610f2;
  --bs-primary-rgb: 102, 16, 242;
}

For deeper control (sidebar width, breakpoints, spacing scale), see Customization & Theming.

AdminLTE deliberately doesn't bundle these — they'd bloat the framework. The Recommended Integrations page lists best-in-class third-party libraries (Flatpickr, Tom Select, Quill, etc.) with copy-paste install snippets.

Yes. Bootstrap Icons is the default in the demos because it's MIT, ships with Bootstrap, and is SVG-based — but nothing in AdminLTE's CSS or JS requires it. Drop in FontAwesome's stylesheet and replace <i class="bi bi-x"> with <i class="fas fa-x"> throughout.

Watch the GitHub repo (Releases-only mode) or subscribe to the RSS feed at https://github.com/ColorlibHQ/AdminLTE/releases.atom.

Still online at adminlte.io/docs/3.2 and earlier versions are linked there. The v3 branch on GitHub continues to receive critical bug fixes; new features land in v4 only.

See the dedicated Migration from v3 guide. The short version: class names changed (.wrapper → .app-wrapper), data-toggle → data-bs-toggle, dark mode uses data-bs-theme instead of .dark-mode, and jQuery isn't required anymore.

Yes — MIT licensed. You can use it in commercial products, SaaS apps, client work, anything. The only requirement is preserving the copyright notice in the source files (adminlte.css / adminlte.js). You don't need to display attribution in the UI.

No. The MIT license requires you to keep the licence notice in the source files you distribute — that's it. You don't have to mention AdminLTE in the rendered UI, your About page, or your README.

Yes. The MIT license explicitly permits this. You can also resell modified versions of AdminLTE itself (theme marketplaces frequently do this) — just preserve the original copyright notice.

Check that the PushMenu plugin is loaded. It's bundled into adminlte.js — make sure the script tag is on the page and after the markup it operates on. Also verify your hamburger button has data-lte-toggle="sidebar" (not data-widget="pushmenu", which is the v3 attribute).

The included Color Mode toggle writes to localStorage under the key lte-theme. If you're using a different toggle implementation, make sure it both sets document.documentElement.setAttribute('data-bs-theme', ...) and writes to localStorage on change.

Turn the bundled switcher off with <html data-lte-color-mode="off">. ColorMode then never writes data-bs-theme — not on load, not on a toggle click, not when the OS preference changes — so your own switcher (or a custom Bootstrap theme name) stays in control. If you only need a server-rendered default instead, render data-bs-theme on <html> and it is respected as long as the visitor hasn't picked a theme themselves. See Color Mode.

Fixed in v4.0.0 (#5993). If you're still seeing this, you're on an older RC — update to the latest.

Put your overrides before the @import of AdminLTE's SCSS. AdminLTE uses !default on its variables, which means the first declaration wins. See Customization & Theming for the import order.

We use an npm overrides block in package.json to keep peers happy — make sure you're on npm 8.3+ which respects them. If you're on an older npm, install with --legacy-peer-deps.