A small file does not guarantee low memory
Images, audio and runtime objects all occupy memory, even when their files look small on disk. A mobile table needs a visual budget tied to intended devices. Begin by checking which assets are resident during an ordinary hand and which belong only to optional screens.
A background image may be small on disk while its runtime cost depends on import and usage settings. List card faces, backs, table backgrounds and shop previews for a mobile table. Identify what an ordinary hand needs and what belongs only to optional screens. That question helps explain costs before blindly reducing quality. The aim is not to shrink everything: card information must remain readable at its actual display size.
What stays resident during a hand
Inventory the assets loaded while a normal hand is visible. Separate card faces from optional shop previews and background variations. Inspect memory on an intended device, then reduce one costly asset deliberately. Compare the hand at its actual display size. The question is whether the resource saving preserves the information people need, not whether the imported file becomes smaller by a pleasing percentage.
Change one expensive asset in a separate version and inspect the same hand on the target device. File size, reported memory and appearance are distinct measures. A lower number is insufficient if ranks or suits become blurry. Open the shop and return, observing memory through that route. Folder names cannot reveal which assets remain resident. Measurement lets loading assumptions be compared with actual behavior rather than treating an orderly project hierarchy as proof of low memory use.
Reduce size without losing information
Tie the budget to intended devices rather than a number borrowed from another project. An initial limit can be revised using measurements. Keep reasons for quality changes: an image became smaller because the difference was invisible at this display size, not because every large image is bad. Evaluate shop-preview requirements separately. This gives artists and programmers a concrete cost to discuss without sacrificing essential readability for an unexplained percentage.
Further reading: Unity: Profiler Unity: Asset workflow
For a related example, read Object Pooling: Reuse with Clear Responsibilities.
