TYPO3 v9 has reached its end-of-life September 30th, 2021 and is not maintained by the community anymore. Looking for a stable version? Use the version switch on the top left.

You can order Extended Long Term Support (ELTS) here: TYPO3 ELTS.

Moving Repeating Snippets To Partials

Some parts within different Templates might be the same. In order to not repeat this part in multiple templates, Fluid offers so called Partials. Partials are small pieces of Fluid template within a separate file that can be included in multiple Templates.

For example, an extension might display tags inside an Resources/Private/Templates/RecordType/Index.html template and also in Resources/Private/Templates/RecordType/Show.html. The snippet to display these tags might look like:

<b>Tags</b>: <f:for each="{tags}" as="tag">{tag}</f:for>

If this is to be changed, e.g. an ul is preferred some day, the modifications would have to be made in both templates.

That's where Partials are used. Partials are stored, by default, within Resources/Private/Partials/. One might create a new Partial Resources/Private/Partials/Tags.html with the snippet:

<b>Tags</b>: <f:for each="{tags}" as="tag">{tag}</f:for>

Inside the existing Template the snippet can now be replaced with a ViewHelper to render the Partial:

{f:render(partial: 'Tags', arguments: {
    tags: post.tags

Fluid will replace the ViewHelper call with the result of the rendered Partial. The argument "partial" receives the full path within the configured Partial folder to the file, excluding the file extension.

It's also possible to create further folders, e.g.: Resources/Private/Partials/Blogpost/Tags.html and to call the Partial:

{f:render(partial: 'Blogpost/Tags', arguments: {
    tags: post.tags

ViewHelper Namespace import

Like within Fluid Templates, custom ViewHelpers can be used within Partials. Because these ViewHelpers are not in the default namespace, their namespace needs to be imported. For information about how to import a namespace, see Importing namespaces.

It's possible to use a Global namespace import, or imports the namespace within the Partial, or within the Template.


Up to CMS v8 this namespace import has to be within each Partial where such a ViewHelper was used. Since CMS v8 there is no need anymore. The namespace has to be imported within the Partial or the Templates. It still can be imported in both, but the template is enough.

How to treat Partials

Partials should best be treated as reusable block of Fluid, with no dependencies. Therefore the namespace imports should happen within the Partial. Also the Partial should be self contained.

This way the Partial can be reused within different Templates. As each Template has do call the Partial, each Template can map existing variables to match the used variables within the Partial.

Let's assume the following Partial: Resources/Private/Partials/Tags.html again:

<b>Tags</b>: <f:for each="{tags}" as="tag">{tag}</f:for>

This Partial only requires the variable {tags}.

Let's assume the following Template: Resources/Private/Templates/BlogPosts/Index.html:

<f:for each="{blogPosts}" as="blogPost">
    {blogPost.content -> f:format.html()}

    {f:render(partial: 'Tags', arguments: {
       tags: blogPost.tags

Within the Template, no variable {tags} exists. Instead, the variable {blogPost.tags} is mapped to {tags} for the Partial.

This way, it can also be reused for the following Template:


<f:for each="{blogs}" as="blog">
    {blog.description -> f:format.html()}

    {f:render(partial: 'Tags', arguments: {
       tags: blog.tags

Again, there is no variable {tags}. This time, an index of Blogs is displayed instead of blog posts of a single Blog. Both have relations to tags which should be displayed the same way. With a single Partial and the arguments-Argument this is possible.