After installing SageThumbs, most image formats spring to life in Explorer, but Adobe Illustrator AI files, EPS and PS files, and PDFs often keep their generic icons. That is by design: SageThumbs renders its 162 GFL formats itself, but those document-style formats are rendered through GhostScript, and not just any GhostScript. The author specifies one specific release, AFPL GhostScript 8.54, hosted on the author’s own site. Newer GhostScript releases, however excellent they are in other contexts, are not compatible with SageThumbs and will not enable these thumbnails. This guide explains why the version is pinned, how to choose between the 32-bit and 64-bit builds, and how to confirm the combination is working. SageThumbs itself is version 2.0.0.23 of 9 May 2017, free and open source under GPL v2 or later.
Why it must be 8.54, and why AFPL matters
SageThumbs was built against the GhostScript interface of its era and the author validated and bundled the workflow around AFPL GhostScript 8.54. Later GhostScript development changed enough that SageThumbs cannot use modern releases for this rendering path, a common story for a 2017 shell extension integrating with another project’s internals. The correct name also matters when you search: the author specifies AFPL GhostScript, the Aladdin Free Public License line of that era, so pages describing an AGPL 8.54 for SageThumbs are using the wrong licence name for this specific historical release. Precision here is practical, not pedantic: searching and downloading with the exact name avoids lookalike packages and modern builds that will never work with SageThumbs no matter how carefully they are installed.
Choose the build that matches your system
The author hosts both builds: the 64-bit build at the 64-bit AFPL GhostScript 8.54 download and the 32-bit build at the 32-bit AFPL GhostScript 8.54 download. On a 64-bit Windows system, which is nearly every Windows 10 and Windows 11 machine in use today, choose the 64-bit build. Choose the 32-bit build only for a genuinely 32-bit Windows installation. Matching the build to the operating system edition mirrors how the SageThumbs combined installer itself works, and a mismatched GhostScript is a quiet cause of AI and PDF thumbnails that never appear despite both programs being present. If you are unsure of your edition, check Settings, System, About, where Windows lists the system type directly.
Install and restart Explorer
- Install SageThumbs first if it is not already present, and confirm ordinary image thumbnails such as PSD work.
- Download the matching AFPL GhostScript 8.54 build from the author’s hosting via the links above.
- Run the GhostScript installer and complete setup with its default location.
- Restart Windows Explorer from Task Manager, or restart the PC, so SageThumbs picks up the newly available renderer.
- Open a folder containing AI, EPS or PDF files in Large icons view and allow a few moments for first-time generation.
Order matters. GhostScript on its own adds nothing visible to Explorer; it is a rendering engine that SageThumbs calls. SageThumbs on its own cannot render these formats. Only the combination produces thumbnails, which is why installing them in either order and then restarting Explorer once at the end is the reliable sequence. Keep the GhostScript installer file you used, noting its exact version, so a future machine rebuild can reproduce a working setup without rediscovering the 8.54 requirement the hard way.
Testing and troubleshooting the combination
Test with a file you know is healthy: a PDF that opens correctly in a reader, and an AI or EPS file from a real project. If PDFs preview but AI files do not, re-save a copy of the AI file with PDF compatibility enabled in Illustrator, because SageThumbs and GhostScript rely on the PDF-compatible data inside modern AI files; an AI file saved without that compatibility has nothing for this rendering path to draw. If nothing in this format group previews, confirm the GhostScript build truly is 8.54 and matches your system edition, confirm SageThumbs thumbnails work for other formats, and clear the Windows thumbnail cache so old generic-icon entries are not masking new successes. Do not respond to failure by installing the newest GhostScript over the top: that replaces a compatible renderer with an incompatible one and moves you further from a working setup.
Frequently asked questions
Can I use the latest GhostScript instead of 8.54?
No, not for SageThumbs. The author specifies AFPL GhostScript 8.54 for AI, EPS, PS and PDF thumbnails, and newer GhostScript releases are not compatible with SageThumbs’ rendering path. Install 8.54 alongside your normal tools as directed in this guide.
Do JPG, PNG and PSD thumbnails need GhostScript?
No. Those formats are part of the 162 formats SageThumbs renders via the GFL Library on its own. GhostScript is needed only for the AI, EPS, PS and PDF group.
Is GhostScript required on both 32-bit and 64-bit SageThumbs installs?
Yes, the requirement is about the format group, not the SageThumbs edition. Whichever system you run, AI, EPS, PS and PDF thumbnails need the matching-edition AFPL GhostScript 8.54 installed as well.
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 Install SageThumbs on Windows 11
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.