---
title: "Using site configuration in TypoScript and Fluid templates"
manual: "TYPO3 Explained"
version: "main"
permalink: "https://docs.typo3.org/permalink/t3coreapi:sitehandling-intyposcript@main"
source: "ApiOverview/SiteHandling/UseSiteInTypoScript.rst"
modified: "2026-09-16T13:05:25+00:00"
---

# Using site configuration in TypoScript and Fluid templates

## `getText`

Site configuration can be accessed via the [site](https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Functions/Data.html#data-type-site) property in TypoScript.

Example:

```typoscript
page.10 = TEXT
page.10.data = site:base
page.10.wrap = This is your base URL: |
```

Where `site` is the keyword for accessing an aspect, and the following parts are the
configuration key(s) to access.

```typoscript
data = site:customConfigKey.nested.value
```

To access the current siteLanguage use the [siteLanguage](https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Functions/Data.html#data-type-siteLanguage) prefix:

**EXT:my_extension/Configuration/Sets/MyExtension/setup.typoscript (excerpt)**

```typoscript
page.10 = TEXT
page.10.data = siteLanguage:navigationTitle
page.10.wrap = This is the title of the current site language: |

page.20 = TEXT
page.20.dataWrap = The current site language direction is {siteLanguage:direction}

# ...

```

> [!TIP]
> Accessing site configuration is possible in TypoScript, which enables to store site specific configuration options
> in one central place (the site configuration) and allows usage of that configuration from different contexts.
> While this sounds similar to using TypoScript constants, site configuration
> values may also be used from backend or CLI context as long as the rootPageId of a site is known.

Site configuration can also be used in [TypoScript conditions](https://docs.typo3.org/permalink/t3coreapi:sitehandling-inconditions@main) and as
[TypoScript constants](https://docs.typo3.org/permalink/t3coreapi:sitehandling-settings@main).

## FLUIDTEMPLATE

You can use the SiteProcessor in the [FLUIDTEMPLATE](https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/ContentObjects/Fluidtemplate/Index.html#cobj-fluidtemplate) content object
to fetch data from the site entity:

**EXT:my_extension/Configuration/Sets/MyExtension/setup.typoscript (excerpt)**

```typoscript
tt_content.mycontent.20 = FLUIDTEMPLATE
tt_content.mycontent.20 {
  file = EXT:my_extension/Resources/Private/Templates/ContentObjects/MyContent.fluid.html

  dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\SiteProcessor
  dataProcessing.10 {
    as = site
  }
}

# ...

```

In the Fluid template the properties of the site entity can be accessed with:

```html
<p>{site.rootPageId}</p>
<p>{site.configuration.someCustomConfiguration}</p>
```

Specific [Site settings](https://docs.typo3.org/permalink/t3coreapi:sitehandling-settings@main) can be accessed via:

```html
<p>{site.configuration.settings.mySettingKey}</p>
<p>{site.settings.all.mySettingKey}</p>
```

## Non-Extbase Fluid view

> [!NOTE]
> **Changed in version 14.0**
>
> The `StandaloneView` was deprecated with
> TYPO3 v13.3 and has been removed with v14.0. Use a
> `ViewInterface` instance provided by the
> [The Site object](https://docs.typo3.org/permalink/t3coreapi:sitehandling-site-object@main).

In a non-Extbase Fluid view (`\TYPO3\CMS\Core\View\ViewInterface`), created
manually by the [Using the generic view factory (ViewFactoryInterface)](https://docs.typo3.org/permalink/t3coreapi:generic-view-factory@main), you can use the PHP API to access the
site settings (see [The Site object](https://docs.typo3.org/permalink/t3coreapi:sitehandling-site-object@main)), then assign that object
to your Fluid standalone template, and finally access it through the same
notation in the [Fluid template of a FLUIDTEMPLATE](https://docs.typo3.org/permalink/t3coreapi:sitehandling-fluidtemplate@main).