> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/edit-your-guideflow/html-editor.md).

# HTML Editor

The HTML Editor enables you to modify your [HTML capture](/help/capture-a-guideflow/how-to-capture-a-guideflow/html-capture.md) and customize how your product appears in your guideflows.

Here's a quick overview of what can be achieved with the HTML Editor:

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/zpelymwf3k>" %}

With the HTML Editor, you can:

* **Select and modify HTML elements** directly in your capture
* **Hide or blur sensitive information** such as customer names, emails, revenue numbers, or internal data
* **Change text, numbers, graphs, buttons, or images** to create polished demo environments
* **Use variables** to dynamically personalize values across your showcase. Learn how to create and use variables [here](/help/variables/create-and-edit-variables.md).
* **Apply changes to all steps** to duplicate your HTML modifications across multiple steps automatically
* **Use AI to randomize values** and quickly generate realistic-looking demo data

Whether you're preparing a sales demo, onboarding flow, or product walkthrough, the HTML Editor helps you keep your content clean, consistent, and presentation-ready.

### Example use cases

* Blur customer or employee data before sharing demos externally
* Replace real company names with placeholder brands
* Update pricing, analytics, or dashboard metrics
* Personalize demos with dynamic variables
* Keep styling and modifications consistent across an entire flow

The HTML Editor gives you full control over your captured experience without needing engineering support.


---

# 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.guideflow.com/help/edit-your-guideflow/html-editor.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.