A folder of Photoshop work reduced to identical blue icons is more than an annoyance: it slows every file choice and invites opening the wrong version. Windows does not preview PSD files by itself, so PSD thumbnails depend on a handler such as SageThumbs, the free open-source shell extension (GPL v2 or later, version 2.0.0.23) that covers PSD within its 162 GFL formats. When PSD previews fail, the cause is usually one of five things: the PSD itself lacks usable preview data, Explorer is set to hide thumbnails, the cache is serving old results, SageThumbs is skipping the file for size, or the handler registration is damaged. This guide separates file causes from system causes with one quick test, then fixes each in turn.
The two-minute test that splits the problem in half
Create or find one small, known-good PSD, ideally a simple file saved recently from Photoshop with maximise compatibility enabled, and copy it into a folder where other previews work. Open that folder in Large icons view. If the test PSD previews correctly, SageThumbs and Explorer are healthy and your problem files carry the cause: preview data, size, or file quirks. If the test PSD also shows a generic icon while JPG files preview fine, the cause is systemic: settings, cache, size configuration or the SageThumbs registration itself. This single distinction prevents the two classic wastes of time, reinstalling software for a file problem and re-saving dozens of files for a system problem.
File cause: PSD files without a usable composite
Thumbnail handlers display the composite preview stored inside the PSD; they do not open Photoshop and render layers. Photoshop’s maximise compatibility option exists precisely to embed that flattened composite, and files saved without it, or produced by tools that write minimal PSD files, may contain nothing a handler can display. The fix is to re-save the file with compatibility enabled, from Photoshop or from an editor that offers an equivalent option, and keep that setting on for future work that others must browse in Explorer. Test the re-saved copy first before batch-processing a library. Extremely large dimensions, unusual modes and damaged headers can also defeat preview generation, which is why testing one re-saved copy tells you more than any amount of settings tweaking when only specific files fail.
System causes: settings, cache and size limits
Work through these in order. First, the folder must be in an icon view, and File Explorer Options must not have Always show icons, never thumbnails checked. Second, clear and rebuild the Windows thumbnail cache so results cached before SageThumbs was installed stop masking the present. Third, open the SageThumbs Control Panel page and check the maximum file size option: production PSD files routinely exceed casual limits, and skipped-for-size files look exactly like broken files until you notice that every failure is a big file and every success is a small one. Fourth, restart Explorer after any change so the handler reloads. If previews return for most files at this point, note which files still fail and treat those individually as file-cause cases rather than reopening the whole system diagnosis.
When SageThumbs itself needs repair
If no PSD previews anywhere while other SageThumbs formats such as TGA preview correctly, or if the SageThumbs Control Panel page has vanished, repair the installation. Reinstall version 2.0.0.23 over the top using the verified installer sagethumbs_2.0.0.23_setup.exe (SHA-256 705d743e28b487e34a4a7245a0dbc303a10e45ba0fd9e4da4101c8cdf506839a), restart Explorer, and rebuild the cache once more. Also check that no cleaner or security utility is removing shell extension registrations on a schedule, a pattern that presents as previews that work after every reinstall and die again within days. And keep the neighbouring-format reality in view: INDD files beside your PSD files will never preview via SageThumbs because INDD is not among its 162 formats, so do not let an InDesign-heavy folder convince you the PSD handler is broken when the PSD files within it are actually fine.
Frequently asked questions
Why do some PSD files preview and others in the same folder do not?
Mixed results point at the files: differing maximise compatibility at save time, sizes above the SageThumbs limit, or individual file quirks. Re-save one failing file with compatibility enabled and compare; that result usually explains the rest of the folder.
Do I need Photoshop installed for PSD thumbnails to work?
No. SageThumbs renders PSD previews from the composite data stored in the file and does not require Photoshop. You need Photoshop or a compatible editor only to re-save files that lack usable preview data.
My PSD previews are generic but the SageThumbs right-click preview works. What does that mean?
The handler is present and can read the file, so suspicion shifts to the Explorer thumbnail cache or view settings. Rebuild the cache, confirm an icon view, and restart Explorer before considering a reinstall.
Related guides
Keep exploring with these guides from this site:
- How to Enable PSD Thumbnails in Windows Explorer
- SageThumbs Thumbnails Not Showing? 8 Fixes
- How to Clear and Rebuild the Windows Thumbnail Cache
Practical notes before you move on
Keep a short note of what you changed and what you observed while working through this guide. Explorer thumbnail problems often return in a slightly different form months later, after a Windows update, a new drive or a change in the kind of files you handle, and a dated note turns the second diagnosis into a five-minute repeat of a known fix instead of a fresh investigation. Note the Windows version, the SageThumbs version (2.0.0.23), the folder and file types involved, and which step actually restored the previews. If a step did nothing, note that too: ruling causes out is real progress, and it keeps the next troubleshooting session focused on what remains.