A UI kit that looks flawless in a preview image can be unusable the moment you open it. The screenshots are rendered from the designer's machine with their fonts installed, their plugins active, and only the three screens they bothered to finish. This guide is about telling the difference before your money moves.
What You Are Actually Buying
"UI/UX design assets" covers five quite different products, and conflating them causes most disputes.
A UI kit is a collection of components — buttons, inputs, cards, navigation — usually in one design file. You assemble screens yourself.
A design system is a UI kit plus rules: named colour tokens, a type scale, spacing units, component states, and documentation explaining when to use what. It is a system because changing one token updates everything downstream.
A template is finished screens for a specific product — a dashboard, a checkout flow, a landing page. Less flexible than a kit, far faster to ship.
Coded components are React, Vue, or plain HTML implementations. This is a different product from a design file, and buyers routinely assume one includes the other. It usually does not.
A custom design engagement is a designer's time producing something new for you.
The Checks That Actually Catch Problems
Open the file before you confirm anything. Most disputes would not exist if the buyer had opened the file first. It takes two minutes.
Count the screens against the listing. "150+ components" often counts every icon and every colour swatch individually. Count the things you would actually use.
Check the layer structure. Well-built files use components or symbols, named layers, and auto-layout. Badly built files are flattened rectangles that look identical in a preview and are impossible to modify. This is the single biggest quality difference and it is invisible in screenshots.
Look for real component states. A button in default state only is half a component. You need hover, active, focus, and disabled — and focus in particular, because it is the one everyone skips and the one accessibility depends on.
Verify responsive variants exist. Ask for the mobile artboards specifically. Desktop-only kits are common and rarely disclosed.
Test dark mode properly. A dark variant built by inverting colours produces unreadable text and muddy shadows. Check that dark mode is a designed theme with its own token values, not a filter.
Check the fonts. If the kit uses a licensed font you do not own, you cannot use the file as designed. Google Fonts is safe; anything from a foundry is a separate purchase you will have to make.
Read the licence before anything else. Personal-use-only kits cannot be used in client work. Some licences forbid use in products that are themselves sold. This is where the expensive mistakes live.
Realistic Pricing
- UI kit: $30 to $200
- Full design system with documentation: $200 to $1,000
- Figma template (single product): $20 to $150
- Coded component library: $100 to $800
- Custom UI design: $500 to $3,000
A $500 "design system" that is really a kit with no documentation and no tokens is the commonest overpriced listing in this category.
Selling Design Assets Well
Show the layer panel. One screenshot of a clean, named, componentised layer structure does more for a serious buyer than ten pretty renders.
State the format and version. "Figma" is not enough — say whether it uses variables, auto-layout, and which features require a paid plan.
List what is not included. Fonts, icons under a separate licence, and stock photography are the three that cause disputes.
Provide a free sample. One real component, downloadable. Buyers who can inspect quality convert at a much higher rate.
Verifying Under Escrow
Escrow only helps if you use the verification window. On Escrozon, funds are held in escrow while you check the delivery, so before you confirm:
- Open every file in the software it was authored in.
- Check the component count and screen count against the listing.
- Modify one component and confirm the change propagates as a system should.
- Confirm the licence text matches what the listing promised.
- Export one asset to make sure nothing is locked or missing.
Only then confirm. If files are missing, corrupted, or the licence is narrower than advertised, open a dispute with the file open in front of you and screenshots ready.
Frequently Asked Questions
Do I get the source file or just exports?
Ask explicitly. Some sellers deliver PNG or PDF exports, which are close to worthless for design work. You want the editable source: .fig, .sketch, or .xd.
Can I use a UI kit in a client project? Depends entirely on the licence. Many kits allow unlimited client work; some restrict you to a single end product; a few prohibit client work altogether. Never assume.
What if the kit uses plugins I do not have? Some Figma files depend on plugins for icons or data. Without the plugin, layers may render as placeholders. Ask before buying whether the file has plugin dependencies.
Is a design system worth five times a UI kit? If you are shipping one project, no. If you are building a product that will grow, yes — the value is in the tokens and rules that keep fifty screens consistent, not in the components themselves.
How do I spot a resold free kit? Reverse-image-search a component screenshot, and search the exact kit name plus "free". Reselling freely licensed assets as original work is the most common fraud in this category, and it is grounds for a dispute.
