Browser sharing · No account required

Transfer files from iPhone to PC without a cable

To send a file from iPhone to PC, open Textunnel in Safari and your PC browser, join the same room, then wait for File channel ready. On iPhone, choose the file with the attachment button. Accept it on the PC if prompted, download the completed file and open the saved copy. Keep Safari in the foreground until the handoff finishes.

How to use it

  1. Connect both devices to the same Wi-Fi, open the same room and confirm any room password matches.
  2. On iPhone, use the attachment button to choose a file from Files or your media picker. The picker controls what file representation is selected.
  3. On the PC, accept the transfer if prompted. Keep Safari in the foreground until receiver verification finishes.
  4. On the PC, wait for completion, use Download and open the saved file from your browser's download list or chosen folder. Save before closing or refreshing either tab.
iPhone-to-Windows step-by-step guide

Choose the document, photo or video on iPhone

For a PDF, ZIP archive or document, first check that you can open it in the Files app. If it is only a cloud placeholder, let the source app download it before selecting it in Safari. Use the attachment button in the room and choose the location containing that file.

For a photo or video, select it through the media picker where offered, or save the file to Files and select that copy. The picker determines the representation Safari supplies. If the receiver needs an exact original file, check the file name, type and size rather than assuming the picker exported the original.

Start with one small file on a new device pair. Once you can receive, save and open that copy on the PC, continue with the larger files. This checks the full handoff rather than only room discovery.

Find the saved copy on the PC

Received by 1/1 on the iPhone confirms the receiving application verified the file for that recipient. On the PC's receiving card, use Download, complete any save prompt and open the file from the browser's downloads list. The destination depends on the browser's download settings.

Check that the saved document opens in its intended application. A download that completed successfully can still contain a format that the PC's installed viewer does not support; that is a separate issue from whether the transfer finished.

For the reverse direction, choose the file on the PC, receive it in Safari and save it to Files. Keep the receiving page until you have checked that saved copy. An old card after a reload can retain its name without retaining downloadable bytes.

When the PC does not appear or the file stops

Confirm the exact room code and password on both devices. If the main action still says Connect receiver, opening this page on the PC is not enough: enter the same room and check the device panel. A connected label alone does not establish File channel ready.

Guest Wi-Fi isolation, firewall rules and VPN local-network routing can prevent a direct path even when both devices use the same Wi-Fi name. Keep network protections in place; on a managed network, ask whether device-to-device access is allowed. A text message arriving does not prove that the file channel is ready.

If Safari was locked or moved to the background, return to the original tab, wait for reconnection and ask the sender to Retry. Eligible checkpoints can save repeated transfer work under the recovery rules in the transfer guide; reconnection alone does not restart a failed file.

What to check in the room

Textunnel received file card with its Download File action
Real Textunnel interface captured October 20, 2026 after a verified file transfer. Use the download action, then your browser or system save flow. On iPhone, save to Files before refreshing Safari. These are controlled desktop-browser sessions at a narrow viewport, not iPhone or Windows system screenshots.

Limits and connection conditions

Use a current PC browser with WebRTC support. On iPhone, keep Safari active and save received files before refreshing. File size and saving options depend on the receiving browser; use the limits below when choosing a route.

Text and clipboard messages: 64 KiB encoded message limit
Use a file for larger content. Clipboard permissions and foreground access still apply.
MQTT file fallback: 25 MiB per file
Both peers must explicitly allow relay in their current tabs.
Share links and folder packing: 256 MiB
Keep the source page open. Browser memory, storage and network limits apply.
Room reception above 256 MiB: Supported disk-saving API required
Choose a receiving browser with disk-saving support for larger files, and check available storage before starting.
Interrupted-file checkpoints: Up to 256 MiB for 10 minutes
Return to the page, reconnect, then sender Retry. Cross-refresh recovery requires opting in before transfer; four temporary records maximum, unencrypted at rest.

WebRTC transport is encrypted. Public-room MQTT content needs a room password for encryption against the broker. Internet content relay requires explicit permission in each tab. History and optional recovery use device storage; the site also uses analytics and advertising scripts.

Privacy, relay permission and full transfer guide

Verified transfer workflows

Maintained by the Textunnel team · Content reviewed 2026-11-04 · Physical acceptance record: October 18, 2026

In same-Wi-Fi tests between iPhone Safari and Mac: 1 MiB and 64 MiB saved and returned over WebRTC; returned SHA-256 matched the source. A 64 MiB rejection also reached the sender correctly.

These checks confirm the tested workflows, rather than a fixed transfer speed. For interrupted transfers, return to the page, reconnect and ask the sender to Retry.

A separate cloud Windows Server 2025 / Chrome 155.0.8059.85 check passed 1 MiB and 64 MiB file round trips with matching download hashes and a refusal check. It used two browsers on one virtual machine; it does not establish an iPhone-to-Windows or Android physical-device result. Windows environment and results.

Detailed transfer test results

Frequently asked questions

Is this AirDrop for Windows?

No. This is browser-based WebRTC sharing, not Apple AirDrop. Both devices must open Textunnel and connect. Use a current PC browser with WebRTC support and keep both pages open during transfer.

Why is an old iPhone file card not downloadable?

A refresh can leave a history card without its file bytes. The card explains that the file is unavailable in this page. Ask the sender to send it again, and save before refreshing.

Will a large video continue while iPhone is locked?

Do not rely on that. Locking or backgrounding Safari can interrupt transmission. Return to Safari, wait for the channel to reconnect and ask the sender to Retry. Eligible verified prefixes can resume within the documented limits.