When you use Zoom for virtual meetings, webinars, or video calls, you might wonder where Zoom stores the background images used for virtual backgrounds and touch-up features. The answer depends on whether you are using the application on Windows, macOS, iOS, or Android, as well as whether the background image is a default option, a custom upload, or part of a filter or effect. Generally, locally uploaded backgrounds are stored in a dedicated cache folder within the user’s application data directory, while default backgrounds are streamed from Zoom’s servers and not permanently saved on the device.
How Zoom Handles Virtual Backgrounds Technically
Zoom employs real-time segmentation technology to separate the user from the background during a video feed. This process requires significant computing power, so to reduce latency and improve performance, the application relies on temporary storage for assets like custom background images. These files are typically held in a cache location specific to the operating system and the user profile actively logged into the Zoom client, ensuring the image is quickly accessible without needing to reload it for every meeting.
Default Backgrounds and Filter Assets
Zoom comes with a library of default virtual backgrounds, such as landscapes, blurred visuals, and office themes. These are not stored permanently on your hard drive in a user-accessible folder; instead, they are hosted on Zoom’s content delivery network (CDN). When you select one of these options, the client downloads the necessary image or video file temporarily, usually caching it in a secure, app-specific directory that is cleared when the application exits or when the cache is manually flushed.

Custom Uploaded Images
If you have uploaded a personal photo to use as a background, Zoom handles this differently depending on the device. On desktop applications, the original file path is rarely stored in plain text, but a processed version of the image is saved in a cache folder associated with the Zoom application data. On mobile devices, the image is often copied to the app’s sandboxed storage or temporary cache, depending on the operating system permissions granted to the Zoom app.
Locating Zoom’s Storage on Different Platforms
The exact location where Zoom stores these temporary background images varies significantly between Windows, macOS, iOS, and Android. On Windows, the cache is usually found within the `%appdata%` directory under the Zoom folder, while macOS stores them in the Library folder within the user’s profile. Mobile users will find that iOS keeps the data in the app’s sandboxed cache, which is inaccessible without jailbreaking, and Android stores temporary files in the device’s internal storage under the Zoom app’s specific folder.
| Platform | Typical Storage Location | Accessibility |
|---|---|---|
| Windows 10/11 | C:\Users\[Username]\AppData\Roaming\Zoom\tmp | Hidden, requires showing hidden files |
| macOS | ~/Library/Application Support/zoomus/ tmp | Hidden, requires terminal or showing package contents |
| iOS | App Sandbox /tmp directory | Inaccessible without jailbreak |
| Android | /Android/data/zoom.videomeetings/cache | Accessible if "Show hidden files" is enabled |
Privacy and Cleanup Considerations
Because these background images are stored in a cache, they might remain on your device even after you uninstall the Zoom application, depending on the OS storage management policies. For users concerned about privacy, it is a good practice to manually clear the Zoom cache periodically or use the in-app settings to remove temporary files. This ensures that any custom backgrounds or sensitive metadata associated with the virtual background feature are not left lingering on the device.

Understanding where Zoom stores background images is useful not only for troubleshooting technical issues but also for managing digital privacy. Knowing that these files are generally temporary and stored locally in a dedicated cache folder can alleviate concerns about permanent data retention. Whether you are using the default assets or your own images, the handling process is designed to optimize performance while minimizing long-term storage impact on your system.