Why Photo Folder Thumbnails Take Ages to Load

How the thumbnail pipeline works

For every file in a folder view, Explorer asks the Windows Imaging Component to decode the image down to a small bitmap, and the results are cached per size in the thumbcache_*.db files under %LOCALAPPDATA%\Microsoft\Windows\Explorer. The first open of a folder is therefore decode-bound: every 45-megapixel raw or JPEG costs real CPU, and a few thousand of them is minutes of work. Cached folders open instantly — that's the whole design. Raw formats (CR3, NEF, ARW) add a dependency: without a vendor codec installed, Windows shows the icon and nothing else.

Cloud folders add their own delay: OneDrive's online-only files pull their previews from the cloud, a round-trip each, and a flaky connection turns a photo folder into a slideshow of placeholders. None of this says anything about your hardware.

• cold cache — the first open of a huge folder decodes every image from scratch
• corrupted cache — missing or wrong thumbnails for files that clearly have previews
• raw and video formats without their codecs installed
• online-only cloud files fetching their previews over the network
• an HDD as the system drive, where the cache itself is slow to read
• "Always show icons, never thumbnails" quietly switched on in Explorer

Fixes that actually work

First, keep the cache warm: don't wipe thumbnails on a schedule like some cleaners suggest, because every wipe buys you the full decode again. When the cache is genuinely broken — previews missing, or showing the wrong images — rebuild it: Disk Cleanup (cleanmgr), pick drive C:, check "Thumbnails", let it delete, and Explorer rebuilds previews as you browse. While you're at it, open File Explorer Options → View and make sure "Always show icons, never thumbnails" is off; it's a legitimate setting that gets toggled by accident or by "optimization" scripts.

Second, match the tool to the library. Explorer is a file manager, not a photo database: browsing 50,000 files in one folder is abuse, and splitting by year or shoot fixes more than any tweak. For real photo work, a manager with its own preview cache (digiKam, Lightroom) generates previews once and then answers instantly. For OneDrive, set your working folders to "Always keep on this device" so thumbnails come from the local disk, not the cloud.

When it's worth looking somewhere else

If even the Details view is slow to populate — file names and sizes crawling in — the bottleneck isn't thumbnails but metadata reads: antivirus scanning every file as Explorer touches it, a drive that is dying, or shell extensions from sync and disk-imaging tools hooking every folder you open. That's a different problem with different fixes, and it's worth diagnosing before you blame the thumbnails.

The quick test is selective: if Details is instant but previews crawl, it's decode and cache; if everything crawls, look at the disk and what's hooking Explorer. Two minutes of watching which half lags saves an evening of fixing the wrong thing.

Questions and Answers

Read next