> 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/input/signature.md).

# Signature

Captures a hand-drawn signature on a pad, inline or in a popup, and delivers it as a PNG file's entry with its content inline

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-fc0e26e68b5b6e5608dff00eff32600ce85e0693%2Fwidget-signature.png?alt=media" alt="Shift handover panel with a signed signature pad and Accept and Clear buttons" width="568"><figcaption></figcaption></figure>

The signature widget lets users sign with a finger, a pen or the mouse, right on the page or in a popup. When they accept, the signature goes to your logic as a file with its PNG inside, ready to be stored in a [`file` field](https://docs.heisenware.com/reference/functions/storage/relational-database.md#files-in-a-table) of the record or printed into a report (its `base64` is the picture). You choose the pen and pad colors and the button texts.

**Good for:** shift handovers, delivery and acceptance notes, approvals and sign-offs.

## 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="Emits" %}
**`signature`** (into an input, `object`): Writes the captured signature when the user accepts it: a file's entry with the PNG inline, `{ name: 'signature.png', type: 'image/png', size, base64 }` (base64 without a data-URL prefix) - what a `file` field takes and a media view shows.

**`onClick`** (fires a trigger): Triggers the linked executor when a signature is accepted.
{% endtab %}
{% endtabs %}

## Settings

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

<details>

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

* **Pen color**: Color of the drawn stroke; auto keeps the theme's text color.
* **Pad color**: Background color of the signing pad; auto keeps the theme's tile color.
* **Display mode**: Popup shows a button that opens the signing pad in a dialog; inline draws the pad in the widget itself with its buttons below. Choices: Inline, Popup.
* **Accept text**: Label of the pad button that delivers the signature and closes the dialog; ignored while the pad is empty.
* **Clear text**: Label of the pad button that wipes the drawing.
* **Button text**: Label of the button on the page, also the title of the dialog. Only when Display mode is Popup.

</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/input/signature.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.
