Storage Options

The bundle ships two storage drivers:

filesystem
google_cloud_storage

Both implement the same storage contract, so the rest of the bundle can keep the same behavior.

Filesystem Storage

YAML

sfs_media:
    driver: filesystem
    filesystem:
        path: '%kernel.project_dir%/public/media'
        url: '/media'

PHP

<?php

// config/packages/sfs_media.php
namespace Symfony\Component\DependencyInjection\Loader\Configurator;

return static function (ContainerConfigurator $container): void {
    $container->extension('sfs_media', [
        'driver' => 'filesystem',
        'filesystem' => ['path' => '%kernel.project_dir%/public/media', 'url' => '/media'],
    ]);
};

This is the simplest setup for:

local development
small and medium applications
environments where media files live directly under the application public path

The driver stores internal URLs with the sfs-media-filesystem:// prefix and can translate them to public URLs later.

Google Cloud Storage

YAML

sfs_media:
    driver: google_cloud_storage
    google_cloud_storage:
        bucket: '%env(MEDIA_BUCKET_NAME)%'

PHP

<?php

// config/packages/sfs_media.php
namespace Symfony\Component\DependencyInjection\Loader\Configurator;

return static function (ContainerConfigurator $container): void {
    $container->extension('sfs_media', [
        'driver' => 'google_cloud_storage',
        'google_cloud_storage' => ['bucket' => '%env(MEDIA_BUCKET_NAME)%'],
    ]);
};

This is the better fit when:

media should live outside the application container or host
several app instances share the same storage
deployment and media lifetime must be decoupled

Stored URLs use the gs://bucket/path format internally and the driver exposes them as standard Google Storage HTTPS URLs.

Driver Responsibilities

Both drivers implement:

store()
remove()
download()
url()

That is important because regeneration and migration may need to download the original file again even long after the first upload.

Private Media Caveat

private: true marks media as private in the entity and is used in some admin and search flows.

It does not provide a signed-URL delivery layer or a full secure asset access system by itself.

Configured Public URLs

Rendering resolves stored URLs through the configured storage driver. A custom filesystem.url or Google Cloud Storage public base URL applies to images, responsive sources and fallbacks, videos, and posters.

For delayed deletion and the required bucket lifecycle rule, see Delayed Google Cloud Storage deletion.