> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/data-types/file.md). # File ### Description The File datatype is used to store files. This can include a video, audio file, pictures, text documents and many more. When uploading files, there is a limit of 32MB per file. Check the specific [File Functions](/platform/wemreference/functions/files.md) for examples on how to work with files and their properties. Files have a validation property that can be used to restrict files to a certain file-type. This can change how the modeler handles this file. When an file has the image validation and this file field is added to a interaction canvas you will have the possibility to add it with the display option as image directly for example. ### Unknown An unknown value can be written as `UnknownFile`. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.wem.io/platform/wemreference/data-types/file.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.