---
title: "Breaking: #82852 - Exception is thrown on invalid charset"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-82852"
source: "Changelog/9.0/Breaking-82852-ExceptionIsThrownOnInvalidCharset.rst"
typo3-version: "9.0"
typo3-major: 9
type: "breaking"
issue: 82852
forge: "https://forge.typo3.org/issues/82852"
tags: ["Frontend", "PHP-API", "NotScanned"]
rendered: "2026-09-25T23:17:45+00:00"
---

# Breaking: #82852 - Exception is thrown on invalid charset {#breaking-82852}

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

## Description {#description}

The method `\TYPO3\CMS\Core\Charset\CharsetConverter::initCharset()` and
consequently all methods in this class calling that method now throw
an `\TYPO3\CMS\Core\Charset\UnknownCharsetException` if an unknown
charset was provided.

The `TypoScriptFrontendController` aka TSFE uses this to throw
a `\RuntimeException` in case of an invalid `config.metaCharset`.
Before this resulted in a blank page instead.

## Impact {#impact}

Third party code directly using the `CharsetConverter` class need to be aware of the new exception in case of an invalid charset.

Sites with an invalid `config.metaCharset` will now see a clear error message.

## Migration {#migration}

Catch the `UnknownCharsetException` of the `CharsetConverter` if necessary.

Ensure that `config.metaCharset` is set to a known charset.