YooAsset's README is Chinese only, its licence badge points at master while the default branch is yoo3, and the repository root is a Unity project
unity3d resources management system
At a glance
- What is it?
- tuyoogame/YooAsset is an Apache-2.0 resource management system for Unity3D written in C#, with releases 3.0.4, 3.0.5 and 3.0.6 and a last push on 2026-09-20. The file describes itself through six situations a team finds itself in rather than through an API, which makes the use cases the most readable part and the documentation the thinnest.
- Who is it for?
- YooAsset is worth evaluating if your problem is shipping less than your whole game in the installer, because that is the case the file is organised around and the one the 300 MB example describes concretely. It is not something you can evaluate from the repository alone: the documentation lives on a separate site, the README is in Chinese, and the repository ships as a Unity project rather than a package you inspect.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 16 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- tuyoogame/YooAsset3,408 ★ · +39
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| tuyoogame/YooAsset | 3.4k | 3.4k |
39 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The README exists in one language and the licence badge points at a different branch
The file is short and entirely in Chinese. There is no English version beside it and no second language link at the top, so the badge row is followed immediately by Chinese prose. The only external documentation pointer in the whole file is the project site at yooasset.com, presented as the official homepage with tutorial documents.
That makes the repository's discoverability close to zero for an English-speaking developer who finds it by search rather than by recommendation. There is no API reference in the file, no class list, no method signature and no code sample. What there is, is a description of system characteristics in prose, and it is a decent one.
The badge row has its own inconsistency. The licence badge links to the LICENSE file through a `blob/master/LICENSE` path, while the default branch of this repository is not master. Releases are tagged 3.0.4, 3.0.5 and 3.0.6 and the branch is named yoo3, so the master path in that link is a different line of the project than the one a clone would give you.
Both facts point the same way: the public file was last written for an earlier shape of this project, and the current state of the code is described somewhere other than in the repository.
The default branch is yoo3 and the version line is 3.0.x
A branch named after the major version is not a common convention, and it changes how you read everything else about this repository.
The default branch is yoo3. The tagged releases are 3.0.6 on 2026-09-18, 3.0.5 on 2026-07-20 and 3.0.4 on 2026-07-14, which is three tags inside a single major line with the most recent one two days before the last push on 2026-09-20. The cadence between the two earlier tags is six days.
So there is a 3.x line with active patch releases, and there is a branch layout implying at least one other line existed. Nothing in the file names the other lines, states which one to install, or says whether a 2.x and a 3.x are compatible at the asset format level. The only reference to a previous version is the mini-game platform support, which is described as a property of 2.x.
The practical question for anyone picking this up is therefore which line to take, and the repository does not answer it. A clone of the default branch gives you yoo3, which matches the newest tags, and the badge link in the file points somewhere else entirely.
Six situations, and one of them asks for hundreds of gigabytes
The file opens by asking which of six situations you are in, and this is the most informative part of the README by a wide margin.
The first is shipping an installer containing no game resources at all, with players downloading as they play. The second is shipping an installer that guarantees the early experience and lets players choose which levels to download. The third names a figure: an installer kept under 300 MB, with the remaining content downloaded before the game starts. The fourth is an offline-leaning package that updates normally on a good connection and runs the old version without one. The fifth is a mod package where players upload their own mods to a server and other players download them.
The sixth is the different one. It describes a very large project with hundreds of gigabytes of assets where every build takes a long time, and asks whether building can be split by project.
That last question is the one that explains the feature list. Distributed builds, split by project and by content within a project, is the answer to a build-time problem at a scale most asset pipelines never reach. Everything else in the file, the downloaders and the version management, is infrastructure in service of the first five situations.
Editor simulation mode runs the real environment without building any bundle
There are four run modes: editor simulation, standalone, online and WebGL. The one with a consequence worth knowing is the editor simulation mode.
In that mode you can simulate the real environment without building asset bundles, and you can switch to any of the other modes without modifying any code.
The second half is the significant claim. A pipeline that requires a different code path in the editor than in a build produces bugs that only appear after a build, and a project that accepts that trade has to rebuild to test anything. Saying the switch needs no code change means the same call sites work in all four modes.
The first half is a form of the same idea applied to build time rather than code. If the editor simulation does not need a built bundle, the iteration loop does not include a bundle build, which is where the distributed build feature becomes more than a large-project concern: it is what makes an editor-first loop viable at all.
The file also notes support for hotplug-style flexibility between the traditional built-in build pipeline and the programmable build pipeline, referred to as SBP. Both are supported, and the mode switch above is described as independent of that choice.
Play-while-downloading resolves a missing dependency at load time
The loading system has four parts, and the third is the one that changes how you design content.
Asynchronous loading is offered through several mechanisms, coroutines, Task and delegates. Synchronous loading is supported, and the two can be mixed. Then there is play-while-downloading: when a resource object is being loaded and one of the bundles it depends on does not exist locally, the system downloads it from the server first and then loads the object.
That changes the failure mode. The usual design is to ensure the required content is present before the code that needs it runs, which means a manifest check and a gate. Here the dependency is discovered at the moment of use and fetched, so a missing bundle becomes a wait rather than an error. Combined with the first use case, an installer containing no resources is a supported configuration rather than a stunt.
The fourth part is the downloader. Multi-threaded, with resumable transfer, automatic verification of downloaded files and automatic repair of corrupted ones. Downloaders can be created by asset category tag or by individual asset object, with configurable limits on concurrent files, a retry count for failures and a timeout judgement. Two downloaders running at once are stated not to duplicate each other's downloads, and the downloader exposes progress and failure callbacks.
Automatic repair is the detail that matters most in the field, and it is the one most often left out.
Mini-game platform support is claimed for 2.x, and the current line is 3.0.x
The multi-platform bullet lists Android, Apple, PC and web, which is the expected set for a Unity tool.
Then it adds something narrower and more specific: version 2.x perfectly adapted to the WeChat mini-game platform and the Douyin mini-game platform.
The sentence is bound to 2.x explicitly. The releases visible in this repository are 3.0.4, 3.0.5 and 3.0.6, and the default branch is yoo3, so the line that carries the mini-game statement is not the line a clone gives you. The file does not say whether that support carried forward into 3.x, was dropped, or is inherited from the same runtime layer.
This is the sharpest example of a pattern in the file. Nearly every characteristic is written in the present tense about the system as a whole, with version numbers appearing only where something changed or where a claim is bounded. The reader has to notice those version numbers to avoid reading a 2.x statement as a current one.
For a team targeting those platforms, that is the first thing to verify from the documentation site rather than from the repository. For everyone else, it is a reminder that a feature matrix in a single-language README is only as current as its last edit.
The repository root is a Unity project, not a package directory
The top-level listing has six entries: .gitattributes, .gitignore, Assets/, LICENSE, Packages/, README.md.
Two of them are Unity project folders. That means the repository is not a package published from a source directory, it is a Unity project that contains the package, so the code you would read lives somewhere under Assets/ and the package manifest structure sits in Packages/.
For evaluating the library that has two consequences. You cannot browse a clean source tree at the root, and opening the repository in a Unity editor is a reasonable way to read it. It also means the demo or sample content, if there is any, is likely inside the same project rather than in a separate example repository, which is the common pattern for Unity packages.
There is no CI configuration, no test directory and no build script in the root listing. There is a LICENSE file consistent with the Apache-2.0 recorded for the project, and the git attributes file.
The documentation site is therefore not a convenience. With a Chinese-only README, no API reference in the repository and no test or build configuration to read, the site at yooasset.com is where the actual contract lives.
Editorial conclusion
YooAsset is worth evaluating if your problem is shipping less than your whole game in the installer, because that is the case the file is organised around and the one the 300 MB example describes concretely. It is not something you can evaluate from the repository alone: the documentation lives on a separate site, the README is in Chinese, and the repository ships as a Unity project rather than a package you inspect. Before committing, read the yoo3 branch for the 3.x line you would actually install, confirm your build pipeline is one of the two it supports, and check whether the platform you target was covered by the 2.x mini-game support or by the current line.
Frequently asked questions
What is YooAsset?
A resource management system for Unity3D, written in C# and licensed under Apache-2.0. It is built around deploying and delivering game content, with distributed builds, addressable resources, tag-based bundle splitting and a set of downloaders.
Which platforms does YooAsset support?
Android, Apple, PC and web are listed, plus a WebGL run mode. Version 2.x is described as perfectly adapted to the WeChat mini-game and Douyin mini-game platforms, though the current releases are 3.0.x.
Do I have to build asset bundles to test in the Unity editor?
No. Editor simulation mode can simulate the real environment without building asset bundles, and you can switch to standalone, online or WebGL modes without modifying any code.
How does YooAsset handle downloads and corrupted files?
Multi-threaded downloading with resumable transfer, automatic verification of downloaded files and automatic repair of corrupted ones. Downloaders can be built per category tag or per asset object, with limits on concurrent files, retry counts and a timeout, and concurrent downloaders do not duplicate files.
Which YooAsset versions exist and what is the default branch?
Tagged releases include 3.0.6 from 2026-09-18, 3.0.5 from 2026-07-20 and 3.0.4 from 2026-07-14, and the default branch is named yoo3. The repository holds Assets/ and Packages/, so it is a Unity project rather than a bare package.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tuyoogame-yooasset)Star history chart for your README
[](https://hysenlabs.com/projects/tuyoogame-yooasset)Was this useful?