Skip to content

Take what you need.
Say where it came from.

All 694 components are free to use in anything — personal, commercial, closed-source, client work, a product you charge for. You do not need to ask, and you do not need to tell us. There is one thing asked in return.

  • Free forever
  • Commercial use
  • Closed source
  • Modify freely
  • No attribution in your UI

The one requirement

Credit syxUI somewhere a person can read it

One line. It does not have to be prominent, and it does not go in your interface or your marketing — just somewhere findable by someone who goes looking.

The whole obligation

UI components by syxUI — syxui.dev

Anywhere like this counts

  • An About or Credits screen
  • Settings › Acknowledgements
  • Your app's licences page
  • Your README
  • Your product's website

If your app genuinely has nowhere a person can read anything — a watch complication, a widget, a CLI — the comment at the top of the file is enough on its own.

Acknowledgements

Inter · SIL OFL

UI components by syxUIsyxui.dev

Sentry · MIT

One row among the others. That is all it needs to be.

Paste one of these

The usual reason a credit gets skipped is not knowing where to put it, so here it is as code.

Section("Acknowledgements") {
    Link(destination: URL(string: "https://syxui.dev")!) {
        Text("UI components by syxUI")
    }
}

Drop it into an existing Settings or About list. `Link` makes it tappable; plain `Text` is fine too.

The short version

Yes, freely

  • Ship it in a paid app
  • Ship it in closed source
  • Use it in client work
  • Change it however you like
  • Use one component or all 694

Not this

  • Repackaging a substantial part of the collection as its own UI kit, template pack or dataset — free or paid, renamed or not
  • Using the syxUI name or mark to suggest we endorsed or built your product

Copy components to build things. Don’t copy the collection to compete with it.

Questions people actually ask

Can I use these in an app I charge for?
Yes. Paid apps, subscriptions, enterprise software, client work — all fine, and you do not need to ask or tell us.
Do I have to open-source my app?
No. Closed source is fine. This is not a copyleft licence and nothing about your own code changes by using a component.
Does the credit have to be visible on screen?
No. It has to be findable by someone who goes looking — an acknowledgements list is the normal place. It does not belong on your home screen or in your marketing.
I changed the component a lot. Does it still apply?
Yes, if you started from ours. Modify it as much as you like — that is the point — but the credit still stands.
I only used one component.
One line of credit covers everything you take, whether that is one component or fifty. It never grows.
My app has no UI to put text in.
Then the comment at the top of the file is enough. Watch complications, widgets and CLIs are the cases this is written for.
Can I build a component library or template using these?
Not from a substantial part of the collection, no — that is the one thing the licence rules out, free or paid, renamed or not. Copy components to build things; don't copy the collection to compete with it. Using a handful inside a larger product you built is completely different, and fine.
Can I say my app is built with syxUI?
Yes — naming us as the source of components is exactly what the credit asks for. What you cannot do is imply we endorsed or built your product.

If an agent is doing the pasting

The Copy for AI button on every component page puts this requirement in the prompt, so the credit gets added while the agent is already editing your project rather than being left for you to remember. The MCP server returns the same instruction with every component it hands over.

Browse the components

This page is the plain-language version. The terms are syxUI Component License 1.0, in LICENSE at the root of the repository, and that file governs if the two ever disagree.

Not sure whether something is covered? Ask before assuming it isn’t — the answer is usually yes.