> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/image-jpg-png-gif-bmp-svg-ico-tiff.md).

# Image (.jpg, .png, .gif, .bmp, .svg, .ico, .tiff)

Configure image document entry settings in Remote Desktop Manager, including the display mode, storage mode, linked file, and URL.

This article details the many settings and options available for ***Image (.jpg, .png, .gif, .bmp, .svg, .ico, .tiff)*** document entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td><p>Select how the document opens:</p><ul><li><strong>External</strong> — Open the document outside Remote Desktop Manager.</li><li><strong>Embedded (tabbed)</strong> — Open the document in a tab of the Remote Desktop Manager main window.</li><li><strong>Undocked</strong> — Open the document in a separate window.</li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr><tr><td><strong>Mode</strong></td><td><p>Select where the document is kept:</p><ul><li><strong>Stored in database</strong> — The file is uploaded to the data source and stored with the entry. New entries use this mode by default.</li><li><strong>Link to file</strong> — The entry points to a file on disk.</li><li><strong>URL</strong> — The entry points to a web address.</li></ul><p><em><strong>Stored in database</strong></em> is not offered when the data source does not support attachments, or for an existing entry that uses another mode.</p></td></tr><tr><td><strong>Filename</strong></td><td>With <em><strong>Stored in database</strong></em>, the file to upload. The browse button is available only while the entry is being created. When a new entry already holds a stored file, click <em><strong>Clear</strong></em> to delete it. Once the entry is saved, use <em><strong>Update document</strong></em> to replace the stored file with another one, <em><strong>Save as</strong></em> to export the stored file, and <em><strong>Save and edit content</strong></em> to save the entry and open the document.<br><br>With <em><strong>Link to file</strong></em>, the path of the file the entry opens.</td></tr><tr><td><strong>URL</strong></td><td>Available when <em><strong>Mode</strong></em> is <em><strong>URL</strong></em>. The web address of the document. Click <em><strong>Navigate URL</strong></em> to open the address in the web browser.</td></tr><tr><td><strong>Use default credentials</strong></td><td>Available when <em><strong>Mode</strong></em> is <em><strong>URL</strong></em>. Use the default credentials to access the document at the URL.</td></tr><tr><td><strong>File size</strong></td><td>The size of the document. This value is read-only.</td></tr><tr><td><strong>Created by</strong></td><td>The user who created the entry. This value is read-only.</td></tr><tr><td><strong>Creation date</strong></td><td>The date the entry was created. This value is read-only.</td></tr></tbody></table>


---

# 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.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/image-jpg-png-gif-bmp-svg-ico-tiff.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.
