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.

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?

• Place all asset files under a single folder named after your asset: Assets/YourAssetName/.
• Separate Runtime and Editor code into subfolders with corresponding Assembly Definition files (.asmdef).
• Include at least one demo scene that works out of the box with zero setup.
• All scripts must compile without errors or warnings on the Unity versions you support.

Why Should You Write Documentation Before Finalizing the API?

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. 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.

What Is the Unity Asset Store Submission Process?

• Create your publisher account at publisher.unity.com if you haven't already.
• Fill in the draft listing: title, description, category, keywords, version, supported Unity versions, and price.
• Upload your keyart image (860x389px) and screenshots (minimum 4, maximum 10).
• 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?

• 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.
• Unity runs regular sales opt in. Sales typically generate 3–5x normal volume.
• Offer a free "Lite" version if your asset has a natural tier. Free versions drive enormous discovery.

How Do You Launch and Market a Unity Asset?

• Post to the Unity forums in the "Assets and Asset Store" section on launch day.
• 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.

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

The real work starts after launch. 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?

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. Assets at the top of the market can reach $2,000–$8,000 per month. 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.

How Do You Handle Customer Support at Scale?

Support is the hidden cost of Asset Store publishing that most first-time publishers underestimate severely. The system I use: a dedicated support forum hosted on my own domain, linked prominently in the Asset Store description. A forum scales far better than email because public questions get public answers, which reduces the total volume of repeated questions over time. My FAQ page has reduced email volume by roughly 60%.

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. A measured, helpful public response 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.

How Do You Navigate the Unity Publisher Portal Step by Step?

The Publisher Portal (publisher.unity.com) has evolved significantly since 2015. Here is what to expect when you go through the submission workflow for the first time — field by field, tab by tab.

Basic Info Tab

• Asset Name: This is your listing H1. Include the core function in the name. "Touch Camera PRO" ranks better than "Camera Tool v2" because it tells buyers exactly what it does before they click. Keep it under 60 characters — longer names get truncated in search result cards.
• Publisher Name: Your publisher profile name appears across all your assets. Choose it deliberately — it is your brand on the Asset Store and appears in external search results.
• Category and Sub-category: Unity uses category as a primary browse filter. Choose accurately. Miscategorized assets get rejected during review and lose their algorithmic placement entirely.
• Supported Unity Versions: Set the minimum version you have actually tested against. Claims you have not verified generate negative reviews the day a buyer hits a compatibility error.
• Supported Platforms: Check only platforms where your asset genuinely works. Broad claims create support burden and one-star reviews from buyers on uncertified configurations.

Listing Content Tab

• Short Description: The 160-character snippet visible on search result cards. Treat it like a meta description. Lead with the core function, then the differentiator: "Production-ready multi-touch camera controller for mobile Unity games. Pan, zoom, rotate, and perspective switch out of the box."
• Full Description: Structure it as a sales page: what it is (one paragraph), what problems it solves (bulleted list), feature list, platform and version compatibility, requirements, and support information. Unity's description editor supports basic markdown-style formatting — use it liberally.
• Key Art: Unity requires a Key Art image at exactly 860×389px. This appears on your listing page, in search results, and in featured placements. Design it for legibility at small sizes. Use a clean background with your asset name and one representative screenshot. Avoid clutter — this image is rendered at thumbnail scale in most views.

Media Tab

• Screenshots: Upload a minimum of 4, maximum of 10. Screenshot 1 appears in some search result card views. Show the Inspector UI, an in-scene demo view, and a final in-game result. If your asset has a runtime API, show a code snippet.
• Preview Video: Link your YouTube video URL. Assets with preview videos consistently outsell those without in every category I have published in. 60 to 90 seconds demonstrating the core workflow is optimal — longer videos lose viewers before the payoff.

Pricing Tab

• Unity uses USD as the base currency; other currencies are auto-converted at Unity's rate. You cannot control per-currency pricing.
• You cannot convert an asset from Paid to Free without Unity support involvement. Decide your pricing model before you submit.
• You can submit a sale price and duration through the portal. Unity also runs Asset Store-wide promotional sales periodically — you must opt into these separately via the Sales Management dashboard.

Package Upload

