> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/forms/fields-toolbox/basics/download.md).

# Download

**Category**: Field

**Version**: 1.0

**Last Updated**: May 28, 2026

**Author**: Any2Info

***

### Description

The Download field allows users to download set files, either a static fixed file or a file originating from a **Document Service**.

***

### General Properties

The **Download** field inherits general Field Properties such as ‘Font size’, ‘Font color’ and ‘Icon color’.

***

### Special Properties

The **Download** field has a few special properties unique to it. These include:

| Name                                                                           | Value                                                                      | Explanation                       |
| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------- | --------------------------------- |
| FIle source                                                                    | *Document service* or *Fixed file*                                         | Determines additional properties  |
| Document Service                                                               | A document service set in the *Tools* section of the *Platform*            | Determines the source of the file |
| File identifier                                                                | If *File source* is set to *Document service* this value is free text.     |                                   |
| If *File source* is set to *Fixed file* this value will be a picker for a file | Either something to identify the external file with, or a fixed file value |                                   |

***

### Tips & Best Practices

* When using an external file test if the File identifier works properly and doesn’t try to download a non-existing file

***

### Examples

The following example is the most basic form of a **Download** field. When tapped/clicked it will download the file that was set using the *File identifier* property.

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FayV59oJ5eTvjsvfaZXKx%2Fimage.png?alt=media&amp;token=393dc5f9-86ae-4f48-9595-05827cedd1a6" alt=""><figcaption></figcaption></figure>

***

### Changelog

| **Version** | **Date**     | **Change**                       |
| ----------- | ------------ | -------------------------------- |
| 1.0         | May 28, 2026 | Initial document & documentation |


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/forms/fields-toolbox/basics/download.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.
