> For the complete documentation index, see [llms.txt](https://pwa.spomky-labs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pwa.spomky-labs.com/1.1.x/image-management/screenshots.md).

# Screenshots

Taking screenshots of your application has great benefits.It may become difficult to manage screenshot updates as the application evolves, in particular if multiple sizes are managed.

This command requires dependencies and **should be executed in `dev` environnement only**.

```sh
composer require --dev symfony/panther
composer require --dev dbrekelmans/bdi && vendor/bin/bdi detect drivers
```

### Image Processor

Please read the section on [the Icons page](#image-processor).

### Taking Screenshots

From your shell, you can use the following command line to take a screenshot of a given URL.

```sh
symfony console pwa:create:screenshot https://example.com
```

This will create a folder in `assets/screenshots` with screenshot. In addition, the console output will give you the best configuration to use these new image files by copy-pasting.

```yaml
pwa:
    manifest:
        screenshots:
            - src: screenshots/screenshot-1200x1100.png
              width: 1200
              height: 1100
              type: image/png
            - ...
```

### Formats And Sizes

You can change the format and sizes by setting the values you need as options. It is recommended to provide mobile and desktop views of your application.

```sh
symfony console pwa:create:screenshot https://example.com --format="webp" --width=750 --height=1334
```

### Output Folder

Similarily, if you want to change the output folder, you can set it as an option.

```sh
symfony console pwa:create:screenshot https://example.com --output="/foo/bar"
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://pwa.spomky-labs.com/1.1.x/image-management/screenshots.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.