Twig Configuration Reference (TwigBundle)

auto_reload

type: boolean default: %kernel.debug%

If true, whenever a template is rendered, Symfony checks first if its source code has changed since it was compiled. If it has changed, the template is compiled again automatically.

autoescape

type: boolean or string default: 'name'

If set to false, automatic escaping is disabled (you can still escape each content individually in the templates).

If set to a string, the template contents are escaped using the strategy with that name. Allowed values are html, js, css, url, html_attr and name. The default value is name. This strategy escapes contents according to the template name extension (e.g. it uses html for *.html.twig templates and js for *.js.twig templates).

autoescape_service

type: string default: null

As of Twig 1.17, the escaping strategy applied by default to the template is determined during compilation time based on the filename of the template. This means for example that the contents of a *.html.twig template are escaped for HTML and the contents of *.js.twig are escaped for JavaScript.

This option allows to define the Symfony service which will be used to determine the default escaping applied to the template.

autoescape_service_method

type: string default: null

If autoescape_service option is defined, then this option defines the method called to determine the default escaping applied to the template.

base_template_class

type: string default: 'Twig\Template'

Twig templates are compiled into PHP classes before using them to render contents. This option defines the base class from which all the template classes extend. Using a custom base template is discouraged because it will make your application harder to maintain.

cache

type: string | false default: '%kernel.cache_dir%/twig'

Before using the Twig templates to render some contents, they are compiled into regular PHP code. Compilation is a costly process, so the result is cached in the directory defined by this configuration option.

Set this option to false to disable Twig template compilation. However, this is not recommended; not even in the dev environment, because the auto_reload option ensures that cached templates which have changed get compiled again.

charset

type: string default: '%kernel.charset%'

The charset used by the template files. In the Symfony Standard edition this defaults to the UTF-8 charset.

date

These options define the default values used by the date filter to format date and time values. They are useful to avoid passing the same arguments on every date filter call.

debug

type: boolean default: %kernel.debug%

If true, the compiled templates include a __toString() method that can be used to display their nodes.

exception_controller

type: string default: twig.controller.exception:showAction

This is the controller that is activated after an exception is thrown anywhere in your application. The default controller (ExceptionController) is what's responsible for rendering specific templates under different error conditions (see How to Customize Error Pages). Modifying this option is advanced. If you need to customize an error page you should use the previous link. If you need to perform some behavior on an exception, you should add a listener to the kernel.exception event (see Built-in Symfony Service Tags).

number_format

These options define the default values used by the number_format filter to format numeric values. They are useful to avoid passing the same arguments on every number_format filter call.

optimizations

type: int default: -1

Twig includes an extension called optimizer which is enabled by default in Symfony applications. This extension analyzes the templates to optimize them when being compiled. For example, if your template doesn't use the special loop variable inside a for tag, this extension removes the initialization of that unused variable.

By default, this option is -1, which means that all optimizations are turned on. Set it to 0 to disable all the optimizations. You can even enable or disable these optimizations selectively, as explained in the Twig documentation about the optimizer extension.

default_path

type: string default: '%kernel.project_dir%/templates'

The default directory where Symfony will look for Twig templates.

paths

type: array default: null

This option defines the directories where Symfony will look for Twig templates in addition to the default locations. Symfony looks for the templates in the following order:

1. The directories defined in this option;
2. The Resources/views/ directories of the bundles used in the application;
3. The src/Resources/views/ directory of the application;
4. The directory defined in the default_path option.

The values of the paths option are defined as key: value pairs where the value part can be null. For example:

1
2
3
4
5

# app/config/config.yml
twig:
    # ...
    paths:
        '%kernel.project_dir%/vendor/acme/foo-bar/templates': ~

1
2
3
4
5
6
7
8
9
10
11
12
13

<!-- app/config/config.xml -->
<container xmlns="http://symfony.com/schema/dic/services"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:twig="http://symfony.com/schema/dic/twig"
    xsi:schemaLocation="http://symfony.com/schema/dic/services
        https://symfony.com/schema/dic/services/services-1.0.xsd
        http://symfony.com/schema/dic/twig https://symfony.com/schema/dic/twig/twig-1.0.xsd">

    <twig:config>
        <!-- ... -->
        <twig:path>%kernel.project_dir%/vendor/acme/foo-bar/templates</twig:path>
    </twig:config>
</container>

1
2
3
4
5
6
7

// app/config/config.php
$container->loadFromExtension('twig', [
    // ...
    'paths' => [
        '%kernel.project_dir%/vendor/acme/foo-bar/templates' => null,
    ],
]);

The directories defined in the paths option have more priority than the default directories defined by Symfony. In the above example, if the template exists in the acme/foo-bar/templates/ directory inside your application's vendor/, it will be used by Symfony.

If you provide a value for any path, Symfony will consider it the Twig namespace for that directory:

1
2
3
4
5

# app/config/config.yml
twig:
    # ...
    paths:
        '%kernel.project_dir%/vendor/acme/foo-bar/templates': 'foo_bar'

1
2
3
4
5
6
7
8
9
10
11
12
13

<!-- app/config/config.xml -->
<container xmlns="http://symfony.com/schema/dic/services"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:twig="http://symfony.com/schema/dic/twig"
    xsi:schemaLocation="http://symfony.com/schema/dic/services
        https://symfony.com/schema/dic/services/services-1.0.xsd
        http://symfony.com/schema/dic/twig https://symfony.com/schema/dic/twig/twig-1.0.xsd">

    <twig:config>
        <!-- ... -->
        <twig:path namespace="foo_bar">%kernel.project_dir%/vendor/acme/foo-bar/templates</twig:path>
    </twig:config>
</container>

1
2
3
4
5
6
7

# app/config/config.php
$container->loadFromExtension('twig', [
    // ...
    'paths' => [
        '%kernel.project_dir%/vendor/acme/foo-bar/templates' => 'foo_bar',
    ],
]);

This option is useful to not mess with the default template directories defined by Symfony. Besides, it simplifies how you refer to those templates:

1

@foo_bar/template_name.html.twig

strict_variables

type: boolean default: false

If set to true, Symfony shows an exception whenever a Twig variable, attribute or method doesn't exist. If set to false these errors are ignored and the non-existing values are replaced by null.