From open tab to transferred file

1. 01

   Open FileTransferX

   Go to filetransferx.com in any modern browser. No install needed — direct P2P transfers work without an account.

2. 02

   Choose Send or Receive

   Pick Send Files on the device that has the files, and Receive Files on the device that should get them.

3. 03

   Select Files

   On the sending device, drag files in or choose them, then review the list before anything is sent.

4. 04

   Connect Devices

   The sender gets a QR code and a short transfer code. The receiver scans the code or types it in.

5. 05

   Transfer

   Once connected, files move in chunks with a live progress bar, speed, and estimated time remaining.

6. 06

   Receive

   The receiving device reviews the incoming files and chooses to accept before anything downloads.

Pairing: QR code or short code

Every send session generates two things that represent the same temporary transfer: a QR code and a short, human-friendly code such as X7K9-P2. A QR code is fastest when a phone is receiving, since it can just scan the sender's screen. A typed code is more practical between two computers, where scanning isn't an option. Both always work, so you're never stuck without a camera. Codes are short-lived and tied to a single transfer session — they are not accounts or permanent identifiers.

Sending text instead of a file

The same pairing and the same direct connection also power Transfer Text, a companion tool for sending a short message device to device rather than a file. Choose Send Text or Receive Text, pair with a QR code or short code exactly as above, and the message appears on the other device the moment it is sent. It is meant for the things that are quicker to beam across than to retype — a Wi-Fi password, a one-time verification code, a link — and, like a file transfer, nothing is stored and closing the tab clears the session.

The connection: direct, with a fallback

Once paired, FileTransferX first attempts to connect the two devices directly. A direct connection means the data channel runs peer-to-peer, without a server relaying the file data — and no account is needed. Establishing that direct path relies on standard connectivity techniques to discover how each device can be reached.

Some networks — strict corporate firewalls, certain mobile carriers — block direct peer-to-peer connections. When that happens, FileTransferX falls back to a secure relay, which forwards the encrypted connection between the two devices. Relay transfers require a free account so we can track and manage relay usage per user. In that fallback path, file data does pass through the relay server in transit; it is not attempting a direct connection to "never touch a server" in every case, only when the network allows a direct path.