As your library and usage of XBMC grows, so does the memory taken up by XBMC's various settings and files. This page is designed to help reduce the space used, as well as reclaim space from files that are no longer needed.
XBMC stores data mainly in the userdata folder or the parent folder of userdata, "XBMC".
1 Cleanup unused cached images
XBMC does not automatically prune old images that are no longer used. For example, if you remove a movie from the library then the poster and fanart will still be saved in XBMC's userdata folder. Until XBMC has an internal method of pruning these files you can use the highly versatile Texture Cache Maintenance utility to remove unused images.
2 Actor images
If you don't care to download pictures of Actors for when you are browsing or looking up actor information in XBMC, you can turn this off. Doing so can often save a few hundred megabytes of memory, depending on how versatile your video library is.
Go into XBMC -> Settings -> Video -> Library -> and disable the "Download actor thumbnails when adding to library" option.
3 Limit the size of cached images
If you don't already have an advancedsettings.xml file, it's very simple to make. XBMC uses this file for advanced settings and features that normal users shouldn't modify without first knowing what they do, as well as for experimental features, etc.
- Since you can use all or just some of the following settings, let's start out with the basic file. Create a plain text file (no rich text formatting, don't use .doc, etc) and save it as advancedsettings.xml. Make sure that the file extension is ".xml" and not ".txt" or ".xml.txt".
- Cut and paste this into your new plain text file:
- Change the two sizes to a lower value, depending on your needs and how much resolution you need for your skin/TV.
- Save this file in your userdata folder:
- If you have an existing file, make sure the tags are between the main <advancedsettings></advancedsettings> tags.
| userdata folder location:
- Note: In older versions of the software (before v14) the
kodi directories were named
| Operating system
|| File path
|| Android/data/org.xbmc.kodi/files/.kodi/userdata/ (see note)
|| /Users/<your_user_name>/Library/Application Support/Kodi/userdata/ (see note)
|| C:\Users\<your username>\AppData\Roaming\Kodi\userdata
| Windows UWP
| advancedsettings.xml tag
|| what it does
|| Specify the maximum resolution that cached artwork (other than fanart / 16:9 images) should be resized to in pixels. The width is automatically calculated as being 16/9*height. The image will be resized to fit within this size. e.g. an image that is 2000x500 will be cached at size 1280x320. An image that is 500x800 will be cached at size 450x720 using the default value of 720.
| Specify the maximum resolution that cached fanart should be resized to in pixels. The width is automatically calculated as being 16/9*height. Only images that are exactly 16x9 and equal to or greater than this resolution will be cached at this size - all other images will be cached using <imageres>. The default value is 1080.
4 Limit add-on rollback
Another advancedsettings.xml tag that can be used is <packagefoldersize>. XBMC saves old copies of add-ons in case you ever need to revert to a previous version, in case there was a bug in the new version or the user did not like one of the changes. Old add-on packages don't normally take up a lot of space, and the default max size before XBMC starts deleting old packages is 200 megabytes. This setting is mainly to allow a user to increase the number of old versions saved, but it can be used to lower them.
The amount (in megabytes) of add-on zip packages saved from previous add-on installs. These packages are mainly used for the add-on rollback feature. Increasing the size should increase the amount of past versions saved.
5 Move cached images to another drive
Path substitution is another advancedsettings.xml tag. If you simply need more space for XBMC's files but don't wish to limit the image quality then you can use path subs to relocate the images to another drive. It's even possible to use a network file share path, but it is recommended that you use another local drive, if possible, for performance reasons.