> ## Documentation Index
> Fetch the complete documentation index at: https://docs.melius.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Assets and references

> Logos, fonts, pack shots, mood boards — how to get them into Melius and reference them in generations.

The agent can produce on-brand work with just a written anchor, but generations get sharper the moment you give it actual brand assets to reference. This page covers what's worth bringing in and how to wire each one up.

## Logos

The single most common cause of off-brand outputs is the model trying to recreate a logo from scratch. Don't make it guess.

<Steps>
  <Step title="Drag your logo file onto the canvas">
    PNG or SVG both work. Transparent backgrounds preferred. The file appears as an image node on the canvas.
  </Step>

  <Step title="Connect it to the image generations that need it">
    Drag an edge from the logo node into your output image node, or use `@logo` (or whatever you've named it) inside a prompt.
  </Step>

  <Step title="Tell the agent to use it">
    In the prompt: *"Place the @logo in the bottom-right corner. Do not redraw it — use the reference exactly."*
  </Step>
</Steps>

<Warning>
  Native AI/EPS file support isn't there yet — only SVG and PNG for vectors. If you need an editable working file, export to SVG from your vector tool first. We're tracking the request and may add AI/EPS support in a future release.
</Warning>

## Fonts

Two paths depending on how strict you need to be:

**Path A: Brand guidelines paste-in.** If you have a one-pager showing your fonts in use (H1 / H2 / body / display, all visible), paste an image of it onto the canvas and connect it to your image nodes. GPT Image 2 is good at recognizing fonts in a reference image and replicating them in output. Not pixel-perfect, but usually close enough to read as on-brand.

**Path B: Studio node for exact typography.** When the type has to be exact (legal copy, headline that uses your custom font), generate the background without text, then use a Studio node to overlay the text layer. The Studio node is a layered editing surface where you can add layers, drop in text, and position elements precisely. You can upload a custom font file (.otf or .ttf) and use it directly in the layer panel.

The Studio node also handles other "last mile" edits: positioning a logo precisely, adding a CTA button, dropping in a price tag. Most marketers end up using it for the final polish step without leaving the canvas.

## Pack shots and product photos

If your product has a specific shape, color, or detail that the model keeps getting wrong, a pack shot is the fastest fix.

* Drop one or more clean product photos onto the canvas.
* Connect them to your image nodes as image-to-image references.
* In the prompt: *"Use this exact product. Don't restyle, recolor, or modify it — only change the surrounding scene."*

If you have multiple angles, **unified groups** save you a step:

<Steps>
  <Step title="Select all the product photos">
    Click and drag a selection box, or shift-click each one.
  </Step>

  <Step title="Group them as a unified group">
    `Cmd+G` for a normal group, or right-click → "Unified group". A unified group exposes a single output port — so you drag one edge instead of one per image.
  </Step>

  <Step title="Connect the group to your image node">
    The agent now sees all the angles as a single reference, which is closer to how a human designer would use a product reference sheet.
  </Step>
</Steps>

<Tip>
  Up to 10 reference images per image-to-image generation. Beyond that, drop the weaker references — more isn't always better, and noisy references can pull the output off course.
</Tip>

## Mood boards and style references

Got a Pinterest board, a competitor ad, or an existing campaign whose look you want to mirror? Use the **Image Style Analysis** template.

<Steps>
  <Step title="Drag your mood images onto the canvas">
    Two to ten images that share the look you want.
  </Step>

  <Step title="Group them as a unified group">
    Same as above — one output port for the whole set.
  </Step>

  <Step title="Add the Image Style Analysis template">
    From the templates menu, pick "Image style analysis". It drops onto the canvas as a pre-configured text node. Connect the unified group to it.
  </Step>

  <Step title="Run the text node">
    The template analyzes the images and outputs a detailed style description — palette, lighting, composition, mood, shot type.
  </Step>

  <Step title="Use that output as context">
    Connect the style analysis node to your image generation nodes via an edge. The detailed style description gets appended to every prompt automatically.
  </Step>
</Steps>

<Warning>
  Easy to miss: after you connect images into the Image Style Analysis template, you have to **run the text node** before its output is usable. If you connect a downstream image node before running the analysis, the analysis text will be empty and the image node won't have any style guidance. Click into the text node and hit run.
</Warning>

## Product detail pages (PDPs)

You don't have to download every product photo manually. Paste a PDP URL into the agent chat and the agent will scrape the page — pulling product dimensions, materials, colors, copy, and reference imagery — into a text node you can reuse.

Example brief:

```
Pull the PDP details from [URL] and focus on the materials, dimensions,
and color options. Save the result as a text node I can reference
in image generations.
```

This is especially useful for product fidelity — if the model keeps getting your product's size or shape wrong, feeding it the PDP-scraped dimensions usually fixes it. See [Product photography & swaps](/help-center/marketers/recipes/product-swap).

## What to leave off the canvas

Not everything needs to be a reference. Some asset types are noise more than signal:

* **Past ads that don't represent the new direction.** If you're refreshing the look, old assets will pull the agent back toward the look you're trying to leave.
* **Generic stock imagery.** Unless it specifically matches your brand, it dilutes the reference.
* **Low-resolution or compressed JPGs.** The model struggles to extract style from heavily compressed images. Use the highest-quality source you have.

If in doubt, generate with fewer references first. You can always add more later.

## Image editing tools on the canvas

Once you have a generated image, you don't always need to start over to make a change. A few tools live directly on each image node:

* **Edit Image** — open the image in a quick editing surface for small tweaks.
* **Inpaint** — draw a mask over an area, then describe what should fill it. Useful for removing or replacing a specific element without re-running the whole generation.
* **Remove Background** — exactly what it sounds like. Outputs a transparent PNG.
* **Upscale** — increase resolution after generation if you started at 1K and want to ship at 2K or 4K.
* **Studio node** — for layered editing with text overlays, see the Fonts section above.

<Note>
  Inpaint is improving but isn't always the right tool. For things like "remove the text from this image," an image-to-image regeneration with a prompt like *"recreate this exactly, but remove all text apart from the @logo"* often produces cleaner results than masking. Try the image-to-image route first; reach for Inpaint when you need to keep most of the image untouched but change one specific region.
</Note>