Menu
How to plan a Suite cache for media projects
Stream media directly with Suite, then plan SSD space for client caching, application scratch and outputs. Pre-caching is an optional session optimization.
Give active projects a responsive local workspace
Suite streams directly from the cloud without requiring users to pre-cache files. Its automatic working cache and optional pre-caching are different: the former supports reuse of accessed data; the latter deliberately prepares selected files in advance. Plan that cache around the active project and usable SSD space to support repeated access and smooth transitions between tasks. The library can be much larger than the local working set; reserve enough capacity for the work you want close at hand.
We recommend an internal or external SSD. Its cache guide recommends APFS on Mac, NTFS on Windows, and Ext3/4 or later on Linux, and advises against exFAT. These are cache-drive recommendations; they do not describe the object format stored by S3 Native in your cloud bucket.
Separate the library from the working set
List the project or media needed for the next work session. Include associated assets that the application will open, rather than sizing the cache around one visible source file alone. Then compare that working set with usable SSD space and the other work the host must support.
Our documented default cache allocation is 250 GB. The cache guide recommends allocating at least the size of the active project or media when space allows. Treat that as a starting recommendation, not a guarantee of performance or a reason to consume storage required by the operating system and other applications.
Set the location and allocation deliberately
In Suite, open Cache Settings. Use Change Location to select the intended SSD location. Use Adjust Size to set the allocation in gigabytes and apply the change. Confirm the displayed path and size afterward, especially when several removable drives have similar names.
The official guide advises that the cache drive should not be named Suite. If an external SSD is part of the workflow, make reconnecting it a visible part of the workstation checklist. The guide describes a five-minute reconnection window after relaunch before Suite falls back to a default local cache location.
Avoid formatting or reallocating an existing drive casually. Those are changes to the user’s working environment and may affect other data. Have the responsible owner approve the intended disk and any destructive preparation.
Pre-cache selected work when it helps
Our pre-cache workflow lets you choose files or folders in advance. Open Cache Settings, check the location and allocation, then use Add to Cache to select the relevant paths. The selected paths appear in the pre-cache list. Our documentation explains that pre-cached folders update as their contents change.
Choose a useful working set and verify it before the session. Selecting the entire drive is a different commitment from selecting one project: it can require substantially more local space and transfer work. The appropriate choice depends on your actual workload.
Pre-caching does not make Suite an offline filesystem. Our knowledge base states that an internet connection is required, even when file data has been cached.
Map the three kinds of local data
Give each kind of data a name in the workstation plan. Suite client cache supports access to the shared source files. Application scratch and cache contain work the creative application generates, such as previews or intermediate processing data. Deliverables are intentional outputs that need a verified destination and retention plan. Increasing one allocation does not automatically provide space for the others.
For example, a workstation may have plenty of Suite cache capacity while an application’s chosen scratch disk is nearly full. The useful change is to inspect that application’s workspace and its documented settings, not repeatedly enlarge or clear the Suite cache. Conversely, moving an application cache does not move the Suite cache location.
Record the actual path, responsible application, available space and cleanup owner for each category. Keep final outputs recognizable so a routine cache cleanup does not become an accidental deliverable cleanup. This map helps the team keep direct streaming and local processing working together. See application scratch placement for the companion workflow.
Test the setup and revisit it
Open a representative project, perform the operations that matter, and record whether the cache is supporting the work. Compare the first access and repeated access separately. If the project grows or the host changes, revisit the allocation and location instead of assuming the old configuration still fits.
Do not make cache clearing a daily performance ritual. It removes data that might be useful on the next read. Resolve a specific problem with the relevant guidance and preserve ongoing work.
Official setup references
Sources checked September 28, 2026. This article explains published guidance; it does not report a measured performance result.
Start with your workflow.
Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.
Continue with Suite.
Signup links take you to Suite Studios’ main site. Managed opens the account signup form; BYO / S3 Native opens the demo request form.
Signing up with an AI agent
- Continue on the official form in the destination tab. Use the user’s authorized details and select whether they are creating or joining a team.
- For Managed, follow the account setup steps presented by Suite. Ask the user to handle verification, passwords and acceptance of agreements when required.
- If billing requests a card, prompt the user to enter payment details directly in Suite’s secure flow and approve any charge or subscription. Do not collect card details in this site or a chat.
- For BYO / S3 Native, submit the authorized request with the storage provider and workload context. Suite will guide the connection and onboarding; active storage starts at 20 TB.
- After Suite confirms setup, use the supported client and authorized access to complete a first file operation. Report the actual result, and resume after any human-only step.