Does the FilePost n8n node accept binary data?

Yes. Select the binary property produced by the previous n8n node, normally data.

Can I upload base64 content from an AI or webhook node?

Yes. The Upload Base64 operation accepts a base64 string or data URL and returns a public CDN URL.

Can n8n uploads expire automatically?

Yes. Set an optional lifetime such as 24h or 7d in the FilePost node.

n8n File Upload Node — Turn Binary or Base64 Data into a Public URL

One node across the file boundary

Automation tools handle JSON beautifully. Files are where workflows become awkward: binary properties, base64 payloads, temporary attachment URLs, and APIs that only accept public links. FilePost gives those files a stable URL so the rest of the workflow can stay simple.

Binary in

Map the binary field from Gmail, HTTP Request, Forms, Drive, or any previous n8n node.

Base64 in

Upload output from AI image, document, database, and webhook nodes without an intermediate conversion step.

Public URL out

Receive the URL, file ID, size, content type, expiry, and filename mode as normal JSON.

Install and connect in about two minutes

On the n8n canvas, search for FilePost and add the verified community node.
Create a free FilePost API key, then add it as a FilePost credential in n8n.
Choose Upload File for binary data or Upload Base64 for a string or data URL.
Use {{$json.url}} in the next node.

Import a working starter workflow

These workflows are deliberately small. Import the JSON into n8n, select your FilePost credential, and adapt the trigger or destination.

Webhook file → public URL

Accept a binary upload, store it with FilePost, and return the URL in the webhook response.

Remote file → permanent URL

Receive a temporary file URL, download it as binary, then return a FilePost CDN URL.

Base64 → public URL

Receive base64 data from a webhook or AI step and publish it without a conversion node.

The webhook starter accepts one multipart file field with any name. After importing it, start a test execution and call its test URL like this:

curl -F "file=@invoice.pdf" YOUR_N8N_TEST_WEBHOOK_URL

Controls that belong inside the workflow

Expiry: set 30s, 24h, 7d, or another supported lifetime for disposable files.
Filename visibility: keep the original name hidden or show it in the public URL.
File management: list, inspect, and delete uploaded files from later workflow steps.

Prefer to inspect the implementation? The package is open source on GitHub. For HTTP-only workflows, see the API reference.

Questions we actually get

Does the node work in n8n Cloud?

Yes. FilePost is a verified community node, so you can add it directly from the n8n Cloud canvas. It also works on self-hosted n8n.

Which binary property should I select?

Most n8n nodes output the file on data. If the previous node uses another name, enter that binary property name in the FilePost node.

Can I upload a base64 data URL?

Yes. The Upload Base64 operation accepts both a plain base64 string and a complete data:...;base64,... URL.

What does the next node receive?

Normal JSON containing url, file_id, name, size, content_type, expires_at, and filename_mode.

Your workflow has a file. The next node needs a URL.