Transfer Text and Files Between Phone and PC with QR Code and P2P

Use a fast QR mode for links and short text, or pair two browsers with WebRTC to send larger files and longer text directly between devices.

Use this tool

Carregando...

Quick guide and practical context

Two modes for two different jobs

The simple mode is designed for short payloads such as links, temporary passwords, Pix payloads, crypto addresses, terminal commands, and compact JSON. The QR itself carries the content or a client-side URL fragment.

The advanced mode handles larger text and files. It uses QR codes only for the initial handshake and then moves the main payload through a WebRTC DataChannel.

When the QR mode is the best choice

If you only need to move something small from one screen to another, QR is the fastest option. It avoids account creation, avoids manual typing, and works well on mobile and desktop.

When content grows beyond practical QR limits, the tool can split it into multiple parts, but larger payloads are usually better served by the P2P mode.

How the WebRTC transfer works

One device creates a WebRTC offer, the other responds with an answer, and both browsers open a direct data channel. Files are sent in chunks so the receiving browser can reconstruct them safely.

This implementation can use STUN for route discovery, but it does not include a TURN relay. That keeps the tool closer to direct transfer, while also meaning some restrictive networks may fail to connect.

Privacy and practical limits

Short-text QR processing stays local in the browser. In P2P mode, the main payload travels through the browser data channel after manual pairing. Network topology still matters, and direct connectivity is not guaranteed on every firewall or NAT setup.

QR capacity is also finite. If a payload becomes too large, splitting or switching to P2P is the correct fallback.

Frequently asked questions

Does this tool upload my content to a server?

Short QR mode is processed locally in the browser. In P2P mode, the main payload goes through WebRTC between the devices. Optional STUN may be used for route discovery, but there is no TURN relay in this implementation.

Do I need an account or app?

No. The tool is designed to work directly in the browser with no sign-up and no dedicated app.

Can I scan the QR from inside the website?

Yes. On compatible browsers you can use the camera directly on the page or import a QR image. On many phones the image picker can also open the system camera.

Why can the P2P connection fail?

Because this build relies on direct WebRTC connectivity with optional STUN and no TURN relay. Restrictive corporate networks, hard NAT, or aggressive firewalls may block the session.

Helpful links to continue similar tasks without starting over.

Privacy and local processing

Tools on this page run directly in your browser and do not send entered content to a backend. This improves privacy and reduces latency.

Transfer Between Phone and PC with QR Code and P2P | Tools Lucasqc