> For the complete documentation index, see [llms.txt](https://docs.inverse.watch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inverse.watch/user-guide/visualizations/visualizations-how-to.md).

# Visualizations How-To

### 1. Create a New Visualization <a href="#create-a-new-visualization" id="create-a-new-visualization"></a>

Once your query has finished running for the first time, you can add a visualization by clicking the “New Visualization” button above the results table.

<figure><img src="https://4269815422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGc9mnST31tkU3h2NNgSL%2Fuploads%2FoCGlVssVsXmhg15bghrx%2Fcreate_new_visualization.gif?alt=media&amp;token=36a2206c-2df5-4b40-9c1e-4fe36814619e" alt=""><figcaption><p>create a new visualization</p></figcaption></figure>

### 2. Edit A Visualization

You can modify the settings of an existing visualization from the query editor screen. Click the visualization on the tab bar and you’ll see an `Edit Visualization` option beneath each visualization. Clicking it will open the current settings for that visualization (type, X axis, Y axis, groupings etc.). Hit “Save” to apply your changes or “Cancel” to leave no trace.

<figure><img src="https://4269815422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGc9mnST31tkU3h2NNgSL%2Fuploads%2FyntGYMLTPri2xfoEyOgy%2FEdit_A_Visualization.gif?alt=media&amp;token=5cacd680-104e-41f8-a3ed-5b580bd03f5f" alt=""><figcaption><p>edit a visualization</p></figcaption></figure>

### 3. Embedding Visualizations

It’s easy to embed visualizations. Just click the ellipsis button beneath any visualization to show further options and select `Embed Elsewhere`.

This will pop up the `<iframe>` code you can drop into your HTML pages.

<figure><img src="https://4269815422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGc9mnST31tkU3h2NNgSL%2Fuploads%2FLvfqr6g032ToLF5mDyOi%2FEmbedding_Visualizations.gif?alt=media&amp;token=48937fbc-35b2-4733-b069-a79aeeb6b9da" alt=""><figcaption><p>embedding visualization</p></figcaption></figure>

{% hint style="warning" %}
Queries with text-type parameters do not support embeds
{% endhint %}

**PNG image Embeds**

For SaaS customers, there is also a hardlink to a PNG of your visualization hosted through `snap.redash.io`. The PNG embed is especially useful in contexts where iframes won’t work (like GitHub issues). If you need the visualization PNG to include a `Cache-Control: no-cache` header, just tack the Query String variable `?no-cache` to the end of your PNG embed link.

**Query String Variables for Embeds**

You can append query string variables to your embed URLs:

* `?hide_parameters` hides any parameter selection widgets
* `?hide_timestamp` hides the timestamp

**Downloading A Visualization as an Image File**

For chart visualizations, you can also download a local image file. Just hover your mouse near the top right area of the visualization and click the camera icon that appears. A PNG will be downloaded to your device.

<figure><img src="https://4269815422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGc9mnST31tkU3h2NNgSL%2Fuploads%2FWUn2y9QtKos4u2ecK9pN%2FDownloading%20A%20Visualization%20as%20an%20Image%20File.gif?alt=media&amp;token=ca53bc55-0637-4043-bf07-51a00ddd4260" alt=""><figcaption><p>visualization png file</p></figcaption></figure>

***


---

# 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.inverse.watch/user-guide/visualizations/visualizations-how-to.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.