Molveau
All guides

Design resources3 min read

13 sites for React components and design inspiration

Where I get component code I can ship, whole-site and single-block references, motion ideas and real product screens. Thirteen sites, filed by need.

When a client needs a pricing page, I open Saaspo. When I need a navbar, I open Navbar Gallery. Here are thirteen sites with screenshots, each filed under the need it answers. Check the license on any code you paste, and take the principle, never the pixels, from anything you only look at.

Component code you can ship

shadcn/ui (ui.shadcn.com): the baseline. Copy-in components on accessible Radix primitives, so you own the code the moment it enters your repo. Everything else in this section assumes it.

shadcn/ui homepage

React Bits (reactbits.dev): animated and creative components such as text effects, backgrounds and interactive cards. The license is MIT with Commons Clause: free in client work, but you cannot resell the components themselves. Two of them ship on this site, adapted to our tokens.

React Bits homepage

blocks.so (blocks.so): free copy-paste application blocks on shadcn conventions, including forms, auth screens, tables and sidebars. My first stop when an app screen needs to exist by tonight.

blocks.so homepage

21st.dev (21st.dev): a searchable community registry of shadcn-style components, with AI generation on top. Search it before you hand-write anything novel, because someone has probably built the widget.

21st.dev homepage

Kibo UI (kibo-ui.com): the heavy components, like Gantt charts, Kanban boards, editors and advanced tables. Free, and installable through the shadcn CLI. You should almost never build these from scratch.

Kibo UI homepage

SmoothUI (smoothui.dev): Motion-based animated components and micro-interactions, compatible with the shadcn registry. I open it when a screen works but feels static.

SmoothUI homepage

Whole-site inspiration

Landing Love (landing.love): thousands of landing pages recorded as full-page video, filterable by GSAP, WebGL and Three.js. The video is the reason to use it, since motion is what a static screenshot misrepresents.

Landing Love homepage

Saaspo (saaspo.com): SaaS web design, filterable by page type. When a client needs a pricing page, I study ten strong pricing pages rather than ten strong homepages.

Saaspo homepage

Single-block galleries

Navbar Gallery (navbar.gallery): navigation only, from sticky bars to mega menus and sidebars. Every site needs this block, and most get it wrong.

Navbar Gallery homepage

CTA Gallery (cta.gallery): calls to action, signup blocks and newsletter boxes, sorted by industry. Visitors see it last, right before they decide.

CTA Gallery homepage

Motion and detail

60fps.design (60fps.design): a feed of interface motion worth copying the timing from: durations, easings and choreography.

60fps.design homepage

Design Spells (designspells.com): single details such as easter eggs, transitions and empty states, each with a note on why it works. Use it to find the one touch an interface is missing.

Design Spells homepage

Real product UI

Refero (refero.design): screens from shipped products, filterable by page type, flow and UX pattern. Marketing galleries show what wins awards. Refero shows the settings, onboarding and billing pages users spend their time in.

Refero homepage

How to use a list like this

  1. Go in with one question: a navbar, a pricing table, an empty state. Browsing without a question is entertainment.
  2. Collect three examples, then write one sentence about what they share. That sentence is the principle you can reuse; the screenshots were only evidence.
  3. Close the tab before you build. With a reference open, inspiration turns into copying, and a copied design always fits the original's content better than yours.

For icons, fonts, photos and 3D assets, the companion guide on free design assets lists the license-checked sources.

Stanislas Molveau

Founder, Molveau Studio

I design and build web and mobile products, and write these guides from teardowns of real apps rather than theory.

LinkedInSee my work