What is com.apple.quicklook.ThumbnailsAgent, and why is it using CPU?
Last reviewed: 19 November 2026. Path, account and launchd job checked on macOS 26.3.1.
com.apple.quicklook.ThumbnailsAgent is the macOS agent that produces the thumbnails of files you see in Finder, Open and Save dialogs and other apps, and keeps them in a cache. It is busy when you open folders full of images, videos or documents that have no cached thumbnail yet. It is part of macOS and safe.
com.apple.quicklook.ThumbnailsAgent at a glance
| com.apple.quicklook.ThumbnailsAgent | |
|---|---|
| Made by | Apple (part of macOS, Quick Look) |
| Type | Launch agent (background process for your user) |
| Location | /System/Library/Frameworks/QuickLookThumbnailing.framework/Support/com.apple.quicklook.ThumbnailsAgent |
| Runs as | your user |
| Started by | launchd job com.apple.quicklook.ThumbnailsAgent |
| Can you quit it? | Yes, but launchd starts it again the next time a thumbnail is needed. |
What is com.apple.quicklook.ThumbnailsAgent?
It belongs to Apple's QuickLookThumbnailing framework, which Apple documents as the way to generate thumbnails for common file types such as images, Live Photos, text, PDFs, audio and video. For other file types, apps can supply a thumbnail extension, and Finder, Spotlight and other apps use it through the same framework. Apple's own thumbnail extensions, such as ImageThumbnailExtension, work alongside it, and the agent keeps the results in its cache.
Its launchd job wakes it when Finder empties the Trash or deletes items immediately, so it can drop thumbnails of deleted files, runs a daily cleanup of its cloud thumbnail database, and registers a service that frees cache space when the disk is low.
Is com.apple.quicklook.ThumbnailsAgent safe?
Yes. It is in the QuickLookThumbnailing framework on the read-only system volume and runs as your user. Its long name is its launchd label and executable name.
Why does com.apple.quicklook.ThumbnailsAgent use so much CPU, disk and memory?
- Folders with many images or videos. Opening a folder of thousands of photos or videos in icon or gallery view asks for a thumbnail of each one that is not cached.
- Files on slow or network drives. Thumbnails of files on external, network or cloud-only storage have to be read from that storage first.
- Third-party thumbnail extensions. Apps can add thumbnail extensions for their own file types. A slow extension makes thumbnail creation for those files slow.
- Large source files. Making a thumbnail of a large RAW photo, PDF or video means decoding part of the file in memory.
How much CPU is normal for com.apple.quicklook.ThumbnailsAgent?
A burst of CPU when you open a large folder for the first time is normal; later visits use the cache. It typically idles at 0% CPU.
How do you stop com.apple.quicklook.ThumbnailsAgent from using so much CPU?
- Use list view for very large folders. In Finder, choose View > as List for folders with thousands of media files. List view needs far fewer thumbnails than icon or gallery view.
- Let the first pass finish. Leave a large folder open for a minute; once thumbnails are cached, the agent goes quiet.
- Reset the thumbnail cache. If thumbnails are wrong or it keeps working on the same folder, run
qlmanage -r cachein Terminal. Theqlmanagehelp describes this as resetting the thumbnail disk cache. - Remove a misbehaving app. If trouble started after installing an app that adds previews or thumbnails, update or remove that app.
When should you worry about com.apple.quicklook.ThumbnailsAgent?
Look closer if it uses CPU for a long time with no Finder windows open. A file it cannot finish, often on a network drive, can keep it retrying; ejecting the drive tells you quickly.
How do you check com.apple.quicklook.ThumbnailsAgent in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type com.apple.quicklook.ThumbnailsAgent in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every com.apple.quicklook.ThumbnailsAgent process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'com.apple.quicklook.ThumbnailsAgent' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with com.apple.quicklook.ThumbnailsAgent?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when com.apple.quicklook.ThumbnailsAgent is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click com.apple.quicklook.ThumbnailsAgent in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about com.apple.quicklook.ThumbnailsAgent
Is it the same as quicklookd?
No. quicklookd is the Quick Look server that the qlmanage tool manages; ThumbnailsAgent belongs to the QuickLookThumbnailing framework.
Will resetting the cache lose anything?
No. Thumbnails are generated again from the files as you browse, which costs some CPU the first time.
Sources
- qlmanage(1) man page and qlmanage -h: run them in Terminal
- Apple Developer: QuickLookThumbnailing