> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/nola/canvas/editing-canvases.md).

# Editing a Canvas

Once a Canvas exists, you refine it by chatting with Nola. You can ask for broad changes ("add a section for open tickets") or pinpoint a single element and change just that. This targeted approach is called **hybrid editing**.

## Editing by chatting

The simplest way to change a Canvas is to describe the change in the Nola chat:

* "Make the header background darker."
* "Add a column to the table for the deal owner."
* "Move the chart above the stats."

Nola applies the change and updates the preview. Because she edits the Canvas in place, small tweaks stay fast — she doesn't rebuild the whole page for every request.

## Editing a specific element (hybrid editing)

When you want to change one particular thing on a Canvas, you can point Nola straight at it instead of describing where it is in words.

1. Hover over the page. Editable elements highlight as you move over them, so you can see what you're able to target.
2. **Click the element** you want to change — a card, a heading, a chart, an image, a section.
3. The selected element is added to the chat as context, and it's clearly marked so you know exactly what Nola will act on.
4. Type your change — for example, "make this bigger" or "change this to show last month instead."
5. Nola applies the change to just that element.

When you're done, **clear the selection** to go back to talking about the whole Canvas.

{% hint style="success" %}
Selecting an element removes all the guesswork. Instead of "change the second card on the right," you can just click the card and say "make this green" — Nola knows precisely what "this" is.
{% endhint %}

<figure><img src="/files/D2iAUhz3ex6IgEUJShC3" alt=""><figcaption></figcaption></figure>

### Why targeted edits matter

Hybrid editing keeps changes surgical:

* **Faster** — Nola changes only what you selected rather than regenerating the page.
* **Safer** — the rest of your Canvas stays exactly as it was.
* **Clearer** — you and Nola are always talking about the same element.

## Adding and replacing images

You can bring your own images into a Canvas — logos, banners, illustrations, product photos.

1. Upload the image in the Nola chat.
2. To control **where** it goes, [select the element](/nola/canvas/editing-canvases.md) or area where you want it first, then upload — or describe the placement, e.g. "put this logo in the header."
3. Nola places the image in the Canvas.

To swap an image out, select it and upload the replacement, or ask Nola to "replace this image."

{% hint style="info" %}
Combining selection with an upload is the most reliable way to place an image. Click where it should go, add the file, and Nola has everything she needs to put it in the right spot.
{% endhint %}

<figure><img src="/files/gURhLdPzJ3HI6cTfYwS9" alt=""><figcaption><p>Uploading an image to Nola</p></figcaption></figure>

<figure><img src="/files/LekB2CXSIZHcOqROlslh" alt=""><figcaption><p>The image placed on the Canvas</p></figcaption></figure>

## Iterating with confidence

Every edit is part of your normal build history, so you can experiment freely:

* Keep refining conversationally until the Canvas is right.
* If a change isn't what you wanted, tell Nola what to adjust — you don't have to start over.
* If something goes wrong, you can [restore an earlier version](/nola/canvas/troubleshooting-canvases.md#restoring-a-previous-version) of the Canvas.

## Next steps

{% content-ref url="/pages/tPyvzlaISWStg0LRdl0O" %}
[Configuring a Canvas](/nola/canvas/configuring-canvases.md)
{% endcontent-ref %}

{% content-ref url="/pages/XO0diqL1H6pd9QAcnv4n" %}
[Troubleshooting a Canvas](/nola/canvas/troubleshooting-canvases.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.noloco.io/nola/canvas/editing-canvases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.