> ## Documentation Index > Fetch the complete documentation index at: https://evakage.docs.thesteau.com/llms.txt > Use this file to discover all available pages before exploring further. # Messages and files > Send, save, and retry temporary encrypted transfers. ## Send a message or file Choose **Open** beside a device or a room you have joined. In the conversation, type a message, choose **Attach File**, or drag and drop a file into the chatbox. An encrypted conversation between two paired browsers Messages and files are **end-to-end encrypted**. They go directly between browsers when possible. If that connection fails, encrypted content goes through the server relay. You can also enable **Via server** in the conversation toolbar. In a room, this switch is available only to devices signed into the account that owns the room. The server cannot read the content. It can see delivery metadata, including recipients and sizes. ## Save files you need A received file must pass its integrity check before you can save it. Verified files show **SHA-256 ✓**. A failed check offers a retry. Choose **Save** before closing the browser or before a server copy expires. When the app streams a relay download to disk, **Save** downloads the verified file again. Its server copy must still be available. ## Retry an interrupted transfer | Transfer | What to choose | | - | - | | Direct transfer | **Resume** keeps received chunks and sends what is missing | | Relay upload | **Restart upload** sends the file again from the beginning | | Relay download | **Restart download** fetches the file again from the beginning | **Gone** means the needed copy is no longer available. Ask the sender to send it again. ## How long server copies last The relay stores encrypted content temporarily while it waits for delivery. By default, a server copy becomes unavailable as soon as any applicable condition below is met: | Condition | Limit | | - | - | | All recipients have finished receiving or saving | Removed promptly | | All participants are offline | 15 minutes | | Only one participant remains in a direct chat | 3 hours; rooms are exempt | | Item age | 3 days | | Server restart or container replacement | Immediately | | Relay capacity is needed | Older items waiting for recipients may be removed once their uploads are complete | The app shows an expiry countdown. Once an item expires, you cannot start another upload or download for it. A download already in progress may finish. Disk cleanup runs every minute by default, but can be delayed. ## Capacity warnings The app warns online participants when a file or text budget reaches **80%**. If space is needed, the server first removes expired items. It then removes the oldest items of the same kind whose uploads are complete but which are still waiting for recipients. Affected online participants receive a notice. Files and text have separate budgets, so a full file buffer still leaves room for chat. Active uploads and downloads are protected from capacity cleanup. An item that cannot fit is rejected. Operators can adjust the [capacity limits](/hosting/configuration). Copies already on your device are not removed by server cleanup. ## Message yourself In **Devices**, choose **Open** beside **This is you** to send encrypted notes or files to yourself in the same browser profile. * Use the same browser profile to recover them after a reload. * Reconnect within **24 hours** of going offline. * Each item has a **3-day maximum age** and can be removed by capacity cleanup. * Clearing your browser identity prevents decryption. Server restarts erase these copies too. For implementation details, see the [relay design and measurements](https://github.com/thesteau/evakage/blob/main/maintainer/relay-memory.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.