---
title: "TypoScript module (Site management)"
manual: "Getting Started"
version: "13.4"
permalink: "https://docs.typo3.org/permalink/t3start:site-management-typoscript@13.4"
source: "Concepts/Backend/SiteManagement/TypoScript.rst"
rendered: "2026-10-01T16:43:19+00:00"
---

# TypoScript module (Site management) {#site-management-typoscript}

The TypoScript backend module can be used to debug the TypoScript configuration
that you provided via your site as described in
["Hello world" example in TypoScript](https://docs.typo3.org/permalink/t3start:typoscript-hello-world@13.4)
or via your site set as described in the Site Package Tutorial, chapter
[The TypoScript-only version](https://docs.typo3.org/m/typo3/tutorial-sitepackage/13.4/en-us/MinimalExample/Index.html#make-typoscript-available).

Before TYPO3 v13, TypoScript was set in database records called "TypoScript
records". It is still possible to do this, and you will see it in older documentation
and installations that have been updated but not yet refactored. The TypoScript
backend module can be used to manage these TypoScript records, see
the TypoScript Reference in chapter
[TypoScript backend module](https://docs.typo3.org/m/typo3/reference-typoscript/13.4/en-us/UsingSetting/Entering.html#typoscript-syntax-typoscript-templates-structure).

In the context of this guide, we concentrate on the new way of providing TypoScript
via the site.

The TypoScript module consists of the following submodules. You can switch them
in the docheader:

![Screenshot of the TypoScript module in the backend demonstrating the location of the submodule switch, a drop down in the document header](../../../Images/ManualScreenshots/Modules/TypoScript.png)

-   [TypoScript Overview](https://docs.typo3.org/permalink/t3start:typoscript-overview@13.4)
-   [Constant Editor](https://docs.typo3.org/permalink/t3start:constant-editor@13.4)
-   [Edit TypoScript record](https://docs.typo3.org/permalink/t3start:edit-typoscript-record@13.4)
-   [Active TypoScript](https://docs.typo3.org/permalink/t3start:active-typoscript@13.4)
-   [Included TypoScript](https://docs.typo3.org/permalink/t3start:included-typoscript@13.4)

## TypoScript Overview {#site-management-typoscript-overview}

Global overview of all pages with active TypoScript definitions (TypoScript
records and site sets). Useful if you have more than one site or more than one
TypoScript record in one site.

## Constant Editor {#site-management-typoscript-constant-editor}

Before site settings were introduced in TYPO3 13, TypoScript constants were
values that were defined in one place that could then be reused across TypoScript definitions.

Constants can still be used for backward compatibility reasons, but the
Constant Editor is not available if you are using site sets. Unlike
site settings, TypoScript constants are only available in TypoScript.

It is therefore recommended to always use site settings.

## Edit TypoScript record {#site-management-typoscript-record-editor}

Only available if TypoScript records are being used. This module can be used to
edit those records. Since this guide focuses on managing TypoScript within the site,
this module is out of scope. For further information about TypoScript records,
see the TypoScript reference,
chapter [Submodule "Edit TypoScript Record"](https://docs.typo3.org/m/typo3/reference-typoscript/13.4/en-us/UsingSetting/Entering.html#typoscript_module_edit).

## Active TypoScript {#site-management-typoscript-active}

This module can be used to debug active TypoScript. During loading and
pre-compiling, TypoScript configuration can override or unset definitions made in
another file.

How exactly this happens depends on things like dependencies between the used
site sets.

For example, if a site set in your site package configures:

**EXT:my_sitepackage/Configuration/Sets/SitePackage/setup.typoscript**

```typoscript
page.20 = TEXT
page.20.value = Apple
```

And the set of another extension configures:

**EXT:my_extension/Configuration/Sets/BananaSet/setup.typoscript**

```typoscript
page.20 = TEXT
page.20.value = Banana
```

It depends on how these sets are loaded whether the `page.20.value` ends up
being set to "Banana" or "Apple".

If the site set of our site package **depends** on the Banana set, the
SitePackage set **overrides** the Banana set and the Active TypoScript submodule
will show you the value "Apple" while it never mentions Banana.

This module therefore shows you the compiled version of the TypoScript.

The module can also be used to simulate what happens if certain
[TypoScript Conditions](https://docs.typo3.org/m/typo3/reference-typoscript/13.4/en-us/Syntax/Conditions/Index.html#typoscript-syntax-implementing-custom-conditions)
are being met or how site settings / TypoScript constants are replaced.

Chapter [Debug the TypoScript in the backend module "Active
TypoScript"](https://docs.typo3.org/permalink/t3start:typoscript-active-debug@13.4) demonstrates the usage of this module in
a concrete example.

## Included TypoScript {#site-management-typoscript-included}

This submodule is helpful in debugging in which order TypoScript files were
included and [@import](https://docs.typo3.org/m/typo3/reference-typoscript/13.4/en-us/Syntax/FileImports/Index.html#typoscript-syntax-import) statements were
resolved.

If the "Banana" from the example in
[Active TypoScript](https://docs.typo3.org/permalink/t3start:site-management-typoscript-active@13.4)
was overridden, you can use this module to find out where it might have been
overridden.

This module is also described in the TypoScript reference, chapter
[Submodule "Included TypoScript"](https://docs.typo3.org/m/typo3/reference-typoscript/13.4/en-us/UsingSetting/Entering.html#typoscript-syntax-typoscript-templates-structure-analyzer).