Yes, MediaLab can keep the object layout in a storage container mirrored to your folder structure in MediaLab. When this is enabled on a container, moving or copying a file into a different folder automatically relocates (or duplicates) the underlying object in storage, so the container always reflects the same folder tree you see in MediaLab.

This works for cloud storage containers (S3, Azure Blob) as well as, on on-premise and hybrid platforms, network-attached storage (NAS, e.g. NFS or SMB).

This is an opt-in feature that needs to be requested through our service desk. It isn't turned on for storage containers by default.

Why it's opt-in

Normally, organizing files in MediaLab (moving them between folders, renaming folders, etc.) is a fast, database-only operation. It doesn't touch the underlying storage at all. Keeping the container's layout in sync changes that: every move or copy has to be followed by a real, network-bound operation against the storage (a cloud provider API call for S3/Azure, or an actual file operation over the network for NAS) to relocate or duplicate the object.

That makes folder-structure syncing meaningfully more expensive and slower than how MediaLab normally handles reorganizing media, especially at scale. Large folders, frequent reorganizing, or very large files all add up in extra storage operations (and, for cloud containers, potentially extra provider costs depending on your storage plan). Because of that, it's reserved for containers where it's actually needed, rather than being on by default.

It also turns off deduplication for copies

Normally, copying a file within MediaLab reuses the same underlying object in storage, so a copy doesn't result in any additional storage usage. With folder-structure syncing enabled, that's no longer possible: the copy needs its own object at its own mirrored path, so MediaLab always creates a real, separate copy in storage instead of sharing the original. This is worth factoring in if you copy files often, since it means real extra storage usage (and, for cloud containers, cost) that you wouldn't otherwise have.

Not compatible with the Archive add-on

Folder-structure syncing does not work together with MediaLab's Archive add-on. Files that are archived or restored go through the Archive feature's own storage process instead, so folder-structure syncing does not apply to them. If your workflow relies on archiving, talk to our service desk about whether folder-structure syncing is still a good fit for the rest of your storage.

When it makes sense

Folder-structure syncing is a good fit when something outside MediaLab needs the storage container to reflect your folder structure directly, for example:

• A separate tool, pipeline, or script that reads files straight from the bucket or NAS share and relies on the folder path to know where things are.
• Handing off storage to a partner, vendor, or external archive/backup system that expects a familiar folder layout.
• Contractual or internal requirements to keep storage organized the same way as your MediaLab folders.

If nothing outside MediaLab depends on the storage container's own folder layout, you generally don't need this. MediaLab already tracks and displays your folder structure regardless of how objects are laid out in storage.

Getting it enabled

Folder-structure syncing is configured per storage container. Contact our service desk to discuss your use case and have it enabled on the relevant container(s).

See also: Cloud storage support (S3 and Azure) for general information on setting up and managing cloud storage containers.