---
title: "Feature: #110775 - Structured text extraction in TextExtractorRegistry"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-110775-1790261961"
source: "Changelog/15.0/Feature-110775-StructuredTextExtractionInTextExtractorRegistry.rst"
typo3-version: "15.0"
typo3-major: 15
type: "feature"
issue: 110775
forge: "https://forge.typo3.org/issues/110775"
tags: ["FAL", "PHP-API", "ext:core"]
rendered: "2026-11-14T17:17:53+00:00"
---

# Feature: #110775 - Structured text extraction in TextExtractorRegistry {#feature-110775-1790261961}

See [forge#110775](https://forge.typo3.org/issues/110775)

## Description {#description}

Text extractors, used to extract the textual content from files, can now
also provide the metadata they find in a file, declare the MIME types they
support, and work on any system resource: files of a FAL storage as well as
files of packages or public files outside of any storage.

A text extractor implementing the new interface
`\TYPO3\CMS\Core\Resource\TextExtraction\StructuredTextExtractorInterface`
receives a `\TYPO3\CMS\Core\SystemResource\Type\SystemResourceInterface`
and returns an `\TYPO3\CMS\Core\Resource\TextExtraction\ExtractedText`
object, which holds the text together with a title, a description and
keywords. FAL files implement `SystemResourceInterface`, so the same
extractor serves both:

**EXT:my_extension/Classes/Resource/TextExtraction/PdfTextExtractor.php**

```php
use TYPO3\CMS\Core\Attribute\AsTextExtractor;
use TYPO3\CMS\Core\Resource\TextExtraction\ExtractedText;
use TYPO3\CMS\Core\Resource\TextExtraction\StructuredTextExtractorInterface;
use TYPO3\CMS\Core\SystemResource\Type\SystemResourceInterface;

#[AsTextExtractor(priority: 10)]
final class PdfTextExtractor implements StructuredTextExtractorInterface
{
    public function getSupportedMimeTypes(): array
    {
        return ['application/pdf'];
    }

    public function extractStructuredText(SystemResourceInterface $resource): ExtractedText
    {
        // Read $resource->getContents() ...
        return new ExtractedText($text, $title, $description, $keywords);
    }
}
```

`getSupportedMimeTypes()` returns the lowercase MIME types which the
extractor can currently handle. The registry selects the extractor by the MIME
type of the resource, not by its file extension. An extractor that depends on
an external tool returns an empty list as long as the tool is not available.
This allows to list the supported file types without having a file at hand,
for example to offer them in a search form.

File types which are detected differently depending on the environment, for
example Office Open XML documents detected as ZIP archives, are resolved to one
MIME type by the file extension through the existing setting
`$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['mimeTypeCompatibility']`,
so an extractor only declares the official MIME type. FAL applies the setting
when it detects the MIME type of a file. The registry applies it as well, if
no extractor supports the stored MIME type, so files indexed before an entry
was added are found without updating the file index. The default entries for
Office documents are described in [Important: #111287 - Office documents detected as container format are accepted](https://docs.typo3.org/permalink/changelog:important-111287-1793349163).

The `\TYPO3\CMS\Core\Resource\TextExtraction\TextExtractorRegistry`
provides three new methods:

-   `findTextExtractor(FileInterface|SystemResourceInterface $resource)`
    returns the extractor responsible for the resource. All extractors are
    asked in the order of their `#[AsTextExtractor]` priority, whichever
    interface they implement: a structured extractor matches if it supports
    the MIME type of the resource, any other extractor if its
    `canExtractText()` accepts the FAL file. A MIME type mapped by
    `mimeTypeCompatibility` is only considered if no extractor matches.
-   `extract(FileInterface|SystemResourceInterface $resource): ?ExtractedText`
    extracts the text with the extractor returned by
    `findTextExtractor()`. The text of an extractor implementing only
    `TextExtractorInterface` is wrapped into an `ExtractedText`
    object. A file reference is resolved to its original file.
-   `getSupportedFileExtensions(): array` returns the file extensions
    known for the MIME types declared by all registered structured text
    extractors, for consumers that offer file types for selection.

The `PlainTextExtractor` shipped with TYPO3 Core implements both
interfaces and declares the MIME type `text/plain`.

The interface `TextExtractorInterface`, the method
`TextExtractorRegistry->getTextExtractor()` and the attribute
`#[AsTextExtractor]` are unchanged, so existing text extractors and their
consumers keep working. Both interfaces stay supported in TYPO3 v15, because
existing consumers call `getTextExtractor()` and expect a
`TextExtractorInterface`, while `findTextExtractor()` and
`extract()` serve extractors of both interfaces.

New text extractors should implement `StructuredTextExtractorInterface`.
Implement `TextExtractorInterface` in addition only if the extractor
shall also be returned by `getTextExtractor()`, as the extractors shipped
with TYPO3 do.

## Impact {#impact}

Consumers of text extractors, such as the search indexing of
[`typo3/cms-indexed-search`](https://packagist.org/packages/typo3/cms-indexed-search), can use the title, description and
keywords of a file, for example to weight them higher than the body text, and
can extract the text of files that are not part of a FAL storage. Extension
authors can implement `StructuredTextExtractorInterface` to provide these
values, and to make the file types they support visible to consumers.
