> 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/media-view.md).

# Media View

Displays bound media — pdf, image or svg — from a file object, file-server path or URL

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-b94a14ccad03f856ce4749030383b61ffc143e3f%2Fwidget-media-view.png?alt=media" alt="Media view showing a PDF work instruction for the changeover to orange juice 0.5 l" width="608"><figcaption></figcaption></figure>

A media view shows a document or picture your logic hands it: a PDF, an image or an SVG graphic, from the file server, from an upload or from a web address. Unlike the image widget, it shows whatever arrives while the App runs, so the work instruction can follow the order, and the photo the selected machine. Handed a list of files, it shows the first one with the number of files on its corner.

**Good for:** work instructions and drawings for the current order, photos from uploads, certificates and reports.

## Properties

The widget's General tab lists these properties under Receives and Emits. Drop an executor's output, input or trigger onto a row to link it. An example also fills an unlinked widget as demo data in the App Builder.

{% tabs %}
{% tab title="Receives" %}
**`data`** (from an output, `string | object | Array<object>`): The medium to display (pdf, jpeg, png, gif or svg): a file object, a file-server path or a URL. A single-element array is unwrapped.

<details>

<summary>Example</summary>

```json
{
  "name": "report.pdf",
  "type": "application/pdf",
  "path": "/shared/uploads/report.pdf"
}
```

</details>

**`clear`** (from an output, `boolean`): Truthy values clear the displayed medium.

<details>

<summary>Example</summary>

```json
true
```

</details>
{% endtab %}
{% endtabs %}

## Settings

Double-click the widget in the Page editor to open its settings, grouped in these tabs. Settings marked *set per screen* are pinned by nature: every screen keeps its own value.

<details>

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

* **Image fitting**: How a picture meets its box when their shapes differ; PDFs ignore it. Choices: Contain (whole image, bars if needed), Cover (fill the box, crop the rest), Fill (stretch to the box), None (natural size, clipped), Scale down (never enlarge). *Set per screen.*
* **Focal point**: Which part of a picture stays visible when the fitting crops it or leaves room. Choices: Center, Top, Bottom, Left, Right, Top left, Top right, Bottom left, Bottom right. *Set per screen.*
* **Corner radius**: Rounding of the corners, from square to circle; theme keeps the theme's radius. Choices: Theme, Square, Low, Medium, High, Circle.

</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/media-view.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.
