> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/reference/widgets/display/iframe.md).

# Iframe

Embeds an external web page by http(s) URL — presentational, without live value bindings

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-60953de23af03396d70b047516cd1b21620480bc%2Fwidget-iframe.png?alt=media" alt="Iframe showing a live wind and weather map around the Hamburg plant" width="808"><figcaption></figcaption></figure>

An iframe embeds another web page into your App page: a weather map, a camera stream, a machine's own web interface, a supplier portal or another App. You give it the address and decide whether it shows a border. The embedded page stays what it is; it exchanges no values with your logic. Many websites forbid being embedded; check that the page you want allows it.

**Good for:** machine web interfaces and camera streams, external dashboards, weather and traffic maps.

## Settings

Double-click the widget in the Page editor to open its settings, grouped in these tabs.

<details>

<summary>Look &#x26; feel</summary>

* **URL**: Address of the page shown inside the frame; must start with http\:// or https\://, otherwise a hint asks for one.
* **Show border**: Draws a thin grey line around the frame.

</details>


---

# 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.heisenware.com/reference/widgets/display/iframe.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.
