The Windows 10 lock screen image is stored in a user-specific cache folder rather than a single fixed location. By default, the active lock screen background is kept in the user’s AppData folder, typically under AppData\Local\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets. Files here are cached and lack extensions, so you must copy and rename them with a .jpg or .png extension to view. You can also check the current lock screen image path in the Settings app under Personalization > Lock screen. The following sections explain these locations in detail, how to reveal the current image, and how the underlying assets are organized.
Default Folder Paths for the Lock Screen Image
Windows 10 stores the active lock screen image as a cached blob in your user profile instead of as a user-selected wallpaper. The most common folder is the ContentDeliveryManager assets directory, which is created by the Windows Content Delivery infrastructure. To reach it:
- Open File Explorer and paste the following into the address bar:
%LOCALAPPDATA%. - Navigate to
Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets. - Inside this folder, you will find files without extensions that represent cached lock screen and other background images.
If you use a Microsoft account and your device is configured to sync lock screen image across devices, this folder will reflect the most recently applied image. On domain-joined or policy-managed machines, group policy or MDM can redirect or lock the lock screen image, which may change where or whether the image is stored on disk.
Alternate Locations and Notes
- The active image you see on the lock screen is usually the newest or most recently updated file in the Assets folder, but not all files there are lock screen images; some are used for other backgrounds.
- If you have set a custom image via Settings > Personalization > Lock screen and chose Picture or Slideshow, the file you chose may also be copied into your user Pictures folder or into the Windows WebCacheV01.dat cache during runtime.
- Third-party tools and scripts sometimes extract these cache files and assign a .jpg or .png extension to make them viewable.
How to See the Exact Lock Screen Image Path in Windows 10
You can confirm the path of the image currently set as your lock screen without hunting through folders:
- Press
Windows key + Ito open Settings. - Go to Personalization > Lock screen.
- Under Background, you will see either Picture, Slideshow, or Windows Spotlight. Below that, if you chose Picture, you will see the file path to the image. If you chose Slideshow, the path will point to the folder containing the images in the slideshow.
This UI entry is the most reliable way to know which file Windows 10 is using at a given moment. Note that Windows Spotlight images are downloaded at runtime and stored in temporary locations that change between updates, so they rarely persist in a stable file path you can bookmark.
Viewing and Extracting the Cached Lock Screen Asset
Because the cached asset in the Assets folder lacks a file extension, you must copy it and add an extension to view it. Follow these steps carefully to avoid confusion with similarly named system files:
- Navigate to the Assets folder described above.
- Sort by Date modified and identify the most recent file that is not
edbor obviously a database file. Lock screen cache files can be large, often several megabytes, similar to JPEG or PNG headers. - Copy the file to another location, such as your Desktop.
- Rename the copy with a .jpg or .png extension, for example
lockcache.jpg. - Double-click the renamed file to open it in your default image viewer. If the preview is garbled or shows an error, try the other extension or use an image editor that can detect format by content.
Bear in mind that the file may be in use or locked by system processes when the screen is active. It is safest to copy the file while signed in on the lock screen or after a restart if the file remains accessible.
Administrative and Policy Controls
Organizations often manage the lock screen through group policy or Microsoft Intune. If policy is enforcing a specific lock screen image:
- The file may be written to a different location, such as
ProgramData, and applied at boot or user logon. - User-side folders like ContentDeliveryManager may be excluded or reset on refresh or upgrade.
- Some policies disable caching of personalized lock screen images entirely, relying on network-based presentation at logon.
In these environments, the “where” question is less about user folders and more about the enforced path documented in the organization’s configuration. You can inspect applied group policy results with gpresult /r or check the effective registry keys under HKLM\SOFTWARE\Policies\Microsoft\Windows\Personalization for lock screen settings.
Summary of Locations and Characteristics
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Primary cache folder | %LOCALAPPDATA%\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets | File system path |
| File naming | No extension; files are raw cached blobs | Observed behavior |
| User-accessible path via Settings | Settings > Personalization > Lock screen shows current Picture path | Windows UI |
| Typical file size | Often multiple megabytes; varies by image resolution | Empirical observation |
| Domain/Policy impact | Group Policy or MDM can redirect or lock the image | Administrative documentation |
| Slideshow behavior | Path points to the folder; individual files may be in temporary caches | System behavior |
By understanding these locations and how Windows 10 manages the lock screen image, you can reliably find the active picture, extract it when needed, and troubleshoot discrepancies caused by policy or profile issues. The combination of the ContentDeliveryManager Assets folder and the Settings personalization page covers most real-world scenarios for both home and managed devices.
Troubleshooting Common Issues
If you cannot see the expected image in the Assets folder, first verify whether your device uses a Microsoft account or a local account, since the cache behavior differs. On Microsoft accounts with sync enabled, Windows may periodically refresh and rename cached files. For local accounts, the image is more static and easier to track. Also ensure that hidden files and file name extensions are visible in File Explorer; otherwise, you might overlook files that lack extensions.
When group policy is in play, the lock screen image may not exist in the user profile at all. In that case, the image is delivered at logon and may only exist in memory or in a system-wide store under ProgramData. Use Event Viewer logs or contact your IT department for the authoritative path if policies enforce branding, security, or compliance imagery.
Compatibility Across Windows 10 Versions
The ContentDeliveryManager folder structure has been consistent since Windows 10 2004, but exact paths can shift with major updates or after significant feature reinstalls. If you recently upgraded from an earlier build of Windows 10 and cannot find the Assets folder, allow time for the Content Delivery Manager to re-populate the cache. In most cases, once the lock screen image stabilizes, the file will appear in the same location until the next major feature update or deliberate configuration change.
Privacy and Cache Considerations
Because the lock screen image cache resides under your user profile, it follows standard file permissions and is not shared with other user accounts unless explicitly copied. Deleting or modifying files in the Assets folder does not change the active lock screen setting immediately; Windows regenerates the cache on the next applicable event, such as applying a new image or a system refresh. If you are troubleshooting disk space, these files are typically small and safe to ignore, though they can be removed when clearing the thumbnail cache or resetting the Content Delivery Manager state.
References and Further Reading
- Microsoft documentation on Windows 10 personalization and lock screen settings.
- File Explorer environment variables and how %LOCALAPPDATA% expands to the current user’s path.
- Group Policy settings for Windows 10 under Personalization, including how policies override user-selected lock screen images.
Understanding the Windows 10 lock screen image location helps both home users and administrators locate, extract, and manage background assets reliably. While user-facing settings point you to the active picture, the actual files live in the ContentDeliveryManager cache, and knowing how to access that folder ensures you can verify, extract, or troubleshoot lock screen visuals across different configurations and policies.
Tags: windows-10, lock-screen, file-locations