Correct way to use Sprite Atlases?

[ccklokwerks]

Is the use of a Sprite Atlas supposed to be completely transparent to other components? i.e. Do I still reference the sprites individually via an Image script?

The reason I ask is, while doing some R&D on building something for WebGL, I noticed that both the sprite atlas AND THE INDIVIDUAL SPRITES are being included in the build. Something is wrong here, but maybe it’s me.

Portion of my editor log showing the atlas and the individual sprites being included in the build:

[HiddenTess]

I’ve been seeing similar problems with using the new Sprite Atlases in Asset Bundles. It not only appears to bundle the individual sprites, but a bundle containing a variant atlas seems to have a dependency to the bundle containing the master atlas. This makes me very sad.

[xucian]

any update on this?

[Peter77]

According to the Unity Answers post, duplicated sprite assets in memory is solved by deleting the Library folder and restarting Unity.

Both atlas and individual sprite in memory?

BTW, the following forum post could be of interest as well:

About "Include in Build" behaviour

I’m trying to use a Sprite Atlas feature in Unity2017.1.0f1. I need to download Sprite Atlas assets via Asset Bundle at runtime and not to be included in a built app binary (In other word, I don’t use Resources). So I have some questions: “Include in Build” means “A built app binary contains a packed sprite atlas”? If I need to use Asset Bundle, should I uncheck the “Include in Build” option? In such case, should I always do “late binding” written in the following document? (I have a prefab…