include

You are reading the documentation for Twig 1.x. Switch to the documentation for Twig 2.x, 3.x.

Warning Twig version 1.x is no longer maintained.

Questions & Feedback

Found a typo or an error?
Want to improve this document? Edit it.

Need support or have a technical question?
Ask support on Stack Overflow.

License

Twig documentation is licensed under the new BSD license.

`include`

The include statement includes a template and outputs the rendered content of that file:

        1
2
3
        {% include 'header.html' %}
    Body
{% include 'footer.html' %}
    

Note

As of Twig 1.12, it is recommended to use the include function instead as it provides the same features with a bit more flexibility:

The include function is semantically more "correct" (including a template outputs its rendered contents in the current scope; a tag should not display anything);

It's easier to store the rendered template in a variable when using the include function:

        1
2
3
4
5
        {% set content %}{% include 'template.html' %}{% endset %}

{# vs #}

{% set content = include('template.html') %}
    

The include function does not impose any specific order for arguments thanks to named arguments.

Included templates have access to the variables of the active context.

If you are using the filesystem loader, the templates are looked for in the paths defined by it.

You can add additional variables by passing them after the with keyword:

        1
2
3
4
5
        {# template.html will have access to the variables from the current context and the additional ones provided #}
{% include 'template.html' with {'foo': 'bar'} %}

{% set vars = {'foo': 'bar'} %}
{% include 'template.html' with vars %}
    

You can disable access to the context by appending the only keyword:

        1
2
        {# only the foo variable will be accessible #}
{% include 'template.html' with {'foo': 'bar'} only %}
    

        1
2
        {# no variables will be accessible #}
{% include 'template.html' only %}
    

Tip

When including a template created by an end user, you should consider sandboxing it. More information in the Twig for Developers chapter and in the sandbox tag documentation.

The template name can be any valid Twig expression:

        1
2
        {% include some_var %}
{% include ajax ? 'ajax.html' : 'not_ajax.html' %}
    

And if the expression evaluates to a \Twig\Template or a \Twig\TemplateWrapper instance, Twig will use it directly:

        1
2
3
4
5
6
7
8
9
        // {% include template %}

// deprecated as of Twig 1.28
$template = $twig->loadTemplate('some_template.twig');

// as of Twig 1.28
$template = $twig->load('some_template.twig');

$twig->display('template.twig', ['template' => $template]);
    

1.2

The ignore missing feature has been added in Twig 1.2.

You can mark an include with ignore missing in which case Twig will ignore the statement if the template to be included does not exist. It has to be placed just after the template name. Here some valid examples:

        1
2
3
        {% include 'sidebar.html' ignore missing %}
{% include 'sidebar.html' ignore missing with {'foo': 'bar'} %}
{% include 'sidebar.html' ignore missing only %}
    

1.2

The possibility to pass an array of templates has been added in Twig 1.2.

You can also provide a list of templates that are checked for existence before inclusion. The first template that exists will be included:

        1
        {% include ['page_detailed.html', 'page.html'] %}
    

If ignore missing is given, it will fall back to rendering nothing if none of the templates exist, otherwise it will throw an exception.