> For the complete documentation index, see [llms.txt](https://docs.birdie.so/birdie-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.birdie.so/birdie-docs/request-screen-recordings/installation/customize-appearance.md).

# Customize Appearance

You can customize your customer-facing recorder [**in your settings**](https://app.birdie.so/settings$)**.**

{% stepper %}
{% step %}

### Select your name&#x20;

<figure><img src="/files/PLiMV9GaCD8JEn18zfg3" alt="" width="375"><figcaption><p>What name do you go by?</p></figcaption></figure>
{% endstep %}

{% step %}

### Add your company logo

* The file should be in JPG, SVG, PNG, or GIF format.
* The file size should not be larger than 4 MB.
* For best results, select a square image with a minimum dimension of 300 pixels or more (excluding SVG files).
  {% endstep %}

{% step %}

### Select your background color

Select the color to match your brand

<figure><img src="/files/5x5UKPeP3HdqrSwpZYTK" alt="" width="375"><figcaption><p>Change background color</p></figcaption></figure>
{% endstep %}

{% step %}

### White Label

Remove the entire Birdie branding

<figure><img src="/files/USPtanSldUpjB2Ndvruw" alt="" width="375"><figcaption><p>Remove Birdie branding</p></figcaption></figure>
{% endstep %}

{% step %}

### Footnote Text (Optional)

Add footnote text in case you want to display any relevant message on your recorder.&#x20;

* **Character Limit:** We recommend keeping messages concise, with a maximum of 105 characters.
* **Formatting:** Only basic HTML tags are supported: `<a>`, `<em>`, `<strong>`, and `<u>`. Other elements like anchors and complex HTML are not allowed.

No Footnote Needed? Simply leave the field empty.

<figure><img src="/files/p86gXVAtBRQXD8hI6YK1" alt="" width="375"><figcaption><p>Footnote Text</p></figcaption></figure>

**💡 Example: How to add a clickable link**

Let’s say you want the footnote to say:

> *“By recording your screen, you agree to our <mark style="color:blue;">Privacy Policy</mark>.”*

And your policy is at: `https://www.acme.com/privacy-policy`

You need to write the following HTML in the footnote field:

```html
By recording your screen, you agree to our <a href="https://www.acme.com/privacy-policy" target="_blank"><u>privacy policy</u></a>
```

{% hint style="info" %}
Note: when you're manually building your request recording links (for example in automations, email signatures, etc.), you can add up to 5 alternate footnote text. \
For each one an identifier will be given: add this identifier at the end of the url as an extra `dc` parameter, e.g. `?dc=<footnote_id>` or `&dc=<footnote_id>` to override the default footnote.
{% endhint %}
{% endstep %}

{% step %}

### Customers can enter text before sending a recording (optional)

By default, text input is disabled since text is typically entered through the helpdesk. If you want to allow your customers to add text alongside their screen recordings, you'll need to enable this feature.

<figure><img src="/files/S8POkWiZSqNltVK6vWwE" alt="" width="375"><figcaption><p>Should customers be able to add text to their screen recordings?</p></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.birdie.so/birdie-docs/request-screen-recordings/installation/customize-appearance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
