How to Publish a Unity Asset to the Asset Store: The Complete Publisher Guide

Why Publish on the Asset Store?

I published my first Unity Asset Store package in 2015. Today I have over ten assets live, generating consistent passive income while I sleep. More importantly, each asset has become a portfolio piece, a community touchpoint, and a source of consulting leads. If you're a Unity developer who has built a reusable tool for your own projects, there is almost certainly a market for it. This guide walks through the entire process from idea to launch, based on hard-won experience.

How Do You Validate a Unity Asset Idea Before Building?

Before writing a line of publishable code, spend an hour on the Asset Store searching for similar tools. You're looking for two signals:

• Demand exists: If there are 3–5 assets solving the same problem, with reviews and ratings, that's validation. You don't need a gap in the market — you need to solve the problem better or differently.
• Your differentiator: What do you do that existing solutions don't? For Touch Camera PRO it was the multi-platform unification and smooth perspective switching. For Tutorial Engine it was the visual graph-based workflow. Know your angle before you start.

Also check the Unity forums and Reddit's r/Unity3D for recurring questions about the problem space. Frequent frustrated posts are gold — they're your future customers telling you what they need.

How Should You Structure a Unity Asset Store Package?

The Unity Asset Store has strict packaging requirements. Structure matters for both the review process and the customer experience:

• Place all asset files under a single folder named after your asset: Assets/YourAssetName/. Never dump files in the root Assets folder.
• Separate Runtime and Editor code into subfolders with corresponding Assembly Definition files (.asmdef). This prevents your editor-only code from being included in builds.
• Include at least one demo scene that works out of the box with zero setup. Reviewers and customers should be able to hit Play and see something working immediately.
• All scripts must compile without errors or warnings on the Unity versions you support. Test on the minimum and maximum versions you list.

Why Should You Write Documentation Before Finalizing the API?

I know it sounds backwards, but writing the documentation before you finalize the public API forces you to think like a user. If a feature is hard to document, it's probably hard to use. I use Google Docs for online documentation and host the link prominently in the asset's description. For APIs I use DocFX to generate HTML from XML doc comments and host it on a subdomain.

Your documentation should cover: quick start (5 minutes to a working scene), all public API methods with parameters and return types, common use cases with code examples, and a troubleshooting FAQ. Time invested in documentation directly reduces the volume of support emails you'll receive.

What Is the Unity Asset Store Submission Process?

Use the Asset Store Tools package (available free from the Asset Store) to upload your package. The submission workflow:

• Create your publisher account at publisher.unity.com if you haven't already.
• Fill in the draft listing: title, description (supports limited HTML), category, keywords, version, supported Unity versions, and price.
• Upload your keyart image (860x389px) and screenshots (minimum 4, maximum 10). Quality screenshots are critical — they're the first thing buyers see.
• Upload a package preview video to YouTube and link it. Assets with videos consistently outsell those without.
• Export your package from Unity using Asset Store Tools and upload it.
• Submit for review. Unity's review team typically takes 3–10 business days.

How Should You Price a Unity Asset Store Package?

Pricing on the Asset Store is a surprisingly strategic decision. My observations after years of watching the market:

• Under-pricing signals low quality. An asset priced at $4.99 will be bought less than the same asset at $19.99 because buyers assume it must be low effort.
• The sweet spot for utility tools and plugins is roughly $20–$50. Larger systems (level editors, full game templates) can go $50–$200.
• Unity runs regular sales (Asset Store sales, Made with Unity sales). Your asset will be included automatically if you opt in. Sales typically generate 3–5x normal volume and are worth the revenue reduction.
• Offer a free "Lite" version if your asset has a natural tier. Free versions drive enormous discovery — the paid version conversion is typically 5–15%.

How Do You Launch and Market a Unity Asset?

The Asset Store's search algorithm rewards recent reviews and sales velocity. Your launch week matters most. Strategies that work:

