# Team files

**Attach file** in a [Team conversation](/nock/team-messaging) sends one image or other file up to **2 MB** to another updated Nock Team inbox. It is a file transfer, not a shared drive, public upload, or grant of workspace access.

## Send a file

1. Open **Team & inbox** and choose the recipient's conversation.
2. Check that it is the right person and computer.
3. Choose the paperclip, **Attach file**, and select one file up to 2 MB.
4. Check the filename and size in the composer. Add a message if useful, or remove the attachment with **×**.
5. Choose the send arrow.

The file action is available only when that exact recipient advertises file support. Use an updated teammate's Nock inbox, not a shared coding chat or a standard outside-agent connection. The Team MCP messaging tools do not attach files. If the paperclip is unavailable, update the recipient's Nock or send a link through an appropriate service instead.

Both Nock computers need to be running to complete the transfer. A queued message is not proof that its file arrived. The sender's attachment card changes from **Waiting for file receipt** to **File received by their Nock** after the receiving Nock reassembles and verifies it. That receipt does not mean the person saved, opened, or read the file.

## Save a received file

The attachment card shows its name, size, and availability. Wait for **Ready to save**, then choose **Save file…** and select a destination in the save dialog.

Nock checks the completed bytes against the sender's file hash before making them available. It does not automatically open or execute an attachment. Images appear as downloadable files, not inline image previews. Save only files you expect from a sender you trust; integrity checking is not a malware scan.

Received files are available for **seven days**. Save a copy outside Team if you want to keep one. Archiving the conversation preserves its messages but does not keep its attachment bytes indefinitely.

## If the file stays unavailable

If the card says **Still arriving or unavailable**, leave both Nock computers open and check their connections. If it stays that way, ask the sender to remove the failed attachment and attach the file again. Check the text message separately; text being queued or visible does not confirm a complete file transfer.

Unsent and incomplete transfers expire after 24 hours. Temporary Team file storage is limited to 64 MB and 128 transfers. Reaching the limit blocks new transfers; it does not shorten the seven-day retention of completed received files. Expired temporary files are cleared automatically. If storage is full or the file is too large, send a link instead. Nock does not create a public file link for you.