Tools· Design & Creative

    Untitled UI

    React component library derived from the Untitled UI Figma design system, whose components install as editable source code instead of a package dependency, built on React Aria for accessibility.

    designingexecutableFreemium

    Description

    Strengths

    Ownership model instead of package dependency
    The CLI's add command copies a component's full, editable source code directly into the project, with no runtime dependency on an external package.
    React Aria as the accessibility foundation
    Keyboard, focus, and ARIA behavior are built in from the ground up through React Aria instead of added on afterward.
    Broad free foundation
    The MIT-licensed free tier already covers base components plus many application UI and marketing building blocks for commercial use.
    Next.js integration with dark mode
    A dedicated CLI route sets up routing and theme providers for Next.js in one step, including support for light and dark mode through CSS variables.
    Origin in an established Figma kit
    Design and code come from the same system, and according to the provider, Untitled UI counts more than 380,000 designers.

    Assessment

    AI features

    • AI-ready kits for Lovable and bolt.new Alongside classic framework integrations, Untitled UI, according to the provider, offers dedicated starter kits for the AI-driven page builders Lovable and bolt.new.

    Suitable for

    • Enterprise and SaaS teams that need accessible application UI such as dashboards, tables, forms, and auth flows with correct keyboard and focus behavior
    • Teams already working with the Untitled UI Figma kit who want to keep design and code in the same system
    • Projects that want to own the component source code directly in their own repository and adapt it freely, instead of importing a closed library
    • Less suitable for Less suitable for marketing sections with pronounced motion effects, since Untitled UI deliberately ships without a built-in animation library

    Limitations and notes

    • No motion out of the box Untitled UI deliberately ships without an animation library, so motion-heavy hero sections require an external solution.
    • PRO license needed for the full range Over 5,000 components and more than 250 page templates are license-gated, the free tier covers only part of the catalog.
    • No automatic version syncing in the project Because the code lives in the project instead of being managed through a package manager, improvements to the components do not make their way into existing projects on their own, and PRO content is additionally unlocked through a login command.
    • Overlap with other primitive libraries Anyone already using shadcn/ui in a project should pick one primitives source to avoid duplicate base components.
    • Client context needed for interactive components In Next.js with the App Router, components that use React Aria hooks need the "use client" directive, otherwise they do not work as expected on the server.

    Quick start

    1. Initialize a project through the CLI, for example npx untitledui@latest init --nextjs or --vite.
    2. Add a component, for example npx untitledui@latest add button, the source code lands directly in the project.
    3. For PRO components and page templates, log in through the CLI first to link the license.
    4. In Next.js projects, wire up the route and theme providers per the integration guide, for client-side routing and dark mode support.
    5. In existing projects, alternatively install the required packages manually, extend the Tailwind configuration, and add the utility functions.

    Tips

    • Do not forget the "use client" directive for interactive components using React Aria hooks in the Next.js App Router.
    • Before installing, check whether a component already exists through shadcn/ui or another primitives library in the project, to avoid duplicate base components.
    • Add a separate animation library for motion-heavy hero or marketing sections, Untitled UI deliberately does not ship one.
    • Check the PRO login status before larger builds, so license-gated page templates do not fail mid-build.

    Access

    Last reviewed: · Pricing, plans and features are a snapshot in time. Check the provider's own page before deciding.

    In the workshop this becomes your method.

    Whoever sees this process run once wants the agent behind it next. We build that in the workshop From Process to Agent.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call