• Post to the Unity forums in the "Assets and Asset Store" section on launch day. Write a detailed, helpful post — not a sales pitch.
• Share on Twitter/X, LinkedIn, and relevant Discord servers with a short demo GIF or video clip.
• Email any beta testers or early users and ask for honest reviews.
• Create a short YouTube tutorial for your most compelling use case. Tutorial videos continue generating traffic and sales for years.

How Do You Maintain a Unity Asset Store Product Long-Term?

The real work starts after launch. Customers will open support tickets. Unity will release new versions that break things. You need to commit to maintaining your asset for as long as it's for sale. I recommend setting aside one day per month for each active asset. Address reported bugs within 48 hours, and update for each major Unity LTS release. A maintained asset with responsive support consistently earns 4–5 star reviews. A neglected one earns 1-star reviews that tank your sales permanently.

What Are Realistic Income Expectations for Asset Store Publishers?

I want to be direct about this because most Asset Store income discussions are either overly rosy or pointlessly vague. Here is what I have observed across my own catalogue and the publisher community:

A new asset in the $20–$40 range with a good launch and consistent 4+ star reviews will typically settle into a range of $200–$800 per month within its first year. That is meaningful supplemental income but not retirement money. Assets at the top of the market — those that become the go-to solution in their category — can reach $2,000–$8,000 per month. There are a handful of publishers doing significantly more, but these are outliers with enormous catalogues or assets that fill uniquely high-demand niches.

The more useful framing is return on invested time. My Touch Camera PRO asset required approximately 200 hours to build, document, and launch. Three years later it has generated multiples of what I would have earned billing those 200 hours to a client — and it continues to generate revenue. That is the Asset Store value proposition: leveraged, compounding return on a one-time investment, provided you maintain it.

The assets that fail commercially almost always have the same root causes: a market that doesn't exist or doesn't buy (over-reliance on "this would be useful" rather than demonstrated demand), inadequate documentation that increases support burden and drives negative reviews, and abandonment after launch when Unity version updates cause breakage.

How Do You Handle Customer Support at Scale?

Support is the hidden cost of Asset Store publishing that most first-time publishers underestimate severely. A successful launch generates a wave of support requests, and the volume does not proportionally decrease after launch — every sale is a potential support ticket.

The system I use: a dedicated support forum hosted on my own domain, linked prominently in the Asset Store description and in the asset's welcome screen inside Unity. A forum (I use a simple self-hosted solution) scales far better than email because public questions get public answers, which reduces the total volume of repeated questions over time. My FAQ page, built from the most common support threads, has reduced email volume by roughly 60%.

Response time matters disproportionately for reviews. A user who gets a helpful response to a problem within 24 hours almost never leaves a negative review, even if they had a serious issue. The same user ignored for a week will one-star you and describe the problem in detail. I treat support as the most important marketing activity for an active asset.

Set up an automated onboarding email triggered on purchase (via the Asset Store partner program or a webhook) that links to the quick-start guide, the support forum, and your contact email. This single step intercepts 20–30% of potential support requests before they become tickets.

How Do You Handle Negative Reviews?

Negative reviews are inevitable. The productive response is to treat every negative review as a bug report and respond publicly in the review thread. Unity's publisher portal allows you to reply to reviews. A measured, helpful public response — "Thank you for reporting this — I've identified the issue and released a fix in v2.3.1; please update and let me know if the problem persists" — does more for your asset's perceived quality than five additional positive reviews. Potential buyers read your responses. They are evaluating how you behave when things go wrong, not just how well the asset works when things go right.

What you should never do: argue with a reviewer, dismiss a reported issue, or ask a reviewer to change their rating unprompted. Even if the review is factually wrong, a defensive response looks worse than the review itself.

Is Publishing on the Unity Asset Store Worth It?

Publishing on the Unity Asset Store is one of the best investments a Unity developer can make. It's not passive income in the "zero work" sense — it requires real ongoing commitment — but it is leveraged income: work you do once continues to pay dividends indefinitely. Start with a tool you've already built for yourself, document it thoroughly, price it fairly, and treat your customers like the professionals they are.