> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/deploy-files.md).

# Deploy File

A simple way to get one or more files quickly onto your device is to use the Deploy Files step type in a JFrog Connect update flow.

The Deploy Files step type enables the quick distribution of one or more files to your devices. To deliver a file, the step type facilitates a two-step process:

1. You upload of the requested file to Artifactory.
2. Devices pull the file from Artifactory.

This functionality is primarily utilized for quick deployment of specific files or binaries to your devices, eliminating the necessity to upload them beforehand.

## Prerequisites

* JFrog Connect and JFrog Platform accounts. 
* Connect Agent 6.0 or later and at least one device registered.
* One or more files ready for deployment.
* In the [Create Update Flow](/features-new-ui/deployments/update-flow.md) procedure, completed through Step 3.

## Add a Step and Configure the Step Type

To add a step and configure the step type you have chosen, do the following:

1. In the Create New Flow page, click **Add Step**.
2. In the **Step Type** dropdown list, choose **Deploy File**, give the step a **Step** **Name**, and create the step. You can change the step name afterwards if you need to.
3. Enter (drag and drop, or browse) the file in the file box.
4. Enter **Device Destination Path**. You can also make this a variable, for example {{device-destination-path}}. You will then enter the value for the variable upon deployment.

<div align="left"><figure><img src="https://1679291640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOX8HIrQ8f257lv49Od1Z%2Fuploads%2FGspDlzhvFhU0po1M7ylU%2Fdeploy-file-nui-01.png?alt=media&amp;token=ea3c429c-b78a-4a6e-b3f1-8ee4c45510bd" alt="" width="563"><figcaption></figcaption></figure></div>

5. (Optional) Configure your [On Failure](/features-new-ui/deployments/update-flow/on-failure-and-rollback.md) policy and instructions for rolling back.
6. Save your step configuration.
7. (Optional) If you want to deliver more than one file, create a **Deploy File** step for each file.

## What’s Next?

Learn how to deliver containers to your edge devices using the [Deploy Docker Image](/features-new-ui/deployments/update-flow/step-types/use-single-container.md) step type.


---

# 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.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/deploy-files.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.