socket.help

Temporary binary storage

Keep short-lived binary objects accessible to scripts.

Expires after 1 hour

Checking this session…

Drop a file hereAny file up to 10 MiB

Files start with a one-hour lifetime. Private links require an access token; public links work for anyone. Preview the selected file before uploading. Downloads keep the original file.

Open an existing file

About Temporary binary storage

Store nonempty binary data in an expiring resource and retrieve the original bytes through HTTP or the shared clients.

When to use it

Store nonempty binary data in an expiring resource and retrieve the original bytes through HTTP or the shared clients.

Temporary binary storage example
Use the shared file upload API or SDK upload method.
Download the exact original bytes with the returned access credential.
Delete or renew through the resource lifecycle API.

How to use it

  1. Select a file up to 10 MiB.
  2. Choose access and a download allowance.
  3. Upload and save the returned URL and credentials.

Limits & privacy

The text editor accepts up to 256 KiB; binary uploads accept up to 10 MiB. Resources start with one hour and use the same file storage, download allowances, sharing controls, and lifecycle as temporary file transfer. Private links contain only the ID; send the access token separately. Text is previewed without execution.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.