> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/photo-studio.md).

# Photo Studio

Photo Studio is the first feature in AI Studio that helps teams create product-related imagery using reusable scene presets and a model library. The feature is configured around product data mapping, where a source product image, product naming field, additional descriptive attributes, and an output image attribute are connected to a reusable scene definition.

**Photo Studio** enables product teams to generate realistic, AI-powered images directly from product catalog data, without requiring external photo production tools. Photo Studio is built around two reusable libraries: **Scene presets** and **Model library**.

{% hint style="info" %}
Pricing and cost are available at [THIS](https://www.ergonode.com/product-information-management/pricing#features) link.
{% endhint %}

### What it does <a href="#what-it-does" id="what-it-does"></a>

Photo Studio takes a product's existing packshot image and enriches it with a fully configured visual scene, placing the product in a lifestyle environment, overlaying dimension lines, highlighting product features, or rendering it on a human or animal model. Generated images are written back directly into product attributes inside Ergonode, keeping the entire workflow within the PIM.

### Key concepts <a href="#key-concepts" id="key-concepts"></a>

| Concept                  | What it means                                                                                                                          |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Scene preset**         | A reusable generation configuration that maps product data attributes to an AI generation prompt and defines where the output is saved |
| **Scene template**       | The category type of a scene that determines which configuration sections are available (Interior, Fashion, Dimensions, etc.)          |
| **Model**                | A reusable AI figure definition (human, animal, or custom) that can be referenced by scene presets                                     |
| **Visual builder**       | A structured UI available in most sections for picking predefined options instead of writing free-text descriptions manually           |
| **Try out scene preset** | A live preview panel on the scene edit page where you can test a scene against a real product before saving                            |
| **Generate photos**      | The product-level trigger, accessible from the AI Actions panel, that runs a scene preset against a specific product                   |


---

# 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://usermanual.ergonode.com/photo-studio.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.
