> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/use-cases/uploading-downloading.md).

# Uploading or Downloading Files in a Script

You can test a web application’s ability to upload or download a file as part of a transaction test, by adding it into your script. Although you can test file uploads and downloads using the FTP server test, you can also use a transaction test to assess a website’s support for file uploads or downloads through a browser interface.

Note the following:

* ThousandEyes does not allow you to upload ordinary files as part of a transaction test. You must generate a file with custom content as part of the script, or generate a file with random content.
* For file downloads, you can write a script to wait for the download to finish, examine the contents of that file, and use those contents elsewhere in the script. One common use case involves timing the performance of uploading or downloading a file.


---

# 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.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/use-cases/uploading-downloading.md?ask=<question>&goal=<endgoal>
```

`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.