Unity Assets & Plugins at a glance
- 40 active listings
- Paid listings: half cost between $4.99 and $21.99, median $13.99
- 15 free listings
- Most common file formats: RAR, BLEND, FBX
- 5% of listings declare a licence that allows commercial use
- Newest listing added Nov 3, 2026
Measured from the live listings on Getly and updated daily.
If you want to know how to sell Unity assets outside the Asset Store, the short answer is: export a clean .unitypackage, say which Unity version and render pipeline it supports, ship a demo scene, and list it on a marketplace that checks the package before buyers see it. On Getly you can publish from inside the Unity editor with a free tool, every new listing is reviewed by hand (usually within a few hours), you keep 80-90% of each sale, and payouts go out in USDT or USDC on the 1st and 15th. This guide walks through each step, with numbers from our own Unity shelf.
What the Unity shelf on Getly looks like
We measured the Unity assets category on 6 November 2026. It holds 38 listings, so it is a small shelf: a new, well-made asset does not have to fight hundreds of near-copies for attention. 36.8% of the listings are free. Prices on the shelf have a median of $14.47, and the middle half sits between $4.99 and $21.99.
One number stands out: 94.7% of the Unity listings state no licence, and 5.3% are personal use only. For a buyer making a commercial game, a missing licence is a reason to keep looking. Stating one is the cheapest way to stand out on this shelf, and it also counts towards your listing's quality score.
Package it so it imports cleanly
A buyer's first minute with your asset decides how they feel about it. If the import throws errors, nothing else matters. Before exporting:
- One top-level folder. Put everything under
Assets/YourStudio/AssetName, so it does not spill into the buyer's project. - Namespaces for your scripts, so your
PlayerControllerdoes not clash with theirs. - Editor code in an Editor folder, or wrapped in
#if UNITY_EDITOR. Runtime code that referencesUnityEditorbreaks the buyer's build. - Every file with its .meta. Missing .meta files break references after import.
- No junk. No
.DS_Store, no.gitfolder, no absolute paths from your own machine. - Textures sized for use. Ship 2048 or smaller unless the asset needs more, and set compression in the import settings.
- A README and a licence file inside the package, not only on the product page.
What Getly's package check looks at
The Getly Publisher for Unity checks the folder before you upload, and Getly checks the uploaded .unitypackage again on the server. The check has two levels, and the difference matters.
| Problems (block publishing) | Suggestions (never block) |
|---|---|
| Missing .meta files | No README |
| A prefab or scene that references a script not in the package | No demo scene |
Runtime code referencing UnityEditor without a #if UNITY_EDITOR guard | No licence file |
| An absolute path from the author's machine | No namespace |
| System or version-control junk such as .DS_Store or .git | Textures over 2048 or uncompressed |
| An empty package | Empty folders, a very large package, assets not under one top-level folder, a compiled .dll |
A suggestion is advice. If you know your asset better than the rule, for example a plugin that has to ship a .dll, you can publish past it. A problem has to be fixed: a Unity product cannot go live until the server-side check has run and found nothing blocking. Buyers then see a "Package check: Passed" line on the product page. Packages over 150 MB are not checked automatically; they are recorded as unverified and can still be published.
Render pipeline notes buyers look for
A common complaint about a visual asset is pink materials after import. That is a pipeline mismatch, and you can prevent it with a few lines in the description and the right folder structure.
- Say which pipelines you support: Built-in, URP, HDRP. Put it in the first paragraph of the description and in the tags.
- Say which Unity version you tested on, and the oldest version you expect to work.
- Ship materials per pipeline in separate subfolders or separate packages, if you support more than one. Name them clearly:
Materials_URP,Materials_HDRP. - Shader Graph shaders need URP or HDRP. Say so, and offer a fallback material for Built-in if you can.
- Post-processing and lighting in your screenshots should be reproducible from the demo scene. If the look depends on a volume profile, include it.
- Models: state polycount, texture resolution and whether LODs and colliders are included.
A demo scene that sells the asset
A demo scene is a suggestion in the check, not a block, but it is the best sales tool you have. It shows the buyer that the asset works before they wire it into their own project.
- One scene that opens without errors or missing references.
- Everything in the pack visible, or a simple menu to switch between items.
- For tools and scripts, a minimal working example: one button that shows the effect.
- Lighting baked or set up so the scene looks like your screenshots.
- A short text in the scene or the README: "Open Demo.unity, press Play".
Record a short video of the demo scene too. A video or preview adds points to the listing's quality score, and buyers of visual assets want to see motion.
Pricing against the shelf
Use the measured shelf as a frame. The median Unity listing on Getly costs $14.47, the cheaper quarter sits at $4.99 or less, and the upper quarter starts at $21.99. More than a third of the shelf is free.
- A free lite version works well on a shelf where 36.8% of listings are free. Put one or two items or a basic version of your tool out for free, and link the full pack in its description.
- Price the full pack by the time it saves, not by file count. A tool that saves a programmer a day of work can sit in the upper quarter.
- Very small card sales pay a fixed floor: on card orders under about $6, the 30 cent processing fee pushes Getly's take to its floor of processing cost plus 2%. If your asset is a $2 utility, consider a bundle.
- Bundles of related packs give buyers a reason to buy more than one item.
To see where buyer attention is per listing right now, check sell opportunities. It shows which categories get the most product-page views per active listing over the last 30 days.
Publishing from the Unity editor, step by step
- Download the free Getly Publisher for Unity package from its page. It needs Unity 2020.3 or newer.
- Import it and open Window → Getly → Publish Asset.
- Sign in: the tool shows an 8-character code. Open getly.store/link in your browser, approve it, and the tool receives a key scoped to your own store. You never type a password into Unity, and you can revoke the key any time under Developer → API keys.
- Pick the asset folder you want to sell. The tool runs the check and lists problems and suggestions.
- Fix the problems. Decide on each suggestion.
- Submit. The tool uploads the package as a draft; it does not publish by itself.
- On getly.store, open the draft, add images, the description, price, licence and tags, then publish.
- The listing goes to review. Every new listing is checked by the Getly team, usually within a few hours, sometimes by the next morning. A rejection names exactly what to fix.
If you do not want to install anything, upload the .unitypackage on getly.store and press "Check this package" on the product edit page. Same rules, same verdict. Files up to 2 GB are supported.
A listing that passes the quality score
A new listing needs a quality score of at least 70 out of 100 to be published. The score uses fixed rules, and reviews and sales are not part of it, so a brand-new asset can reach 100.
| Part | Points | For a Unity asset |
|---|---|---|
| Description length | up to 25 (1,200+ characters for full points) | What is inside, pipelines, Unity version, how to use it |
| Paragraphs or a list | 10 | A contents list: models, prefabs, scripts, scenes |
| Concrete facts | 10 | Two facts such as "48 prefabs" and "2048 textures" |
| Images | up to 25 (4 or more for full points) | Demo scene, close-ups, the inspector, a pipeline comparison |
| Short description (40+ characters) | 8 | One line: what it is and which pipeline |
| At least 3 tags | 7 | "urp", "low poly", "inventory system" |
| Licence | 7 | Say whether it may be used in commercial games |
| Category | 4 | Unity assets |
| Video or preview | 4 | A short capture of the demo scene |
What you keep and how you get paid
There are no listing or monthly fees. Getly takes a commission only when a sale happens. The details are on the pricing page.
- Base: you keep 80% of each sale.
- First 90 days of a new store: you keep 90% on every sale.
- Your own traffic: 90% on sales within 24 hours of a click on your personal ?sref= link, through a Pay Widget on your site, or in your Telegram store. Put the link in your devlog, Discord and video descriptions.
- Volume tiers: 83%, 85% or 88% when your completed sales in the previous month reach $500, $2,000 or $10,000.
- Getly Exclusive: 85% on a product you sell only on Getly. If you also sell the asset elsewhere, leave this switch off.
Payouts go out on the 1st and 15th of each month in USDT or USDC, to a wallet on BNB Smart Chain (minimum $5). Each sale is held for about a month before it is paid, so your first payout comes roughly a month after your first sale. Getly asks for no KYC for stablecoin payouts.



