> For the complete documentation index, see [llms.txt](https://creativemail.gitbook.io/knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://creativemail.gitbook.io/knowledge/help-articles/changes_to_html_do_not_reflect_in_the_editor.md).

# Why HTML Edits Don't Persist in the Email Template Editor

If you modify the HTML code directly within a Salesforce Email Template, please note that **those changes will not be reflected in the Creative Mail editor interface**.

To ensure your edits persist and display correctly within the Editor:

* **All changes must be made through the Creative Mail editor.**

While it is technically possible to alter the HTML manually, such changes:

* Will not be recognized by the editor
* Will **not display** during subsequent edits
* Will be **overwritten** the next time the template is saved via the editor.

This behavior occurs because Creative Mail stores the visual design data separately from the HTML template. That design data is only updated through the editor itself.


---

# 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://creativemail.gitbook.io/knowledge/help-articles/changes_to_html_do_not_reflect_in_the_editor.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.