Storage Allocation
From Roll20 Wiki
Storage and Management
To help users manage assets and account storage limitations as well as control game size, here is a table of how things you upload, purchase, or create are stored and managed on Roll20.
| Item | Calculated in User's Account Storage | Loaded with Game |
|---|---|---|
| Art | Y | Y |
| Music Uploaded | Y | N |
| Music Linked to | N | N |
| Character Sheets | N | Y |
| Pages (Map Pages) | N | Y |
| Handouts | N | Y |
| Macros | N | Y |
| Card Decks | N | Y |
| Tables | N | Y |
| API Scripts | N | Y |
| Marketplace Modules | N | Y |
| Marketplace Art (token images and map items) | N | Y |
| Marketplace Modules | N | Y |
| Marketplace Addons | N | Y |
| Marketplace Decks | N | Y |
Y = Yes this item counts in this category
N = No, this item does not count in this category
For an item to count as being loaded at runtime, it must be deployed within the game. An image in your library does not get loaded at run time unless it has been placed onto the tabletop.
Keep in mind that any item that uses another item. I.e. a handout containing art from the user library) will count the art as being "in the game". A card deck takes up minimal memory, but all of the images are counted in the Art library.
Special Cases
Rollable Tokens and Card Decks
Rollable Tokens and Card Decks are quite small in space they take up. Images are not "double-dipped" from your Art Library storage. These items will only impact your game size if the assets are actually deployed onto a page. A rollable token that has a hundred faces, but only ten of them are showing on a given page will only count the images that are showing when considering game size. They will not affect your Account Storage because the images are already accounted for in your Art Library.
