TYPO3 v10 has reached end-of-life as of April 30th 2023 and is no longer being maintained. Use the version switcher on the top left of this page to select documentation for a supported version of TYPO3.

Need more time before upgrading? You can purchase Extended Long Term Support (ELTS) for TYPO3 v10 here: TYPO3 ELTS.


What is TSFE?

TSFE is short for \TYPO3\CMS\Frontend\Controller\TypoScriptFrontendController, a class which exists in the system extension EXT:frontend.

As the name implies: A responsibility of TSFE is page rendering. It also handles reading from and writing to the page cache. For more details it is best to look into the source code.

There are several contexts in which the term TSFE is used:

  • PHP: It was and is available as global array $GLOBALS['TSFE'] in PHP.

  • TypoScript: TypoScript function TSFE which can be used to access public properties in TSFE.

  • (deprecated since v9.5 and removed in 10.0) Page TSconfig: TSFE.constants.

The TypoScript part is covered in the TypoScript Reference: TSFE. In this section we focus on the PHP part and give an overview, in which way the TSFE class can be used.

Accessing TSFE


Some of the former public properties and methods have been changed to protected or marked as internal. Often, accessing TSFE is no longer necessary, and there are better alternatives.

Access $GLOBALS['TSFE'] directly only as a last resort, usage is strongly discouraged, if not absolutely necessary.

From the source:

When calling a frontend page, an instance of this object is available as $GLOBALS['TSFE'], even though the Core development strives to get rid of this in the future.

TSFE is not available in all contexts. In particular, it is only available in frontend contexts, not in the backend or CLI.

Initializing $GLOBALS['TSFE'] in the backend is sometimes done in code examples found online. This is not recommended. TSFE is not initialized in the backend context by the Core (and there is usually no need to do this).


Following are some examples which use TSFE and alternatives to using TSFE, where available:

Access ContentObjectRenderer

Access the \TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer (often referred to as "cObj"):

// !!! discouraged
$cObj = $GLOBALS['TSFE']->cObj;

In the case of user function (for example, a non-Extbase plugin) via setter injection:

public function setContentObjectRenderer(ContentObjectRenderer $cObj): void
    $this->cObj = $cObj;

Access current page ID

Access the current page ID:

// can be used in TYPO3 version 10
$pageId = $GLOBALS['TSFE']->id;

Access language settings

In order to get current language settings, such as the current language ID, obtain \TYPO3\CMS\Core\Site\Entity\SiteLanguage object from the request attribute 'language':

// can still be used, but will be deprecated
$languageId = $GLOBALS['TSFE']->sys_language_uid;

Accessing language settings can be done using the language aspect.

Get the language of the current page as integer:

$languageId = (int) $context->getPropertyFromAspect('language', 'id');

Access frontend user information

// TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication
$feUser = $GLOBALS['TSFE']->fe_user;

Some information via frontend and backend users con be obtained via the user aspect. For example:

// return whether a frontend user is logged in
$context->getPropertyFromAspect('frontend.user', 'isLoggedIn');

Get current base URL

It used to be possible to get the base URL configuration (from TypoScript config.baseURL) with the TSFE baseURL property. The property will be deprecated in TYPO3 v12. Already in earlier version, site configuration should be used to get the base URL of the current site.

// !!! will be deprecated
// TYPO3\CMS\Core\Site\Entity\Site
$site = $request->getAttribute('site');
// array
$siteConfiguration = $site->getConfiguration();
$baseUrl = $siteConfiguration['base'];