My cache folder is 3.7 gig, and it does contains some important files, so I would not mess with it. For Safari use the Reset Safari function and select your choices. FYI, in my case the app Garmin (European GPS maps) was using 2gig in cache. Once I was done with it, I deleted it and now back to.7 gig. In Bridge: Edit Preferences Cache Purge Cache should do the trick. As for the other programs, you must visit their respective forums and ask for help there. Be sure to specify your OS version and program version, it will get an answer much faster since there are Macs as well as Windows based PCs running Adobe products.
This page is a companion document to the system requirements for Premiere Pro and After Effects. It provides additional information on system components and considerations for optimal performance.
Want a downloadable version of this document? Click here to download a PDF.
The four key variables for a great video production system are memory, storage, graphics, and your processor.
Professional video workflows rely on system memory. A good video editing workstation should have at least 32GB of memory— and as much as 128GB.
Fast storage is critical for video production. Use solid-state NVMe or SSD storage. Unless you have a fast RAID array, spinning disks generally do not offer sufficient speed for HD and 4K video production.
Adobe Media Cache Files Delete
The best way to achieve excellent performance (and to keep different types of files organized) is to spread the load between multiple drives. An optimal setup has three drives:
- System drive for OS and applications
- Drive for the media cache
- Media drive (or shared storage)
Only have two drives? Use a fast external drive for your media and Media Cache.
The media cache is where Premiere Pro stores accelerator files, including peak files (.pek) and conformed audio (.cfa). Premiere Pro can make thousands of call to these files every second). For more information, see Set Media Cache preferences.
Media Cache Files Mac
- NVMe Flash memory drives with Thunderbolt 3.0 connectivity are excellent.
- SSD drives with USB 3.1 connectivity are also good - but have a 4TB limit.
The GPU is used for onscreen rendering and export, priority areas for video production. Premiere Pro is engineered to take advantage of the GPU. After Effects is also GPU-optimized.
- Graphics card with at least 4GB of memory (VRAM).
- (Optional) Multiple GPUs, including eGPUs, can be used to speed up rendering and export.
Out-of-date graphics drivers are one of the most common causes of performance issues with video applications. For optimal performance, make sure you have the latest drivers for your GPU, including integrated Intel GPUs. For more information, see GPU and GPU Driver Requirements for Premiere Pro.
For CPUs, clock speed matters more for After Effects. Multiple cores have more impact for Premiere Pro. The sweet spot for running both applications is a fast CPU with 8 cores.
- Core i7 or Core i9 Intel processors or AMD equivalents are strongly recommended.
- Fast clock speed at least 3.2 GHz, or higher.
- 8 cores are ideal for Premiere Pro. The application can use more cores, but without significant added benefit. Depending on the task, Premiere Pro runs at 93-98% efficiency with 8 cores.
H.264 and H.265 (HEVC) are widely used capture formats for DSLRs, mirrorless cameras, action cameras, and phones. H.264 is also the preferred format for uploading to YouTube and social media sites. These compressed formats are well suited for capture and distribution, but they are processor-intensive for post-production.
If you work with H.264 and H.265, consider Intel Core i7 and Core i9 processors, which offer Quick Sync hardware acceleration, supported in both Premiere Pro and After Effects.
AMD and Intel Xeon processors work well for other formats, such as cinema camera formats, (such as RED, Sony Venice, ARRI) and broadcast formats (such as XDCam HD).
Adding memory is the easiest and usually most impactful place to start if you want to upgrade your system to improve performance for both Premiere Pro and After Effects.
Upgrade Premiere Pro system in this order of priority:
- More RAM — up to 128GB if your motherboard supports it.
- A faster GPU (or additional GPUs) for faster rendering and export
- Faster (or more) NVMe or SSD drives
- Faster CPU
Upgrade your After Effects system in this order of priority:
- More RAM — 128GB is a good target for top-of-the-line systems.
- Faster (or more) SSD or NVMe drives
- Faster GPU (or additional GPUs) for faster rendering and export
- Faster CPU
Export times are impacted both by your graphics hardware and your workflow. A second GPU (same class GPU as the primary GPU) can provide substantial speed increases for export. Creating previews during your edit can also accelerate export times.
Assuming you have a good system, performance for multicam workflows is more dependent on your project setup than your hardware. Expert users create their own project templates to standardize their setup.
A calibrated reference monitor connected through external transmit hardware is highly recommended for accurate display of interlaced and color critical content. Proper monitoring of HDR content requires an HDR-capable external display.
This is a matter of personal preference. Because the timeline is a central element in the Premiere Pro UI, an ultra wide 37” display combined with a second reference monitor is an excellent option.
Simultaneous monitoring of multi-channel audio requires a multi-channel sound card. On Windows the sound card should be ASIO-capable.
Your workflow, and how you decide to work with file formats, can have a significant impact on overall performance. Our best practices guide for working with native formats has suggestions for designing your workflow to ensure optimal performance with your hardware.
- Puget Systems recommendations for Premiere Pro
- Puget Systems recommendations for After Effects
The Adobe Bridge central cache stores thumbnail, preview, and metadata information in a database. This database improves performance when you browse or search for files. However, the larger the cache, the more disk space it uses. Cache preferences help you manage the trade-off between performance and cache size.
- Choose Edit > Preferences > Cache (Windows) or Bridge > Preferences > Cache (Mac OS) and choose from among the following options:
100% Preview, also called full-size cache, is a JPEG file that displays the 100% zoom-in. This zoom-in is what you see in a slideshow and in full-screen preview. It is also what you see when you use the Loupe tool in Review mode or the Preview panel. When you use this cached file, you avoid rerendering a 100% image from the original source file. However, it does require additional disk space and initial processing takes some time.
When you use the Loupe tool or 100% zoom, this 100% preview is extracted into memory from the file. The Keep 100% Previews In Cache option allows the 100% preview to be written to the central cache, which is in the following location:
- Mac OS: /Users/[User name]/Library/Caches/Adobe/Bridge CS[version number]/Cache/full
- Windows: /Documents and Settings/[User name]/Application Data/Adobe/Bridge CS[version number]/Cache/full
Note: On Windows, turn on Show Hidden Files to see this location. See Show hidden files, folders, filename extensions Windows XP, Vista, Windows 7.
You can also generate full-size previews for all files in a folder. Click the thumbnail and preview quality button in the Application bar and choose Generate 100% Previews. These full-size previews are only used for 100% zoom and loupe, however. They are not used to display thumbnails, slideshows, and screen previews in less than 100% view. Also, they aren't used in the Preview panel or Review mode when you are not using the Loupe tool.
Automatically Export Cache To Folders When Possible
This option synchronizes central and exported cache data. It generates exported cache files for every folder that Adobe Bridge browses (as long as the folder is not read-only).
The first time Adobe Bridge views a folder, it checks for the existence of an exported cache. If it finds an exported cache, Adobe Bridge imports all the entries into its central cache. After that, Adobe Bridge only deals with the central cache for that folder; any new or modified thumbnails or metadata is stored in the central cache. If Automatically Export Cache To Folders When Possible is selected, Adobe Bridge also updates the exported cache with the newly generated or updated thumbnails or metadata. But Bridge does not read exported cache data for that folder since the folder exists in the central cache. What does this mean in practice? It comes into play when multiple instances of Adobe Bridge -- on the same or different computers -- view the folder. For example:
- Bridge CS4 created an exported cache for a folder.
- Bridge CS5 encounters that folder and reads the exported cache, importing all the entries into the Bridge CS4 central cache.
- You put new files in the folder, or add a keyword or other metadata to an existing file.
- Bridge CS4 views the folder and generates thumbnails for the new files. And because Automatically Export Cache To Folders When Possible is selected, it updates the exported cache file.
- Bridge CS5 views the folder and ignores the exported cache file because it has already seen that folder. It generates thumbnails for the new files and adds them to the central cache.
If you don't want to fill disk space with exported caches for every folder Adobe Bridge views, deselect this option. You can export the cache manually for any individual folder by choosing Tools > Cache > Build And Export Cache. You could do this step, for example, before burning a folder to DVD.
Location shows the path to the central cache. The Adobe Bridge CS3 central cache is in a different location from Adobe Bridge CS4 and CS5. Adobe Bridge CS4 and CS5 do not read the central cache from Bridge CS3.
Each file and folder that Adobe Bridge caches uses one database record. A database record includes one or more JPEG files that Adobe Bridge generates to display thumbnails and previews. The cache can store to 500,000 records; the default cache size is 100,000 records. Increasing the cache size can improve performance, but a bigger cache uses more disk space.
Compacting the cache removes obsolete database records and the JPEG files associated with those records.
Purging the cache deletes all thumbnails and previews from the central cache.