Send files between phone and PC

No cable and no sign-in. Create a room on the left and scan it with the phone. On the right, switch between files, text, screen, and video. The browser connects the devices directly; a relay that deletes itself after 15 minutes is used only if that fails.

Next time, type this in the address bar txt.17nas.com

Not connected · create or join a room first
Connect a device on the left, then choose what to send on the right

Check it once. Neither side has to tap Save on every file. After the other device joins, it shows Save all. One tap packs the files into one archive in the downloads folder.

    Safety and privacy

    This is what the page actually does. It is for handing a file to another device for a short time. It is not an encrypted drive, and it is not absolute privacy.

    Direct transfers are not stored here

    Files, text, screen, and camera go between the two devices first. After a direct connection, that content is not stored on 17NAS. The site only helps the two sides find the room: the room code and the connection handshake pass through here. A public STUN server may also see the public IP.

    The relay expires, and files are not treated as web pages

    A file is stored on this machine only when a direct hole cannot be opened. The disk name is a random id. It is not placed in the web directory, and the sender folder path is not used as a server path, so the uploaded file is not executed. It is deleted after one download or after 15 minutes. Screen and camera do not use the relay.

    Rooms are hard to guess, and the first try is not blocked

    A room holds two devices. A wrong code, or a link to a room that does not exist, only shows a normal failure at first. After 5 failures in about 10 minutes, the image check appears. Creating a room, and returning to your own room after a refresh, does not ask for that check.

    Leave-for-later is a separate path

    You can leave a file when the other person is offline. Leaving it and picking it up both require sign-in. The file is on Cloudflare R2. The link contains a code, not the file name. It burns after 24 hours by default. You can shorten that, or burn it after a set number of opens. Time still deletes it.

    When to use this instead of a cable or WeChat

    Copying phone photos to a computer, sending a config file to a phone, or moving a short note to another device does not need a cable, and you may not want to sign in to a drive first. The table compares common options.

    Method Needs Where the content goes Fits
    Quick Transfer Any device that can open a web page Direct: only the two devices. Relay: deleted after 15 minutes A short transfer across systems, with no cable
    Cable / file app A cable or the vendor tool Local Frequent transfers, or very large files
    WeChat File Transfer A WeChat login Tencent servers Small files when you are already in WeChat
    AirDrop Apple devices, nearby Device to device Both devices are Apple

    What happens if a direct connection fails

    Same Wi-Fi

    Most home routers can open a WebRTC path. Large files and screen sharing stay between the devices. The server only carries the handshake.

    Mobile data ↔ a computer at home

    Symmetric NAT is common, so a direct connection may fail. Files then use the relay, so keep them within 32 MB. For screen or video, join the same network.

    Leave for later

    If a live room cannot open a hole, the file is still kept on this machine and deleted after 15 minutes. Leave-for-later uses Cloudflare R2 instead. Both leaving and picking up require sign-in, and the file burns within 24 hours.

    FAQ

    About phone–PC transfer, privacy, and relay limits.

    How do I send files from a phone to a PC without a cable?

    On the computer, open this page and tap Create room. The phone then sees a code and a QR code. Scan it with the phone camera, or open the same page in the phone browser and enter the 6-character code. After both sides connect, drop photos or documents onto the page. On the same Wi-Fi this is usually a direct browser connection. It also works across networks, though it may then use the timed relay.

    How is this different from WeChat File Transfer and AirDrop?

    WeChat File Transfer requires a WeChat login, and the file passes through Tencent servers. AirDrop only covers Apple devices. This tool runs in the browser: no app, and both sides do not have to be the same brand. When the direct connection works, the content stays between the two devices. It fits handing phone photos to a computer, or sending a NAS config file to a phone.

    Do files pass through 17NAS servers? What about privacy?

    The browser tries a direct connection first. When that works, files, text, screen, and camera are not stored on 17NAS. The site does see the room code and the handshake that connects the two devices, and a public STUN server may see the public IP. Only when a hole cannot be opened is the file kept briefly on this machine: a random id, not in the web directory, and not stored under the upload path. It is deleted after 15 minutes or after one download. Screen and camera do not use the relay. Leave-for-later requires both people to sign in. That file is on Cloudflare R2 and burns within 24 hours. This is a short transfer, not an encrypted drive.

    Why does it sometimes say it cannot connect directly and will use the relay?

    Home broadband, mobile data, and office networks often sit behind symmetric NAT or a firewall, so the browser cannot always open a hole. The relay is the fallback, not the default path. A direct connection is more likely on the same local network, or when at least one side has a public IPv6 address. The NAT test and IPv6 test on this site show the current network conditions.

    How long are relayed files kept, and is there a size limit?

    Three cases: (1) Direct (same LAN, or hole punching succeeds): files never touch the server, so there is no server-side size limit — but the receiving side currently buffers the whole file in memory before saving, so keep single files within the receiving device's available memory (a few hundred MB is safe on a 4 GB phone). (2) Relay: 32 MB per file, 256 MB total pool site-wide, files self-destruct after 15 minutes and are deleted as soon as they are downloaded once; text up to 32 KB. (3) Offline pickup (sign-in required, stored on Cloudflare R2): 100 MB per file, 1 GB total of un-burned files per account, up to 24 hours, up to 5 opens. Idle rooms expire after 30 minutes.

    Can I send photos and video, and also share a screen?

    Yes. File mode takes photos, documents, and archives. Text mode fits links and codes. Screen and camera use live WebRTC and only work after a direct connection. The relay does not forward audio or video, so this machine's bandwidth is not filled by a stream. Some iPhone browsers have limited screen sharing. Chrome, Edge, or Safari on a computer is more reliable.

    Do I need an account or an app? Is it paid?

    No. Open the page and use it. Sign-in is not required for the live transfer, and the tool is free. Do not use it for illegal content. Relayed files expire, but this does not replace an encrypted drive and it is not a place to keep files long term.

    Can I send files when the devices are not on the same Wi-Fi?

    Yes. The code is an internet room id. The devices do not have to be on the same local network. The same Wi-Fi makes a direct connection more likely and usually faster. A 4G or 5G phone sending to a computer at home will often use the timed relay. Keep those files within 32 MB, or join the same network before sending a large file.

    Can someone guess the code, or try room links at random?

    The code is 6 characters, and a room holds two devices. A wrong code, or a link to a room that does not exist, only shows a normal failure at first. After 5 failures from the same network in about 10 minutes, you must enter the characters in the image. Creating a room does not ask for that check. Someone already in the room who refreshes keeps the same seat and is not asked again.