• Use the Asset Store Tools package (available via Package Manager: com.unity.asset-store-tools) to export and upload directly from within the Unity Editor.
• Before uploading: strip editor logs, system hidden files (.DS_Store, Thumbs.db), and any internal assets not intended for the customer.
• Package size limit: 512MB for standard assets. Large collections require Publisher Plus status approval.
• All scripts must compile without errors or warnings on every Unity version you list as supported. The review team tests this on submission. A single compilation error causes rejection.

How Long Does Unity Asset Store Approval Take?

New asset submissions take between 3 and 10 business days to complete the Unity review process. In practice I have seen approvals come through in 2 days for straightforward utility plugins and as long as 14 days for complex packages with large asset collections or embedded video content.

What triggers a longer review period:

• Packages exceeding 100MB in size
• First submissions from new publishers (additional publisher identity verification may be required)
• Assets containing third-party dependencies without clear licensing attribution in the package documentation
• High-volume submission categories — camera tools, character controllers, shader packages, and UI frameworks tend to have longer queues because of submission volume

Update submissions for already-approved assets are significantly faster: typically 1 to 3 business days.

Track your submission status in the Publisher Portal under Asset Management. Unity does not send email notifications when the status changes — you need to check manually. If your submission is rejected, the review team provides a written reason. Common rejection causes: missing or broken demo scene, compilation errors on a claimed Unity version, missing documentation, or Key Art that does not meet the 860×389px specification. Rejections do not penalize your publisher account — fix the reported issue and resubmit.

How Does Unity's Revenue Share Model Work?

Unity takes a 30% platform fee on all Asset Store sales. As the publisher, you receive 70% of the sale price. This is the standard revenue share across major digital storefronts (Apple App Store, Google Play, Steam at standard rates).

• Payment schedule: Unity pays publisher earnings on the last business day of each month, for sales made in the previous month. There is a minimum payout threshold (historically $100 USD); earnings below the threshold roll over to the following month automatically.
• Payment methods: PayPal (most common) or international bank transfer via SWIFT/IBAN. All payouts are in USD regardless of the buyer's currency or location.
• Tax documentation: Unity requires a W-9 (US publishers) or W-8BEN (non-US publishers) before releasing your first payout. Complete this in the Publisher Portal under Account settings before you reach the payout threshold — failing to do so delays your first payment by a full billing cycle.
• Sale pricing and revenue: The 70/30 split applies to the discounted price, not the list price. If you price an asset at $20 and run it at 50% off during a sale, you earn 70% of $10 = $7 per sale. Factor this into your sale participation decisions.

How Do You Write an Asset Store Listing That Converts?

The Asset Store description functions like a product landing page. Most publishers write it last, in 20 minutes, as an afterthought. This is a significant missed opportunity — a well-written listing is the highest-leverage marketing asset in your entire publishing operation.

Opening paragraph (lead with the benefit): Write it like a journalist's lede. "Touch Camera PRO gives your mobile game a fully featured, production-ready camera system with zero configuration required" converts better than "Touch Camera PRO is a Unity plugin written in C# that provides multi-touch camera functionality." Buyers scan for outcomes, not implementation details.

Problems-first bullet list: Buyers search for solutions to problems. "No more hand-rolling multi-touch input across iOS and Android" converts better than "Cross-platform touch input system." Map each feature to the pain point it eliminates. This is also where your search keyword density lives.

Feature list: Comprehensive and formatted as bullets. Include the searchable terms: runtime API, Inspector interface, demo scenes, documentation format, support channel URL, and any third-party integrations.

Compatibility block: "Tested on iOS 15+, Android 8+, Unity 2022.3 LTS and Unity 6 (6000.0 LTS)" is specific and honest. Buyers filter by Unity version before they read your description — give them the information they need to qualify themselves.

Keyword field strategy: The Asset Store has a separate keyword field used in search ranking. Research the terms buyers actually use, not the terms you would use internally. For a camera system: "touch camera", "mobile camera controller", "pan zoom rotate", "pinch to zoom", "cinemachine alternative". Fill every available keyword slot with terms a potential buyer would type into the search bar.

