> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/reporting/template-images.md).

# Template - Images

## Overview

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F2omSFmw3fWcpxxG22XHw%2Ftemplate-images-at-a-glance.svg?alt=media&amp;token=49cd5737-9c51-4441-984c-c3d1cbe72f6b" alt=""><figcaption></figcaption></figure>

Reports can include two kinds of images:

| Kind               | What it is                                                                                                                                    | Example                                           |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **Static images**  | Images you place in your Word template, such as a logo or cover graphic. They appear in every report as they are.                             | Your company logo on the cover page               |
| **Dynamic images** | Images uploaded to AttackForge, such as screenshots in a proof of concept. They come from the project data each time the report is generated. | Screenshots in a vulnerability's proof of concept |

This page explains how AttackForge downscales dynamic images, and how to size and style them in your reports.

Help, examples and tips are also on the [ReportGen GitHub support site](https://github.com/AttackForge/ReportGen).

## Why it matters

* **Faster reports.** Smaller images mean reports with many screenshots generate more quickly.
* **Readable evidence.** The right width keeps screenshots clear enough to read.
* **A consistent look.** Images are the same width and style throughout the report.

## Who uses it

| Who                         | To                                                   |
| --------------------------- | ---------------------------------------------------- |
| **Administrators**          | Set the maximum image width                          |
| **Report template authors** | Size, caption and style images in templates          |
| **Testers**                 | Know how their screenshots will appear in the report |

## Image downscaling

To speed up report generation, AttackForge downscales dynamic images, meaning images uploaded to AttackForge, not images placed statically in your template.

By default, dynamic images are downscaled to a maximum width of 975 pixels. You can change this with the **Max Image Width** setting.

| Setting             | Default    | Range              |
| ------------------- | ---------- | ------------------ |
| **Max Image Width** | 975 pixels | 100 to 2000 pixels |

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fb48wyrWF9WsPNGtYwYfb%2FScreenshot%202026-11-11%20at%207.35.04%E2%80%AFam.png?alt=media&amp;token=9b441fd0-9912-450e-8524-d55731d33a07" alt=""><figcaption></figcaption></figure>

### Choose the right width

| If you                         | Then                             | Trade-off                           |
| ------------------------------ | -------------------------------- | ----------------------------------- |
| **Increase** the maximum width | Images are sharper in the report | Reports may take longer to generate |
| **Decrease** the maximum width | Reports may generate faster      | Images are lower quality            |

Raise the width if testers' screenshots are hard to read in reports, such as screenshots with small text or wide screens. Lower it if reports with many screenshots are slow to generate.

### Change the maximum image width

1. Open the **Max Image Width** setting in **Administration > Projects > Reporting > Create Report**
2. Enter a width between 100 and 2000 pixels.
3. Save, then generate a report to check image quality and generation time.

**T**he setting applies to the whole tenant and only affects the copies used in reports.

### Add dynamic images to your report

Dynamic images are part of rich-text fields, such as a proof of concept. Print a rich-text field with its `{@..._styled}` tag, where `...` is the tag name, and its images are included:

```
{#vulnerabilities}
{#affected_assets}
{@proof_of_concept_styled}
{/}{/}
```

### Size images in the template

Use the [`resize` filter](https://support.attackforge.com/app/modules/reporting/template-filters) to set the width of images in the report. Images are scaled up or down, and the height changes to keep the same shape. Resize will stretch or shrink the already downscaled image - it does not change the amount of pixels.

```
{#vulnerabilities}
{#affected_assets}
{@proof_of_concept_styled | resize:[“300”]}
{/}{/}
```

### Caption and style images

Options on the `{@..._styled}` tag control image captions, figures and styles. See [Template Styles](https://support.attackforge.com/app/modules/reporting/template-styles) for the full list.

| To                                                           | Use                                                                      |
| ------------------------------------------------------------ | ------------------------------------------------------------------------ |
| Show the caption, filename, both or nothing under each image | `"image_description"`: `caption`, `prefer-caption`, `filename` or `none` |
| Hide the figure under each image                             | `"image_figure":"none"`                                                  |
| Style images and their captions                              | `"image_style"`                                                          |
| Style images only (Word character style)                     | `"image_display_style"`                                                  |
| Style image captions only (Word character style)             | `"image_description_style"`                                              |
| Set the default style for all images                         | The **AF Images** style in your template                                 |

**Example** — boxed images with captions, at 300 pixels wide (from Template Styles):

```
{#vulnerabilities}
{#affected_assets}
{@proof_of_concept_styled(“image_display_style”:”BoxedImage”,“image_description”:“caption”) | resize:[“300”]}
{/}{/}
```

### Add static images

To add an image that appears in every report, such as a logo, insert it in your Word template as you would in any Word document. Static images aren't downscaled.

## Tips

* **Start with the default.** 975 pixels suits most screenshots on an A4 or Letter page.
* **Change one thing at a time.** After changing the maximum width, generate the same report and compare quality and time.
* **Use `resize` for layout, and Max Image Width for performance.**
* **Ask testers to crop screenshots** to what matters. Smaller, focused images are clearer and faster.
* **Use `prefer-caption`** so every image has a description, even when the tester didn't add a caption.
* **Compress large static images,** such as cover graphics, before adding them to the template, to keep the template small.

## FAQ

**What's the default maximum image width?** 975 pixels.

**What's the allowed range?** 100 to 2000 pixels.

**Are images in my template downscaled?** No. Only dynamic images, meaning images uploaded to AttackForge, are downscaled.

**Why are screenshots blurry in my report?** They may be downscaled too far. Try a larger Max Image Width, or check the `resize` width in your template.

**Why is my report slow to generate?** Large images take longer. Try a smaller Max Image Width.

**How do I make every image the same width?** Use the `resize` filter, such as `| resize:["300"]`.

**How do I hide image filenames?** Use `"image_description":"caption"` or `"none"`. See [Template Styles](https://support.attackforge.com/app/modules/reporting/template-styles).

## Related pages

* [Reporting overview](https://support.attackforge.com/app/modules/reporting/overview)
* [Template styles](https://support.attackforge.com/app/modules/reporting/template-styles)
* [Template filters](https://support.attackforge.com/app/modules/reporting/template-filters)
* [Template options](https://support.attackforge.com/app/modules/reporting/template-options)
* [ReportGen on GitHub](https://github.com/AttackForge/ReportGen)


---

# 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://support.attackforge.com/app/modules/reporting/template-images.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.
