Square UI: shadcn/ui admin dashboard templates you clone instead of compose

What Square UI actually ships, and who it is for

Square UI is a collection of free, open-source admin dashboard templates for shadcn/ui. The README describes each one as a complete starting point you can clone, copy, and ship, and the live catalog sits at square.lndevui.com. The templates cover dashboards, email, chat, calendars, file managers and more, with named entries including Habit Tracker, Marketing Dashboard, Dashboard 5, Rentals, Bookmarks, Maps, Files, Dashboard 4, Leads, Dashboard 3, Dashboard 2 and Employees.

The audience is narrow and specific. This is for a developer who has already chosen Next.js, Tailwind CSS and shadcn/ui, and who wants a finished screen rather than a set of primitives to assemble. If you are starting from an empty app and have not picked a styling approach, Square UI does not help you decide; it assumes the decision is made. The README gives no installation command, no npm package name and no CLI, which tells you the intended workflow is copying files out of a template directory, not adding a dependency.

That distinction matters more than it sounds. A component library is installed, versioned and upgraded. A template is forked, edited and then belongs to you. Square UI sits firmly in the second category, and every trade-off in this review follows from that.

Radix UI and Base UI: the two-directory layout is the real architecture

The most concrete structural fact in the repository is that every template exists twice. The README states plainly that templates using Radix UI are located in templates/, while templates using Base UI are in templates-baseui/. The top-level repository entries confirm this: the tree contains home/, templates/ and templates-baseui/ alongside README.md, LICENSE.md and .gitignore.

So the architecture is not a shared package with a swappable primitive layer. It is two parallel copies of the same layouts, one per primitive library, kept in step by hand. Each template is a standalone Next.js app with its own routes, its own Tailwind configuration and its own shadcn/ui components vendored in. Nothing in the README suggests a shared workspace, a common package, or a build step that reconciles the two trees.

For an adopter this is mostly good news. You pick a tree, you get a self-contained app, and you never inherit a dependency on Square UI itself. It also means the two trees can drift: a fix applied to templates/dashboard-5 has no mechanism in the repository layout that would carry it to templates-baseui/dashboard-5. If you plan to follow upstream changes, decide early which tree you are tracking, because you are effectively tracking a directory, not a release.

The Base UI variants also give you a genuine escape hatch. If your organisation has standardised on Base UI rather than Radix, you are not rewriting the interaction layer by hand. That is unusual for template collections, and it is the strongest argument for choosing Square UI over a single-primitive alternative.

Getting a template running locally

The README does not give install steps, so the following follows the repository layout rather than a documented procedure: the templates live in subdirectories of templates/ or templates-baseui/, and each is a Next.js app. Clone the repository first.

git clone https://github.com/zerostaticthemes/square-ui.git
cd square-ui

Then pick a template directory. The README's table links each template under both trees, for example templates/dashboard-5 and templates-baseui/dashboard-5. Change into the one you want.

cd templates/dashboard-5

From there the app is a standard Next.js project, so the usual dependency install and dev server apply. The README does not name a package manager or a script, so expect to read package.json in the template directory to confirm the exact script names before running anything.

npm install
npm run dev

What you should see is the template's dashboard rendering locally. If the dev script differs, package.json in that directory is the authority, not this article. The live demos listed in the README, such as square-ui-dashboard-5.vercel.app, are the fastest way to check what a template looks like before you clone it.

The limitation: no releases, no documented licence, no upgrade path

Three things are missing, and each one is a real cost.

First, no releases are published. The repository has no tagged versions, so there is nothing to pin and nothing to diff against. If you copy a template into your product and later want the upstream improvements, you are comparing directories by hand. This is the standard failure mode of template collections, and Square UI does not mitigate it.

Second, the licence is unresolved. The repository metadata reports the licence as NOASSERTION, and the README does not state terms for the free collection. A LICENSE.md file exists at the repository root, and that file is the only place to look. Do not assume the free templates carry the same terms as the paid Shadcn Dashboard collection, which the README describes as commercial licence; they are separate products and the README treats them separately.

Third, the README is a catalog, not documentation. It tells you what each template contains and where it lives. It does not document the component structure, the data layer, or how the charts are wired. Any template you adopt has to be read as source. For a one-off admin screen that is fine. For a team expecting upgrade notes and a changelog, it is not.

One more boundary worth stating: Square UI is not a component library. If your need is a versioned set of accessible primitives with documented props, shadcn/ui itself is the thing you want, and Square UI is a consumer of it, not a replacement.

Square UI against a single-primitive template collection

The obvious alternative is a shadcn/ui admin template that ships only a Radix variant, of which there are many. The difference is not quality, it is lock-in at the primitive layer.

A single-primitive template ties your dashboard's dialogs, dropdowns, popovers and menus to one underlying library. If your design system later standardises elsewhere, or if a primitive library changes its API in a way you cannot absorb, you are rewriting interaction code across every screen. Square UI's dual tree means the same layout exists against both Radix UI and Base UI, so the migration is a directory swap plus your own customisations, not a rewrite.

That is a real difference in approach, but it is not free. Maintaining two trees doubles the surface area, and as noted the repository layout provides no mechanism to keep them in sync. You are trading a migration risk for a drift risk. Which one is worse depends on how long you expect the product to live and how much you intend to customise. A short-lived internal tool should take the single tree and move on. A product you expect to maintain for years, with a design system that may change, gets more from the dual tree.

Maintenance, cost and licence implications

The repository is not archived, and the last push was on 2026-09-15, which is recent. That tells you the collection is still being touched. It does not tell you anything about support commitments, and the README makes none: no issue triage policy, no contribution guide, no release cadence.

Upgrade cost is the number to think about. With no tagged releases, adopting a template means the copy in your repository is the source of truth from that moment. Upstream fixes do not reach you automatically. Budget for reading the diff yourself if you want them, and expect that diff to grow the more you customise.

On licence, the honest position is that the terms are not resolved by the README. The metadata says NOASSERTION, the README is silent, and LICENSE.md at the repository root is the file to read before you ship anything. Note also that the README promotes a separate paid collection, Shadcn Dashboard, described as having 20+ more premium shadcn admin templates with a commercial licence, full pages and lifetime updates. Free and paid are distinct offerings with distinct terms, and nothing in the README suggests the paid terms apply to the free templates or the reverse. This is not legal advice; read the licence file and, if the terms affect a commercial product, get it reviewed.

Editorial conclusion

Square UI is worth adopting if you need a working admin shell this week and are willing to read the source of a single template rather than learn a framework. It is the wrong choice if you need a maintained component library with versioned releases, documented upgrade paths, or a component set that is not shadcn/ui. Before committing, open the template directory you want, check whether it sits under templates/ or templates-baseui/, and read LICENSE.md at the repository root, because the README does not state licence terms for the collection and no releases are published.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. zerostaticthemes/square-ui on GitHub