#107951Feature : Introduce a Digital Asset Provider API in TYPO3 Core
Description
Problem
Currently, TYPO3 does not provide a standard mechanism to integrate external media or asset libraries such as Shutterstock, iStock, Unsplash, or internal DAM/PIM systems.
Editors can only browse files that are already available through the File Abstraction Layer (FAL) — either stored locally or in connected storages.
Several third-party extensions (for example, https://github.com/ideativedigital/stock-pictures) attempt to fill this gap by providing integrations with stock photo services.
However, these solutions have to re-implement Core logic (File Browser, metadata handling, authentication, etc.) and cannot provide a fully consistent user experience.
As a result:
- Developers duplicate similar logic across extensions.
- Editors experience inconsistent interfaces when selecting external assets.
- Integrations are fragile and hard to maintain with each Core update.
Proposed Solution
Introduce a new Digital Asset Provider API in TYPO3 Core.
This API would define a generic and extensible interface that allows TYPO3 to connect to external digital asset libraries while keeping a consistent Core-level user experience.
Concept
- Define a DigitalAssetProviderInterface describing methods for:
- searching assets (with pagination and filters)
- retrieving metadata (title, description, license, preview URL, etc.)
- retrieving or importing asset files
- Introduce a registry mechanism for providers, so extensions can register their services declaratively (e.g., via Symfony service tags).
- Extend the File Selector / Element Browser to display digital asset providers alongside existing FAL storages.
- Ensure unified UX and metadata mapping between local and external assets.
- Allow two usage modes:
- Import mode : download the asset and store it in FAL.
- Reference mode : store only the remote reference and metadata.
Developer Perspective
Third-party extensions would only need to:- Implement the provider interface.
- Handle authentication and API communication with the external service.
- Return standardized asset data to the Core.
Everything else — UI integration, preview rendering, metadata mapping — would be handled by the Core.
Affected Parts
- Backend File Selector / Element Browser (UI layer).
Example Use Cases
- Editors can search for images in Shutterstock or iStock directly from the File Selector, preview them, and import or reference them.
- Integrators can connect TYPO3 to an internal Digital Asset Management (DAM) system using the same API.
- Organizations can connect cloud asset repositories (e.g., S3-based or proprietary) with minimal custom code.
Benefits
- Unified experience for all digital asset sources.
- Reduced code duplication across integrations.
- Easier development and long-term maintenance of external asset connectors.
- Future deprecation of stock-pictures and similar extensions in favor of the Core API.
References
Existing extensionsReviews 1
History 46
-
Presedo Roberto changed description <span data-processor="relativetime" data-value="2025-10-31T10:44:51+00:00" > 10/31/25, 10:44 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 91409 status
NewUnder Review <span data-processor="relativetime" data-value="2025-11-03T14:07:33+00:00" > 11/03/25, 14:07 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91409 <span data-processor="relativetime" data-value="2025-11-03T16:19:21+00:00" > 11/03/25, 16:19 </span>
-
Oliver Hader changed target version <span data-processor="relativetime" data-value="2026-01-23T12:29:53+00:00" > 01/23/26, 12:29 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-03-31T09:05:28+00:00" > 03/31/26, 09:05 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:01+00:00" > 04/21/26, 11:23 </span>