Tools· Design & Creative

    Watermelon UI

    Shadcn-compatible open source registry with more than 260 React 19 and Tailwind v4 components, ranging from single building blocks to complete dashboard and e-commerce sections, installed straight into your own source via the CLI.

    designingexecutableOpen Source

    Description

    Strengths

    Broad component inventory
    More than 260 building blocks according to the repository documentation, from primitives through blocks to complete dashboards, e-commerce sections, and auth flows, covering more ground than a plain collection of individual elements.
    Copy-paste architecture with full control
    Components are copied directly into your own source code instead of being pulled in as a runtime dependency, which keeps the complete code in your own repository and free to customize.
    Shadcn-compatible install path
    Individual building blocks can be pulled into the project through the familiar shadcn CLI and a dedicated registry namespace, or copied by hand through the "Code" tab of each component as an alternative.
    Fully typed throughout
    Every component is fully typed in TypeScript, with no need to add type definitions afterward.
    Open MIT license
    The registry's source code is released under the MIT license (LICENSE file in the repository), and commercial use is allowed without an attribution requirement.

    Assessment

    AI features

    • Full source code inside your own project Because components are installed as source files rather than as a package, the complete, unobscured code sits in your own repository, a basis on which AI coding assistants can read, adapt, and build further on components directly.
    • Registry protocol with machine-readable component metadata Every component is exposed as a JSON description on its own registry subdomain, a format that CLI tools and agentic install routines can read and process automatically.
    • Directly visible source code per component Every catalog entry shows the component's code through its own "Code" tab, which can be copied without the CLI, for example to hand it to an AI assistant directly as context.

    Suitable for

    • Projects on React 19 and Tailwind CSS v4 that need several connected sections quickly through the shadcn CLI, rather than assembling individual components
    • Teams that want full access to the component source code in their own repository instead of a black-box dependency through a package manager
    • Projects that need complete dashboards, e-commerce flows, or auth flows as a starting point instead of assembling them from individual primitives themselves
    • Less suitable for Less suitable for projects locked to React 18 or Tailwind CSS v3, where the technical foundation the provider requires is missing

    Limitations and notes

    • React 19 required Components use `use()` hooks and asynchronous server components; despite a differing statement in the project's own documentation, using it under React 18 does not work reliably in practice.
    • Tailwind CSS v4 required The components use Tailwind v4's new `@theme` block structure and color-token syntax, so projects on v3 need to translate their styles first.
    • Separate subdomains for catalog and registry The overview site sits at ui.watermelon.sh, the actual component registry at registry.watermelon.sh; the two URLs should not be confused during setup.
    • Inconsistent inventory figures The homepage advertises more than 600 components, while the GitHub repository documents around 260; it is worth checking the current catalog before deciding rather than relying on either figure.

    Quick start

    1. Browse the catalog at ui.watermelon.sh/components and pick the component or block you need.
    2. Initialize the project once with the preset code shown on the installation page.
    3. Add an individual component through the shadcn CLI and the component's registry URL.
    4. Import the component from your own components/ui folder and wire it into your application.
    5. If the shadcn configuration is missing, copy the source code manually through the component's "Code" tab instead.

    Tips

    • Check the current catalog before deciding rather than relying on the marketing figure of more than 600 components; the repository documents around 260.
    • Install Framer Motion once per project as a peer dependency before adding the first components.
    • After installing complete dashboards, check the bundle size, since many primitives get pulled in along with them.
    • When using it alongside other registries such as Cult UI or MagicUI, standardize on a single animation library to avoid duplicate dependencies.

    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