Skip to content
Textual
Menu

Sending and receiving files

Use DCC transfers with a clear view of connectivity and privacy limitations.

On this page

Direct Client-to-Client, or DCC, transfers send a file directly between users rather than uploading it to an IRC channel. The transfer request includes connection information such as an IP address and port.

Receive a file

Open Window → File Transfers, then select or control-click the pending transfer to see the available actions. Accept files only when you expect them and trust their source; receiving a file is not a reason to run it.

Send a file

Control-click a nickname in the user list and use the Client-to-Client submenu, or drag a file onto that user. The recipient must accept the transfer and be able to reach the listening connection.

Connection problems

NAT, firewalls and carrier-grade NAT can prevent the recipient from connecting to you, whether you use Wi-Fi or a wired connection. Textual's documented behavior attempts automatic port forwarding with UPnP or NAT-PMP, but that depends on the router and network configuration.

If the sender's address cannot be determined, check the transfer settings and the actual network address rather than assuming that restarting will fix it. Do not expose unrelated services when changing firewall or forwarding rules.

The original documentation describes native IPv6 support, with compatibility depending on the other client. Its detailed error descriptions and transfer screenshot are preserved in the legacy DCC guide.

Transfer errors

Error What to investigate
No open port Whether Textual can open a listening port and whether the transfer settings conflict with another process
Could not read source file Whether the file still exists and Textual has access to it
Unknown source IP address Address discovery, connection settings, and the network path
Connection was disconnected Cancellation or an interrupted connection
Could not establish connection Reachability, firewall/NAT restrictions, and the sender's advertised address

Privacy limitations

The documented DCC file transfers are unencrypted. A TLS connection to IRC or an OTR private conversation does not encrypt the separate transfer, and a direct transfer can reveal your IP address to the other person. Choose another suitable transfer method when those limitations do not fit the file you need to share.

Keep reading

Source material

Adapted from the Textual knowledgebase, with related historical details preserved in the legacy library.

Need a hand? Contact us about this guide.

Textual screenshot