SuiteFile streaming
Menu
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.

How it worksExplore Suite Managed
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

File streaming delivers requested file data through a filesystem, helping teams get to useful work sooner when applications read portions of large files. Suite combines a mounted cloud drive with a local working cache, so people can use familiar applications and shared projects across locations.

Application interface
A mounted filesystem
Data retrieval
As requested
Local storage
A working cache
01The mechanism

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. A cache supports the working set

    Local caching keeps file data available for reuse. Available cache space, the active working set and access patterns affect what needs to be fetched again.

  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.

02Compare approaches

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.

03Evaluate it

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.

04Where S3 Native fits

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.

05Questions, answered
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