---
title: "Installation"
manual: "Look - real frontend previews in the TYPO3 page module"
version: "main"
permalink: "https://docs.typo3.org/permalink/flowd/typo3-look:installation@main"
source: "Installation/Index.rst"
rendered: "2026-09-17T14:56:56+00:00"
---

# Installation {#installation-1}

## Install with Composer {#install-with-composer}

Look is installed like any other TYPO3 extension in a Composer based project:

```bash
composer require flowd/typo3-look
```

Afterwards set up the extension so that TYPO3 picks up its configuration:

```bash
vendor/bin/typo3 extension:setup
```

That is all for the extension itself. The previews appear as soon as a
content element uses the view helper, see [Usage](https://docs.typo3.org/permalink/flowd/typo3-look:usage@main).

## If your frontend uses web fonts {#if-your-frontend-uses-web-fonts}

Look needs no web server configuration. One case is the exception: the preview
frame runs with an *opaque origin*, and browsers fetch web fonts and JavaScript
modules from such a frame as cross-origin requests. They only load if the
server answers with `Access-Control-Allow-Origin: *` for the path they
come from.

This affects web fonts of your frontend build, and the scripts of your build
when you enable [allowSiteScripts](https://docs.typo3.org/permalink/flowd/typo3-look:confval-flag-allow-site-scripts@main). Without
the header the previews still work, they just use fallback fonts. Images,
stylesheets and videos are not affected.

**nginx, for the path your frontend build lives in**

```nginx
location ~* \.(woff2?|ttf|otf|mjs|js)$ {
    add_header Access-Control-Allow-Origin "*";
}
```

The header is safe for public static files, it grants read access to bytes
that are served publicly anyway and browsers never combine `*` with
credentials. Do not add it to dynamic or authenticated paths.

## Check the installation {#check-the-installation}

Open a page in the page module that contains a content element with a Look
preview. You should see the element in the frontend design, scaled down. If
you see the plain TYPO3 preview instead, the content element type does not use
the view helper yet. If the frame stays empty or shows a red callout, see
[Known problems and how to solve](https://docs.typo3.org/permalink/flowd/typo3-look:known-problems@main).