Search Issue Tracker

By Design



Found in







Issue ID




Built Asset Bundles yield identical file sizes of different Assets when using Standard Build Pipeline

Asset Bundles


How to reproduce:
1. Open the user attached "" project
2. Select the "texture.jpg" file found in the Assets/Texture folder in the Project window
3. Set the Texture Type to "Sprite (2D and UI)" in the Inspector window
4. Build the Asset (BuildAssetBundle -> StandardBuildPipeline)
5. Open the "AssetBundles' folder in the project folder

Expected result: Different Asset sizes
Actual result: Identical Asset sizes

Reproducible with: 2019.4.36f1, 2020.3.28f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a4

Note: Building the Asset with "ScriptableBuildPipeline" yields the expected result

  1. Resolution Note:

    The size being similar is caused by the texture being included in both AssetBundles with the builtin build pipeline. You can observe the content by using WebExtract on the AssetBundles and Binary2Text on the files. To better understand this duplication you can refer to this section "Duplicated information across AssetBundles" in ScriptableBuildPipeline will attempt to resolve this automatically. If you run the generated bundles through binary2text you will observe that the prefab one generated by ScriptableBuildPipeline it contains an external reference to the other bundle .

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.