Configuring file storage

Learn how to configure where your local files should go using a storage scenario.

Fredrik Limsater avatar
Written by Fredrik Limsater
Updated over a week ago

ftrack is tracking your files as Asset versions and Components. A Component represents the existence of a file, but does not tell your where the data is located. To keep track of this ftrack uses the concept of Locations.

To simplify the setup of locations a Storage scenario can be used instruct ftrack on how your files should be stored when publishing from ftrack connect or integrations.

When starting ftrack connect for the first time you will be asked to Configure a storage scenario.

Configuring storage scenario

A storage scenario can be configured to instruct ftrack on how your files should be stored and tracked.

The active storage scenario can be configued from System Settings ‣ Media Management ‣ storage scenario. To configure a storage scenario you will need to have ftrack connect running.

If you’ve already configured a storage scenario you will see the name of the currently active scenario.

You can also see the JSON parameters of the scenario, for advanced users and developers this may be good for debugging purposes.

If you haven’t already configured a scenario or want to update an existing scenario you can press Configure Storage Scenario. From here you will be able to select from a list of storage scenarios.


I cannot see anything in the Select storage scenario dropdown
Make sure that you have ftrack connect started and that you are properly logged in with a API key. 

Files are not being published using my newly configured storage scenario
Make sure to restart ftrack connect and any other applications that communicates with ftrack after configuring. This is necessary in order for the new storage scenario to become available.

Centralized storage scenario

By default ftrack comes with a Centralised storage scenario.

The centralized storage scenario is suitable for studios with one central storage where published files are stored.

The centralised storage scenario will copy your published files into a folder structure generated from the object names where the Asset version is published, along with the Asset name and version number.

As an example we can say that you have a project named CarCommerical with a folder called Images. Now you publish a file component named front.png on an asset named DarkImage. It becomes version 3 of the asset and will yield a path:


Configured correctly ftrack will know where the storage is mounted on your machine and produce a file path suitable for your OS:


The storage that you intend to save your files on must be mounted and available on all computers that need to publish and import data.

Did this answer your question?