DCC explained: IRC's peer-to-peer file transfers

IRC channels carry text only — no attachments, no inline images. What IRC has instead is DCC (Direct Client-to-Client): a mechanism where two users negotiate, over the IRC server, a direct connection between their machines for private chat or file transfer. The server brokers the handshake; the data itself never touches it.

How it works #

A DCC offer is a CTCP message: DCC SEND filename ip port size. The sender's client opens a listening port and tells the receiver where to connect; accept, and the file flows peer-to-peer. DCC CHAT does the same for a direct private conversation that bypasses the server entirely.

Because the connection is direct, both sides see each other's IP address — and because one side must accept an incoming connection, DCC has been at war with NAT and firewalls since home routers were invented. Passive/reverse DCC flips who connects to whom, which fixes the case where exactly one side is unreachable. When both are behind strict NAT, DCC simply fails, which is the main reason its everyday use faded in favor of pasting an HTTPS link.

XDCC: the file-server culture #

XDCC turned DCC into infrastructure: bots holding file catalogs, serving them on request (/msg bot xdcc send #4). XDCC networks were a major distribution channel in the 2000s — and remain associated with piracy, so treat random XDCC offerings with the same legal and security judgment you would any unlicensed download.

The safety rules (these never expired) #

DCC is the historical malware vector of IRC, and the old rules still apply verbatim:

• Never accept files from strangers. No exceptions, no curiosity.
• Auto-accept off. Verify your client does not accept DCC automatically; modern clients default safely, old configs may not.
• Mind the IP exposure. Accepting any DCC reveals your address to the peer; a bouncer on a VPS conveniently makes that the VPS's address instead.
• A file named funny.jpg.exe was the classic trick in 1999 and still works on someone every year.

Should you use DCC in 2026? #

For files between people who trust each other and have working connectivity, it is still pleasingly direct — no third-party host, no size limits beyond your bandwidth. For everything else, the pragmatic answer is the one the culture already settled on: upload somewhere and share the link in channel (pastebin discipline applies to files too). But when someone offers you a "DCC SEND" out of nowhere, you now know exactly what it is — and that the correct response is to decline.