Maintain an active changelog section: After your first update, add and maintain a visible changelog in the description. Buyers check update histories to judge whether an asset is actively maintained before purchasing. An active changelog is stronger purchase signal than a high star average.

How Do You Build a Community Around Your Unity Asset?

The gap between a $500/month asset and a $3,000/month asset often has nothing to do with code quality — it is the community infrastructure around it. Community amplifies word-of-mouth, generates organic content through forum discussions and YouTube tutorials, and creates loyal customers who advocate for your asset inside studios you will never directly reach.

• Unity Forums thread: Post a dedicated support thread in the "Assets and Asset Store" section on launch day, with a demo video embedded and a FAQ pinned at the top. This is your primary indexed support channel — every public question you answer becomes permanent SEO content that reduces future support volume. After two years of active support, the forum thread often outranks your Asset Store listing for long-tail searches.
• Discord server or channel: Real-time community for rapid feedback, feature requests, and building relationships with power users. Power users become advocates who recommend your asset in Discord servers and subreddits you will never see.
• Changelog page on your own domain: Linked prominently from your Asset Store listing. Makes your update history browseable outside the Asset Store and signals that you are an active, committed publisher — not someone who shipped once and disappeared.
• Email list: Even 200 targeted subscribers — Unity developers who bought or trialled your asset — produce a measurable sales spike when you launch a major update or announce a new asset. Collect emails through your support forum or a dedicated product landing page.

How Do You Manage Multi-Version Unity Compatibility?

Unity version compatibility is the ongoing maintenance burden that most first-time publishers underestimate. Unity releases two to four versions per year (Long-Term Support and TECH streams). Your customers use different versions. Your asset needs to compile and function correctly across at least two LTS generations simultaneously.

Recommended compatibility matrix for a new asset in 2026:

• Minimum supported version: Unity 2022.3 LTS. Many studios maintain projects on 2022 LTS through 2027 per Unity's official support policy. Dropping it eliminates a significant portion of the addressable market.
• Primary development version: Unity 6 (6000.0 LTS). Test and develop here first; verify on 2022.3 LTS before each release build.
• TECH stream releases: Do not claim support for TECH stream releases (such as 6000.1, 6000.2) unless your feature requires capabilities unavailable in the LTS. TECH releases break frequently, and the maintenance cost exceeds the size of the TECH-stream audience.

Implementation tactics for multi-version support:

• Conditional compilation: Unity exposes version define constants (UNITY_2022_3_OR_NEWER, UNITY_6000_OR_NEWER) that let you branch code per Unity version with zero runtime cost.
• Assembly Definition version constraints: The versionDefines field in .asmdef files enables conditional code inclusion per package version — useful for supporting both the Built-in and URP render pipelines from a single source tree.
• Automated compatibility checks: Run your test suite against both supported LTS versions before each release. You do not need a full CI pipeline — two local Unity installations and a 30-minute test pass catches 90% of compatibility regressions before they become negative reviews in the store.

How Do You Build a Back Catalog and Cross-Sell Across Assets?

Publishers with multiple assets have a compounding advantage: each new asset acquires customers who are then exposed to your other work. The studio that spent $30 buying your camera controller is the highest-intent buyer on the platform when you release a UI framework six months later.

• Cross-links in every description: Include direct links to your other Asset Store assets in each listing description. Unity permits this. Buyers who love one asset from a publisher convert at a substantially higher rate when they discover additional assets from the same source.
• Free Lite tier as a discovery funnel: A free version of your most popular asset provides permanent, zero-cost discovery. The Lite version should be fully functional for simple use cases but gated on advanced features — additional presets, runtime configuration UI, API hooks. The "Lite" label in the asset name signals that a Pro version exists and frames the upgrade as the natural progression.
• Bundle pricing: Unity's Publisher Portal lets you create bundle packs combining multiple related assets at a combined discount. Bundles convert at 2–3x the individual asset rate because the aggregate value proposition is immediately legible to the buyer without requiring them to evaluate each asset separately.
• Your publisher page: Your publisher profile page at publisher.unity.com aggregates all your assets in one place. Link to it in every asset description and in your Unity forum signature. As your catalog grows, the publisher page itself becomes a destination that qualified buyers bookmark and return to for future purchases.

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. 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.