> 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/tools/remote-tools-overview/software-application-logs.md).
# Get Device Files (Fetch Files)
In JFrog Connect you can easily retrieve logs or other files and folders from your IoT device.
You can retrieve a file or folder from a device. This is useful if you want to get log files or any other kind of file from a device.
## Get File or Folder
To retrieve a file or folder from a device, do the following:
1. Go to **File Fetch** in the left navigation tree and choose the relevant Fleet in the dropdown list at the top of the page.
2. Choose the name of the device from the **Device** list.
3. For a single file, enter the path on the device including the file name. For an entire folder, enter the path including the folder name on the device.
4. Click **Fetch**. In the Fetched Files table, you will see the state of the file fetch action in the State Column.
5. When your file or folder has been fetched successfully, click the icon in the View column.
6. Click **Download** or **View** to see the contents of the file retrieved. If your file is above the viewable file size in Connect, you can download the file and view it in a separate viewing application.
## Content Availability
### In Connect Web UI
The content you retrieve from a device is available for three days from the Connect web UI.
### In Artifactory
When you use the Connect UI to retrieve the files, the content is also automatically saved in Artifactory and is available there whenever you want it.
To find the content in the Artifactory web UI, go to Artifacts and the following path:
`connect-default-general/upswift-general/devices/`
In addition, you can retrieve the content from Artifactory using the Artifactory CLI.
### Using the Connect API
The [Fetch Files request](https://docs.connect.jfrog.io/developers/api-reference/connect-api-reference/device-files#post-api-v2-project_key-devices-device_uuid-logs) in the Connect API returns a URL to a location in Artifactory. You can use the Artifactory UI, API, or CLI to download the files from this URL. The files may not be available immediately at the URL. They become available when the device completes a successful upload of the files.
## What’s Next?
Learn how to [remove a device](/features-new-ui/devices/view-device-details/remove-a-device.md) from your fleet.
---
# 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/tools/remote-tools-overview/software-application-logs.md?ask=&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.
