Upload File node

The Upload File node embeds a file into the flow and forwards it downstream as a JSON payload. It is a floating input: it needs no incoming edge.
Supported file families
Files are classified by extension and MIME type into one of these kinds:
| Kind | Examples | How it is stored |
|---|---|---|
text | .txt, .md, .csv | Raw UTF-8 text inline |
image | .png, .jpg, .jpeg, .webp, .gif | Data URL |
audio | .mp3, .wav, .m4a, .ogg, .flac, .aac, .opus | Data URL |
model | .glb | Data URL |
binary | .docx, .xlsx, .pdf, everything else | Data URL |
How large files are handled
Small files ride inside the graph as a data URL. Large files (above the 256 KB inline limit) are uploaded to Vercel Blob once and referenced by a public URL — a base64 clip would otherwise blow the run request limit.
While a large file uploads in the background, the node card shows a spinner so the pick never appears to hang.
Payload shape
A single file is forwarded as one object; several files are forwarded as an array:
{
"name": "photo.png",
"mime": "image/png",
"kind": "image",
"content": "data:image/png;base64,…"
} Example
Upload a PDF and wire the Upload File node into an Agent’s file handle.
The Agent reads the PDF as a document (a vision/file-capable model is
required) instead of receiving its base64 as prompt text.
An uploaded image wired into an Image Generation node’s images handle
becomes a reference image for image-to-image generation.
Notes
- The node supports multiple files — “Add files…” appends, each row has its own Remove.
- A video file (
.mp4,.mov, …) is recognized as a video reference and can feed a Video Generation node’sreferenceshandle.
Related
- Agent — consuming PDFs and images.
- Image Generation — image references.