---
id: "arquivos-importar-e-baixar"
titulo: "Importing and downloading files"
resumo: "Bring files in from outside the workspace, what happens on a name collision, and how to download a file from a remote worktree."
idioma: "en"
tipo: "guia"
categoria: "arquivos-git"
aplicavelDesde: "0.0.16"
capabilities: ["fileTree.import.upload", "fileTree.download"]
estadoEditorial: "aprovado"
nivelEvidencia: "artefato-distribuido"
refFonte: "27574c339b58316408f6be2d62169d59041d07bf"
revisaoFonte: "2026-09-24"
revisor: "mantenedor (v1, 2026-10-03)"
rota: "/docs/en/ferramentas/arquivos/importar-e-baixar/"
fonte: "pt-br/ferramentas/arquivos/importar-e-baixar.md"
caminhoPublico: "docs/publica/en/ferramentas/arquivos/importar-e-baixar.md"
hashFonte: "sha256:f6499de29d406c5834831939fbcecfaba553707dcacda921bd59c4aa4cc6949b"
hashDestaPagina: "sha256:6ab2ba4ac65f566397b4bc93c09c46e0930aab6b3c3a7f0659b8142aa2df8d23"
traducaoAssistidaPorIA: true
traducaoDesatualizada: false
corpoRetido: false
---
<!-- traducao-assistida-por-ia: idioma=EN fonte=pt-br/ferramentas/arquivos/importar-e-baixar.md fonteHash=sha256:f6499de29d406c5834831939fbcecfaba553707dcacda921bd59c4aa4cc6949b estado=atual -->

## Import files from the system

The path is to **drag files from outside the app and drop them onto the tree**.

- The destination is the folder under the cursor at the moment of the drop.
- The files enter the **workspace** folder.
- Files dropped by native drag and drop reach the app through the operating system's own channel, not through the tree's internal drag mechanism.

### What to expect from the copy

- Names are planned **before** the copy, and the copy is done item by item.
- There is **progress and cancellation** in the import flow.
- When it finishes, the result is summarized.

> **Known limitation:** the Files panel starts the import **without showing the conflict decision or the progress**. The dialogs that would ask for a decision on a name collision do not appear in that panel.
>
> **Practical consequence:** a name collision may arrive **with no decision screen** for you to choose between replacing, renaming or cancelling. Treat this as an open limitation — before importing something that might collide, prefer importing into an empty folder and moving afterwards.

## Download from a remote worktree

When the workspace is on a remote host, the file row offers **download**.

- The action only makes sense with a remote target: **with no remote target, there is nothing to download**.
- The file is brought from the remote host to the local system.
- The download does not change the file on the remote.

## Limits

- **Importing does not replace files atomically** on an environment runtime: replacing an existing file is not guaranteed as a single operation.
- **Cancelling midway** interrupts the sequence; whatever was already copied remains.
- The import **does not** go through git: what enters stays as a new or modified file, and shows up as a change in status.

## Related

- [The tree and git status](/docs/en/ferramentas/arquivos/arvore-e-status/)