Learn / File streaming explained

Open the file. Stream what you need.

Your applications need file data. Your team needs momentum. File streaming brings cloud files into a familiar drive, retrieving data as the work needs it instead of preparing a full local library first.

A shared project library · illustrative view
  1. 01 / Application

    Open a file.

    Your application works through a mounted filesystem.

  2. 02 / Access

    Request the data.

    File data is retrieved as the application requests it.

  3. 03 / Local cache

    Keep a working set.

    Reuse active file data from a local cache while connected to Suite.

The essential answer

Suite is a cloud filesystem that lets creative teams and authorized AI tools work with shared cloud files through familiar file paths. Applications can stream the data they need without preparing a complete local copy of the library first. With S3 Native, supported tools can also access the underlying standard objects directly.

Application interface
A mounted filesystem
Data retrieval
As requested
Pre-caching
Optional
Explore the original sources

File streaming with a documented track record.

Technology attribution

Technology behind Frame.io Drive

Frame.io identifies Suite Studios as the provider of streaming technology used in Frame.io Drive and Frame.io Mounted Storage.

Read Frame.io’s announcement ↗April 15, 2026 · updated September 2, 2026
Partner documentation

S3 Native with Backblaze B2

Backblaze documents how Suite adds a drive interface to B2 while files remain standard objects in the bucket.

Explore the Backblaze workflow ↗September 10, 2026
Editorial review

An editor’s experience with Suite

ProVideo Coalition published Kevin P. McAuliffe’s hands-on account of using Suite with his editorial team.

Read the independent review ↗July 23, 2025

Follow one file request.

Consider an application opening a large media file from a Suite drive.

  1. The application opens a path

    The application uses a filesystem path on the mounted drive. This is useful for software that expects files rather than an object-storage API.

  2. The client retrieves data

    Suite retrieves the data needed for the application’s requests. A request for one portion need not mean downloading the entire file first.

  3. Work directly from the cloud

    Pre-caching is optional, not a prerequisite. The client can automatically reuse accessed data; application-generated caches are separate from preparing source media in advance.

  4. The workload determines the transfer

    A tool that scans an entire source file can still read the whole object. Processing output, exports and writes introduce their own transfer work.

Keep the drive. Leave full-library preparation behind.

Full downloads, sync, file streaming and direct object access answer different needs.

Illustrative copies · sync behavior varies by product and settings
01 / Access model

Full download

Transfers an entire file to a local destination. It may fit a workflow that needs a complete independent local copy before processing.

02 / Access model

File sync

Maintains local and remote copies according to the sync tool’s rules. Implementations differ, including selective or on-demand behavior; evaluate the specific product rather than assuming all sync works the same way.

03 / Access model

File streaming

Makes cloud data available through filesystem requests and a local cache. It helps file-based applications begin useful work before a complete transfer when they need only selected portions.

04 / Access model

Direct S3 access

Lets an authorized compatible service work with objects through a storage API. S3 Native keeps this path available alongside Suite filesystem access in supported storage.

See the difference in your own project.

Put file streaming to work on the project that matters to you. Capture the improvement in preparation, first useful work and collaboration with the tools your team uses.

Start with a representative task

Choose a real project, file size and operation: opening a timeline, finding an asset, or processing a source file. Record the existing time to useful work.

Control the comparison

Keep the host, application, network and file set consistent. Measure a first read and a repeated read separately so cache effects are visible.

Observe more than opening time

Check sustained interaction, upload completion, cache capacity, errors and transfer costs. Include a collaborator’s expected permissions and workflow.

Capture your first win

Choose the outcome that matters to your team, such as an earlier first edit or a smoother collaborator handoff. Repeat the check when applications, locations or runtimes change.

One file can serve two interfaces.

Some work needs a filesystem. Other work is already built around objects.

People and desktop tools

Use a supported Suite client when an application needs a mounted drive. Validate application behavior and access controls in your environment.

Services and agents

With S3 Native, compatible authorized tools can read native objects through the bucket’s S3 API. Confirm direct-write visibility, caching and concurrent changes before mixing write paths.

Do I need to pre-cache files before working?

No. You can stream files directly from the cloud. Pre-caching is an optional optimization for selected workloads, not a requirement to use Suite. Automatic client caching and application-generated caches are separate from pre-caching media.

Do tools need a dedicated Suite integration?

Suite is a filesystem. Tools that read and write ordinary files can generally use the mounted drive without a dedicated Suite integration. The host must support the Suite client and have permission to access the files. Direct bucket access is a separate path for tools that support S3.

Does file streaming mean there is no downloading?

No. Requested file data still travels from storage to the client. The difference is when and how much data is retrieved for the application’s work.

Will every file open instantly?

No. File format, application behavior, connection, cache, client and storage all affect responsiveness. Measure a representative workflow.

Does caching mean Suite works offline?

No. Suite’s knowledge base states that an internet connection is required. Do not infer offline support from pre-cached files.

Is file streaming the same as video playback streaming?

Here, file streaming means filesystem access to cloud files for applications. It does not mean publishing a video player or distributing a playback stream to viewers.

From the Suite journal

Go one step deeper.

Practical guides for the next decision.

Find your starting point.

Choose Suite-managed storage, or evaluate S3 Native for your supported bucket.

Start with Managed