A pasted image becomes a remote file
A remote shell cannot use a file that exists only on your device. In a supported SSH file workflow, OmniTerm uploads the attachment first and then inserts the resulting remote path into the active terminal. This lets a remote tool use the uploaded file; it does not guarantee that every remote tool understands images.
Paste an attachment
- Connect to the intended server with working file-transfer access.
- Focus the terminal where you want the file path to appear.
- Paste the image or file, or use the attachment picker when clipboard access is unavailable.
- Wait for the upload to succeed and inspect the inserted path.
- Review the command or prompt before sending it to the remote application.
The attachment limits are 16 MiB per file, 32 MiB per batch, and 8 attachments per paste. Empty files are not accepted by this attachment workflow. Use the file tools for other transfer needs.
Understand the privacy boundary
The file remains on the destination unless you remove it or another retention policy applies. Ending a session does not promise to erase uploaded images. An assistant you run on the server may send the image to its own provider; review that tool's data handling separately.
Clipboard permissions vary by platform and browser. A blocked clipboard is not a failed server login: try keyboard paste or the file picker. When a remote program asks to read or change your clipboard, review the app's permission prompt rather than approving automatically.
Text paste can also display a safety review. Inspect multiline commands before accepting them. See SFTP transfers for checking destinations and AI assistance for provider considerations.