Skip to main content
XRTX Logo
XRTXGROUP
Contact us
Browser-to-Browser WebRTC

XRTX Transfer

Direct, end-to-end encrypted file transfers between devices. Files travel peer-to-peer and are never uploaded to XRTX infrastructure.

AES-256-GCM + ECDHZero Cloud Storage
Operational Security Advisory & Safe Transfer Policy

Never enter or transmit sensitive credentials or private keys: Do not use this tool to transmit root passwords, SSH private keys, seed phrases, unencrypted database credentials, or classified operational secrets across untrusted endpoints or unverified sessions.

Endpoint Security Boundary: Browser transport encryption protects data in transit between peers, but cannot safeguard against compromised operating systems, resident malware, screen captures, or untrusted recipients.
Execution Warning: Cryptographic verification guarantees that file bytes were not altered during transit; it does not guarantee that received files are safe to execute. Never open unverified executables or scripts without sandbox inspection.

Drop files here or click to browse

Multi-gigabyte streaming supported • Encrypted in browser memory • Never stored on servers

How XRTX Transfer Works

01 / Ephemeral Session

Session Creation

Your browser creates an ephemeral session and generates a fresh ECDH cryptographic keypair in browser memory.

02 / Private Out-of-Band Pairing

QR & Fragment Binding

The receiver connects via QR or pairing link. Secret pairing material resides in the URL fragment (#) and is never sent to the server.

03 / Key Exchange & SAS

Authentication

Peers perform ECDH key agreement and display identical 6-digit verification codes to prevent any MITM attacks.

04 / Direct P2P Channel

WebRTC DataChannel

Files travel directly from device to device over encrypted SCTP. XRTX servers never receive the data stream.

05 / Relay Fallback

TURN Relay Protection

If strict firewalls prevent direct P2P, encrypted chunks relay through TURN without exposing plaintext file contents.

06 / Integrity Verification

AEAD & SHA-256 Check

Every chunk uses AES-256-GCM authentication tags, and the full file is verified with SHA-256 before completion.