> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sndbox.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Upload File

> Upload an approved local file. Exact configuration, ports, placement, and execution behavior.

**Node type:** `upload_file` · **Version:** `1` · **Category:** Browser

Upload an approved local file. This node does not declare an external side effect.

## Configuration

| Field       | Type    | Default | What it controls                                                                         |
| ----------- | ------- | ------- | ---------------------------------------------------------------------------------------- |
| `locator`   | locator | `null`  | Recorded locator bundle. sndbox prefers accessible role/name data and retains fallbacks. |
| `file`      | path    | `""`    | Local file selected through the picker or mapped from a trusted path output.             |
| `timeoutMs` | number  | `30000` | Maximum time for this operation in milliseconds.                                         |

<Note>A trusted path output from an earlier node may be mapped after the file has been approved.</Note>

## Workflow JSON

The editor stores this node with the following implemented default configuration:

```json title="Default node configuration" theme={"system"}
{
  "type": "upload_file",
  "version": 1,
  "configuration": {
    "locator": null,
    "file": "",
    "timeoutMs": 30000
  }
}
```

Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See [Variables and data mapping](/workflows/variables-and-data).

## Inputs

This node has no typed ports in this direction.

## Outputs

| Port     | Type  | Required | Description |
| -------- | ----- | -------- | ----------- |
| `result` | `any` | No       | Result      |

## Where it can run

* Desktop local runner
* Paired self-hosted runner
* Managed browser worker

## Test and inspect

Use **Test node** in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.