> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/data/collections/field-types/file-upload.md).

# File/Upload Fields

Learn about File/Upload fields in Noloco tables

File/Upload fields serve as a storage point for various file types, allowing you to attach documents, images, or other files to a record. They offer easy uploading and secure storage options, accommodating diverse file formats.

## Supported File Types

Below is a table of the supported file types you can upload to Noloco:

| File Type            | Extension(s)                                            |
| -------------------- | ------------------------------------------------------- |
| JSON                 | .json                                                   |
| PDF                  | .pdf                                                    |
| XML                  | .xml                                                    |
| Audio                | .3gpp, .3gpp2, .aac, .mp3, .wav, .webm                  |
| Image                | .bmp, .gif, .heic, .jpeg, .jpg, .ico, .png, .svg, .webp |
| Email                | .eml                                                    |
| CSS                  | .css                                                    |
| CSV                  | .csv                                                    |
| HTML                 | .html                                                   |
| Markdown             | .md                                                     |
| JavaScript           | .js                                                     |
| Plain Text           | .txt                                                    |
| Video                | .3gpp, .3gpp2, .mpeg, .mp4, .mov, .webm                 |
| Compressed Files     | .zip, .7z                                               |
| Microsoft Word       | .doc, .docx, .dotx                                      |
| Microsoft Excel      | .xls, .xlsx, .xltx                                      |
| Microsoft PowerPoint | .ppt, .pptx, .potx, .ppsx                               |
| Microsoft Outlook    | .msg                                                    |

{% hint style="info" %}
If there's a file type you'd like us to support that isn't listed here, we'd love to hear from you! Please submit your request in our [community forum](https://community.noloco.io/c/feature-requests/7). Your suggestion helps us improve Noloco and better meet your needs.
{% endhint %}

## Configuration Options

* **Multiple Files** Allow users to upload multiple files to a single field
* **File Type Restrictions** Limit which file types can be uploaded (images only, documents only, etc.) These can be limited in the forms / action buttons the file field is used in

## Use Cases

File/Upload fields are essential for:

* Document management systems
* Image galleries and portfolios
* Resume and CV storage
* Contract and agreement storage
* Product images and specifications
* User profile pictures
* Report and invoice attachments

## Best Practices

* Set appropriate file type restrictions based on your use case
* Consider file size limits to manage storage costs
* Use descriptive field names that indicate what types of files should be uploaded
* File fields work well in forms for document collection
* Consider organizing files with clear naming conventions
* Use multiple file uploads when users need to submit several related documents


---

# 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://guides.noloco.io/data/collections/field-types/file-upload.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.