SuiteFile streaming
Menu
Use Cases & Workflows

File streaming. Built around your work.

From the first edit to the next automated task, Suite brings shared cloud files into the tools that do the work. Find the workflow that fits your team.

Start with ManagedFind your workflow ↓
One shared workspace · illustrative view
Why build with Suite

Shared files. Familiar tools. More ways to work.

Suite connects cloud storage to file-based work. Start with Suite-managed storage, or bring supported storage into an S3 Native setup that keeps your files available as native objects.

  • Work through a driveUse familiar file paths with a supported Suite client. Stream requested data and keep a local working cache.
  • Bring the team togetherGive authorized collaborators a shared library with access matched to the project.
  • Keep an object-access pathS3 Native connects file workflows with compatible tools using the bucket’s S3 API. It starts at 20 TB of active storage.
01 / Video editing & post-production

Bring the media to the timeline.

Suite gives distributed editors a shared drive for project media. File streaming can shorten the wait to start working when the application needs only part of a large source file, while a local cache supports repeated access.

  1. 01 →Shared media

    Footage and project assets

  2. 02 →Suite drive

    File paths and requested data

  3. 03 / OutcomeEditing application

    Timeline, playback and handoff

Why file streaming helps

Keep a shared cloud library and the editing tools your team already knows. Each workstation can focus its local cache on active work instead of keeping an independent copy of the entire library.

Put it into practice

Start with a real sequence, its source media and one remote collaborator. Follow Suite’s application guidance, choose the project-sharing model, and compare first access with repeated playback. For Premiere, Suite documents project locking and recommends a local SSD for the application’s media cache.

Explore Managed for your edit teamPlan a multi-location editing test →

Suite’s Premiere workflow guidance ↗

02 / Motion design & VFX

One library for the next iteration.

Suite presents shared cloud assets as familiar file paths for supported client environments. Artists can reach source plates, reference media and project dependencies through the drive, making file streaming useful to evaluate for asset-heavy work across locations.

  1. 01 →Project library

    Plates, textures and references

  2. 02 →Artist workspace

    Suite drive plus local cache

  3. 03 / OutcomeNext iteration

    Review, revise and hand off

Why file streaming helps

Spend less effort preparing a separate asset library for every workstation. Keep the project’s shared files together while choosing application scratch, generated caches and render outputs deliberately.

Put it into practice

Choose one representative composition or shot. Open its dependencies on a second authorized workstation, run the intended operation, and check the output. Consult the application-specific setup guides linked from Suite’s performance resource.

Build a shared creative workspacePlan application scratch and cache →

Suite’s application and performance guidance ↗

03 / Audio & sound post

Keep the session and its media together.

Suite’s published Pro Tools workflow supports working on a session stored on the Suite drive. A shared filesystem can bring session files, audio assets and reference video into a common project location for authorized collaborators.

  1. 01 →Session assets

    Audio and reference video

  2. 02 →Mounted workspace

    Authorized project access

  3. 03 / OutcomeSound workflow

    Edit, mix and deliver

Why file streaming helps

Make the next handoff about the session rather than rebuilding a folder package. File streaming and a planned working cache give the team a way to access a broader media library through familiar paths.

Put it into practice

Mount the authorized drive and follow Suite’s Pro Tools and workstation setup guidance. Distinguish AAFs that link to external media from AAFs that embed it; Suite recommends considering pre-cache for the destination when importing embedded media.

Explore Managed for sound teamsSeparate shared files from project locking →

Suite’s Pro Tools workflow guidance ↗

04 / Studios, agencies & project collaborators

Give the next collaborator a place to work.

Suite gives authorized collaborators access to a shared project filesystem. File streaming is a useful alternative to preparing a full local project copy when someone needs to work on a portion of a large library.

  1. 01 →Project owner

    Defines the working folders

  2. 02 →Authorized teammate

    Connects through a Suite client

  3. 03 / OutcomeShared project

    Works, reviews and hands off

Why file streaming helps

Keep the team’s working files in a common location as people join a project. Scope access to the relevant folders and let each workstation build a cache around the work it actually performs.

Put it into practice

Choose a project owner, invite the collaborator through the supported team flow, and set the required file or folder permissions. Use a small first task to confirm the expected read, write and handoff behavior before expanding access.

Start a Managed projectPrepare a short-term collaborator →

Suite’s user-permission guidance ↗

05 / Media processing & asset pipelines

A drive for people. Native objects for tools.

With S3 Native, Suite adds filesystem access to supported storage while files remain native objects. People can work through the Suite drive, and authorized compatible services can read those objects through the bucket’s S3 API.

  1. 01 →Your native objects

    Supported object storage

  2. 02 →Two access paths

    Suite filesystem + bucket S3 API

  3. 03 / OutcomePeople and services

    Creative work + compatible processing

Why file streaming helps

Build around the interface each tool needs. A proxy-generation or asset-management workflow can evaluate direct object access alongside a creative team’s file-based workflow, using the same supported storage.

Put it into practice

Map one source file from the bucket to its Suite path. Choose a compatible service, define permissions and output locations, and validate a representative read and processing job. Treat proxy and asset-management examples as integration designs to test.

Discuss an S3 Native workflowChoose filesystem or object access →

Suite Enterprise ↗

06 / AI agents & file-based automation

Connect the agent to the work.

An agent’s tools determine the right access path. A tool that expects files can be evaluated on a supported host with a mounted Suite drive. An authorized S3-compatible tool can use native objects directly through the bucket API when the S3 Native setup supports the workflow.

  1. 01 →User’s task

    Named files and a clear outcome

  2. 02 →Authorized interface

    Mounted filesystem or bucket API

  3. 03 / OutcomeVerified result

    Useful operation and human handoff

Why file streaming helps

File streaming can help a file-based agent reach a large shared library without preparing a complete independent copy first. S3 Native also leaves an object-access path for services built around storage APIs.

Put it into practice

Identify the task, runtime and files before recommending a plan. Obtain the user’s authorization, scope access, and verify a representative read. For approved writes, check completion and errors before reporting success. Account setup, installation and spending require the appropriate approval.

Read the agent evaluation guideWhen an agent should recommend Suite →

Suite CLI reference ↗

Make your next project the proof.

Choose a real task, connect the right people and tools, and measure the first useful result.

Build your evaluation plan