SUPPORT/FREQUENTLY ASKED

Questions & answers.

Everything you need to know about DuneUI. Need something specific? Reach out on X / Twitter.

01

General

DuneUI is a free, open-source library of UI components and page sections built with TailwindCSS v4 and pure CSS. Designed to help you ship distinct interfaces faster — no account required, no lock-in.

Yes. Every component is free for personal and commercial projects. No payment, no attribution needed.

No. All components are accessible directly from the website. Just browse, inspect at any viewport, and copy the code.

Developers and designers who want production-ready UI blocks without generic bloat. Whether you are building a SaaS, a studio site, or a personal archive — DuneUI gives you solid architectural primitives.

02

Components

Components are written in semantic HTML + TailwindCSS v4 (plus pure CSS options), making them compatible with React, Vue, Svelte, Astro, Next.js, and vanilla HTML.

Absolutely. Components are a starting point, not a constraint. Modify tokens, spacing, layout, and typography however you want.

We follow accessibility best practices including semantic HTML, ARIA attributes, and keyboard navigation across interactive primitives.

As of v2.0, DuneUI is built for TailwindCSS v4 alongside standalone Pure CSS specimens.

03

License & Usage

Yes. Use any component in commercial projects — SaaS apps, client websites, e-commerce stores, and more.

No. You cannot package DuneUI components into a competing UI kit or component package and distribute it publicly, whether for free or for sale.

Attribution is not required. A mention is always appreciated and helps the project grow, but it is entirely optional.

04

Technical

No. DuneUI is copy-paste based. Set up TailwindCSS v4 (or drop in our Pure CSS blocks) and paste the markup directly.

DuneUI pairs Instrument Serif, Urbanist, Albert Sans, and JetBrains Mono via @fontsource. You can swap them for your own font tokens anytime.

STILL STUCK?

Ask directly on X / Twitter

Have a question about integration, licensing, or upcoming components?

Message @FabianHermar