> For the complete documentation index, see [llms.txt](https://docs.trendswap.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trendswap.app/getting-started/portrait-guidelines.md).

# portrait guidelines

The quality of your output video directly reflects the quality of your input portrait. Because TrendSwap enforces a strict **100% Identity Preservation Protocol**, the neural engine faithfully transfers every facial contour, skin texture, and eye detail from your photo.

***

## Optimal Photo Specifications

| Parameter            | Recommended Specification                            | Acceptable Range         |
| -------------------- | ---------------------------------------------------- | ------------------------ |
| **Framing**          | Chest-up portrait                                    | Waist-up to headshot     |
| **Gaze**             | Looking directly into camera lens                    | Slight angle (under 15°) |
| **Lighting**         | Soft, front-facing natural or studio light           | Even ambient light       |
| **Expression**       | Neutral, subtle smile, or slight grin                | Any natural facial pose  |
| **Image Resolution** | 1024×1024 pixels or higher                           | Minimum 512×512 pixels   |
| **File Formats**     | JPEG (`.jpg`, `.jpeg`), PNG (`.png`), WebP (`.webp`) | Up to 25 MB              |

***

## What to Do (Best Practices)

* **Clear, unobstructed face**: Keep hair, hats, and bangs away from the forehead, eyes, and cheekbones.
* **Good contrast**: Ensure separation between your hair and the background.
* **Sharp focus**: Use photos where the pupil reflections and facial bone structure are crisp.
* **Pets & Animals**: Front-facing cat and dog portraits with clearly visible snouts and eyes work exceptionally well in templates like *Smalltown Boy*, *Hit the Road Dude*, and *Baby Knight*.

## What to Avoid (Red Flags)

| Issue                           | Why It Harms Output                                      | How to Fix                                         |
| ------------------------------- | -------------------------------------------------------- | -------------------------------------------------- |
| **Sunglasses / Visors**         | Obscures eye geometry and pupil tracking                 | Remove eyewear or wear clear prescription glasses. |
| **Extreme Side Angles**         | Deprives the neural net of 3D facial symmetry            | Use a direct front-facing photo.                   |
| **Heavy Beauty Filters**        | Blurs skin texture and eliminates natural bone landmarks | Use unedited raw camera photos.                    |
| **Extreme Shadows / Backlight** | Creates harsh contrast artifacts in motion frames        | Face the window or light source directly.          |
| **Multiple People in 1 Photo**  | Ambiguity regarding which person to recast               | Crop the image to show only the intended subject.  |


---

# 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://docs.trendswap.app/getting-started/portrait-guidelines.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.