On this page
The part of a kit that is not the seller's to sell
A Figma UI kit is a bundle of other people's work as much as the seller's. The frames, components and variables are theirs. The typeface rendering your dashboard UI kit headings usually is not. Neither is the photography in the hero mockups, the icon glyphs lifted from a free pack, or the illustration set pulled from a stock library.
When you buy, you are not just buying files. You are buying the seller's right to pass those files on to you. That right is narrower than most buyers assume, and it is the single most common source of trouble in this category.
What sellers must own, and what they must say
Original design work is the baseline. Everything the seller did not draw or build themselves has to be either licensed for redistribution or left out of the download entirely.
In practice that splits into three buckets:
- Fonts. Free and open-source typefaces are fine. So are commercial fonts, but only if the seller's licence explicitly permits redistribution inside a product — most desktop and web font licences do not. If a premium typeface appears in the mockups, the seller has to say so in the listing, and you will need your own licence to use it.
- Imagery. Stock photography, illustration and 3D assets must be disclosed. Many stock licences prohibit redistribution as part of a template, which means a kit showing licensed photos may be showing you something you cannot legally reuse.
- Components and icons. Third-party icon packs, charting libraries and plugin-generated elements carry their own terms. A component library built on someone else's icon set inherits that set's restrictions.
AI-generated work is a disclosure point too. If any part of the kit was produced with generative tools, the listing should say so — partly because provenance affects what the seller can warrant, and partly because some buyers cannot use it.
A short, honest listing does more for a seller than a long one. Buyers who discover an undisclosed font licence after purchase do not come back.
Variables, auto-layout and components
This is where a kit earns its price or does not.
A kit built with Figma variables, auto-layout and proper variants adapts to your brand in minutes. Change a colour token, swap a type scale, and the whole file follows. Components stay responsive because the constraints are structural, not painted on.
Static frames only look similar. They are pictures of an interface. To make them useful you rebuild the layout, re-link the spacing, and re-create every state by hand. That is not a small job, and it is invisible in a screenshot.
The listing states which one you are getting. Look for component count, whether variants exist, and whether variables are used. If the listing is vague on those three points, treat the kit as static until proven otherwise.
Reading a listing properly
Check the tool first: mostly Figma, plus Sketch, Adobe XD and Penpot. Then check structure. A wireframe kit with 200 components and no auto-layout is a library of shapes. A design system with 40 components, published variables and documented states is a working foundation.
Fonts and imagery inside the kit
Assume nothing is included until the listing says it is.
Demo images, icons and fonts are rarely bundled with the download — often for licensing reasons, occasionally because the seller did not think about it. A mobile app UI kit can look complete in the preview and arrive as grey placeholder rectangles.
Two things worth confirming before you pay:
- Which fonts the kit actually uses, and whether they ship with it.
- Whether any imagery is included, and under what terms.
If a premium typeface is shown in the screenshots, the seller must say so. You then need your own licence for it, which is a real cost on top of the kit price. Font licences are narrow and scope-specific — a desktop licence does not cover an app, a web licence does not cover print, and neither covers redistribution.
Dark mode and accessibility
Dark mode is a common checkbox and a less common reality.
Ask whether dark mode is a real token set or a separate file. A genuine implementation uses the same components with swapped variable values, so both themes stay in sync when you edit. A separate dark file is a duplicate you now maintain twice.
Colour contrast matters as much. Serious kits document whether their palettes meet accessibility guidance, and which combinations pass. Kits that do not mention it usually have not tested it.
For a dashboard UI kit or a mobile app UI kit heading into production, these two questions separate a file you can ship from a file you have to audit.
What you inherit, and what you do not
The default licence on Attesar is commercial. That covers client work and internal projects. It does not cover reselling the kit, republishing it as your own, or redistributing the source files.
What you inherit is the seller's rights as they stand — no more. If a font was licensed for the seller's use only, you inherit nothing for that font. If imagery was included under a limited stock licence, your use is limited the same way.
This is why disclosure matters more than polish. A kit with plain open-source fonts, no stock imagery and a clear licence note is safer to build on than a beautiful file with three undisclosed dependencies.
Browsing UI Kits & Design Systems with these questions in hand takes ten minutes and saves a rebuild. The category covers Figma UI kits, design systems, design system documentation kits, wireframe kits, dashboard and mobile app UI kits, mobile game UI kits, icon sets, chart and data-viz kits, and component libraries built on Figma variables — and the licensing position differs across all of them.
Questions buyers ask
Which tools are supported?
Mostly Figma, plus Sketch, Adobe XD and Penpot. Each listing states the tool, the component count, and whether auto-layout and variables are used. If those details are missing, ask before buying rather than after.
Can I use a kit in client work?
Yes, under the commercial licence. You cannot resell the kit, republish it as your own, or hand the source files to a third party. Client deliverables built with the kit are fine; the kit itself is not a deliverable.
Are the fonts included?
Sellers must use free fonts or include them in the download. If a premium font appears in the mockups, the listing says so, and you will need your own licence for it. Never assume the typeface in the preview ships with the file.
How is a kit delivered?
As a downloadable file or a Figma community or duplicate link, unlocked once your payment is protected. Check which before purchase — a duplicate link gives you a working file, a download may give you an archive you import yourself.
If you are weighing up a purchase, start from the UI Kits & Design Systems listings and read the licence note first.