---
title: "Design Editor caching strategies | Customer's Canvas On-Premises"
canonical: "https://customerscanvas.com/docs/on-premises/design-editor/it-ops/advanced/cache/"
---
# Design Editor caching strategies
> Design Editor uses a cache to make users' work faster. It stores data that they have accessed recently. Original and edited images, images of text layers, proof images, and product templates are cached.
Caching is carried out in the following way. When a user edits a product, Design Editor caches every design element and the product itself. Also, proof images and hi-res outputs are saved in the cache. When a cache size reaches the limit, then a cleanup process starts. The stored items are sorted by a timestamp. The older elements are, the sooner they are removed from the cache. The hi-res output and proofing URLs never expire, however. If a user wants to obtain a file that was removed from the cache, Design Editor renders it again.
You can control the cache and the cleanup process by setting up cache parameters. You can define them in either [FileCache.config](https://customerscanvas.com/docs/on-premises/design-editor/it-ops/config-backend/file-cache.md) file or `Aurigma.DesignAtoms.FileCacheConfiguration` section of **web.config**:
```xml
...
```
## Configuring Cache Parameters
You can set up the cache size and its location. To control the cleanup process, you can set up an interval in seconds between cleanup runs or a cache size that triggers this process.
The following parameters configure the cache:
Name | Description | Default value | Possible values
Cache
MaxSize | the maximum size of the cache in bytes | 4294967296 (4GB) | number
CleanUpInterval | interval between cleanup runs, in seconds | 1800 (30 minutes) | number
MaxUtilizationThreshold | maximum cache utilization level (in percent) that triggers automatic cleanup; when the cache size reaches MaxUtilizationThreshold, the cleanup process starts | 95 | number
UtilizationTarget | utilization level (in percent) to which the cache should be cleaned up; when the cleanup algorithm reaches the UtilizationTarget level, the cleanup process stops | 70 | number
RootPath | the folder where the cache is stored | ~/App_Data/FileCache | folder path
For example, let us change the default parameters to run the cleanup once an hour or after reaching the 90 percent level.
```xml
```
By setting the path to the `RootPath` parameter, you move the cache location to drive D.
## Moving Data Folders to Another Location
By default, Design Editor stores the file cache in the `~/App_Data/FileCache` folder. You may want to change it using relative or absolute paths:
- Relative paths to folders are specified based on your site root and start with `~/`.
```xml
```
- Complete absolute paths start with a drive letter.
```xml
```
- Absolute paths start with `\\` for network locations.
```xml
```
:::note
When you use absolute paths to external folders, make sure the user account, under which Design Editor runs in ASP.NET/IIS, has the read/write access to the remote folders.
:::
As well as for the cache folder, you can change locations of the public gallery, fonts, and the folder containing user data. `PublicGalleryFolder` and `UserDataFolder` should be set up in [AppSettings](https://customerscanvas.com/docs/on-premises/design-editor/it-ops/config-backend/appsettings.md), and `FontDirectory` is set up in [Aurigma.DesignAtoms](https://customerscanvas.com/docs/on-premises/design-editor/it-ops/config-backend/design-atoms.md):
```xml
```