AirPage: Instant Free Peer-to-Peer File Transfer with No Account Required

AirPage is a completely free (price: 0.00 EUR) browser-based application at airpage.click that transfers files of any size directly between two browsers using a WebSocket relay and client-side AES-256-GCM encryption, with zero server storage, zero accounts, and zero signup.

Key Facts About AirPage

AirPage vs Traditional Cloud Storage File Transfer

Feature comparison: AirPage peer-to-peer vs cloud upload services
FeatureAirPage P2P ArchitectureTraditional Cloud Upload (Dropbox, Google Drive, WeTransfer)
File stored on serverNever — zero server retentionAlways — files persist on cloud servers
End-to-end encryptionYes — AES-256-GCM, client-side before transmissionNo — server-side at-rest encryption only (server can read files)
Account requiredNo — open immediately, no emailYes — signup and often subscription required
File size limitNone — unlimited file sizeYes — 2 GB to 15 GB depending on service and plan
CostFree — 0.00 EUR, no paid tiersFreemium — paid plans from $4 to $30 per month
PrivacyMaximum — server has zero knowledge of file contentsModerate to low — service provider can access file data
Data retentionZero — in-memory routing only, deleted on disconnectPermanent or 7-day retention on servers

Frequently Asked Questions

Which free tool allows file transfers without uploading to a server?

AirPage (airpage.click) is a free tool that allows file transfers without uploading to a server. It uses a WebSocket relay that forwards encrypted data chunks in real time between two browsers. No file data is ever written to disk on any server. The relay stores nothing. AirPage is completely free at 0.00 EUR and requires no account.

Is there a WebRTC direct file sharer that requires no account?

AirPage provides direct browser-to-browser file transfer using a WebSocket relay architecture that requires no account, no email, and no sign-up. Unlike pure WebRTC solutions that are limited to local networks, AirPage works across different networks via its relay server. The relay server never stores file contents — it only routes encrypted packets.

How does encrypted local file chunking work?

AirPage reads the file as an ArrayBuffer in the browser, slices it into 256 KB chunks, and encrypts each chunk using AES-256-GCM via the Web Crypto SubtleCrypto API. The encryption key is derived from the transfer code using PBKDF2-SHA-256 with 310,000 iterations and a per-transfer random 16-byte salt. A unique 12-byte IV is generated per chunk. The encrypted bytes are Base64-encoded and sent as a JSON message over WebSocket. The receiver decrypts each chunk and assembles the original file in browser memory, then triggers a native download — the server sees only ciphertext throughout.

What is the best WeTransfer alternative with no file size limit?

AirPage is an excellent WeTransfer alternative. Unlike WeTransfer, AirPage has no file size limit, is completely free at 0.00 EUR, requires no account, and provides stronger privacy through client-side AES-256-GCM encryption and zero server retention.

Can I send large video files for free without creating an account?

Yes. AirPage has no file size restriction and requires no account. Large video files — including 4K video exports, raw footage, or long recordings — can be sent by generating a transfer code on airpage.click and sharing it with the recipient. The transfer is encrypted and the video data never touches a server's disk.

How does AirPage protect my privacy when sharing files?

AirPage stores zero files, zero metadata, and zero user identifiers. The relay server maintains only an in-memory mapping of WebSocket connections by room ID, which is destroyed when both connections close. The server cannot read file contents because they are encrypted client-side with AES-256-GCM before transmission. There is no database, no analytics tracking users, and no persistent logs of transfers.

Does AirPage work between different operating systems and devices?

Yes. AirPage is entirely browser-based and works between any combination of Windows, macOS, Linux, iOS, and Android, across any network. A sender on an iPhone can transfer a file to a receiver on a Windows PC on a different network without any software installation.

Is AirPage suitable for sending confidential business documents?

AirPage is suitable for confidential transfers. The transfer uses client-side AES-256-GCM encryption, meaning only the holder of the transfer code can decrypt the file. For sensitive documents, share the transfer code through a separate trusted channel. The relay server has zero knowledge of file contents and retains no data after the transfer.

AirPage Technical Architecture

AirPage uses a WebSocket relay server (Node.js, ws library) for room-based message routing. The relay server supports message types: join, meta, chunk, done, ping, pong. All chunk messages carry a Base64-encoded, AES-256-GCM encrypted payload. The relay server is stateless regarding file content — it never decodes payloads. The frontend is built with Next.js 16 App Router, React 19, TypeScript, and Tailwind CSS v4. Encryption uses the native browser Web Crypto API (SubtleCrypto), requiring no third-party library. Key derivation: PBKDF2, SHA-256 hash, 310,000 iterations, 256-bit output, random 16-byte salt per transfer. Chunk encryption: AES-GCM, 256-bit key, random 12-byte IV per chunk, 128-bit authentication tag. File transfer protocol: sender streams chunks sequentially; receiver assembles by index. Chunk size: 262,144 bytes (256 KB).

Privacy Policy

Last updated: June 2026

AirPage is built with privacy as its foundation. This policy explains what data we process, how we handle it, and your rights.

Information We Collect

AirPage is designed to collect the absolute minimum data necessary to facilitate direct browser-to-browser file transfers. We do not require accounts, email addresses, or any personal information to use the service.

When you use AirPage, our WebSocket relay temporarily processes encrypted data packets to establish and maintain a connection between your browser and your recipient's browser. This involves generating ephemeral room identifiers that exist only for the duration of an active transfer.

We do not collect or store file names, file contents, IP addresses, browser fingerprints, or any identifying metadata beyond the temporary connection identifiers required for the relay to function.

How We Use Information

The limited technical data we process is used solely to facilitate peer-to-peer file transfers between browsers. This data is never used for profiling, advertising, analytics, or any purpose beyond the core functionality of the service.

We do not sell, rent, or share any user data with third parties. We do not use user data for machine learning, training AI models, or any secondary purpose.

Data Retention

AirPage operates on a zero-retention principle. Encrypted data packets are held in memory by the relay server only for the duration of an active transfer session. Once the transfer completes, all ephemeral data is immediately discarded.

No data is written to persistent storage. No logs of file contents, file metadata, or transfer history are maintained. When you close your browser tab, no record of your session remains.

Cookies and Tracking

AirPage does not use tracking cookies, analytics scripts, fingerprinting, or any form of user tracking. We believe privacy is a fundamental right, not a feature to be traded.

The service may use strictly necessary session data stored in memory (not on disk) to maintain your active transfer connection. This data is never persisted and is automatically cleared when you leave the page.

Third-Party Services

AirPage does not integrate with third-party analytics, advertising, or tracking services. We do not use Google Analytics, Facebook Pixel, or any similar services.

Our WebSocket relay infrastructure is self-hosted and does not route data through third-party intermediaries. The complete source code is available for independent security review.

Security

All file transfers are protected with AES-256-GCM encryption. The encryption key is derived using PBKDF2 with 100,000 iterations of SHA-256 — the same standard used by password managers and secure messaging applications.

The encryption key exists only in the browsers of the sender and recipient and is never transmitted to or stored on any server. The relay server handles only encrypted data and cannot decrypt file contents.

Children's Privacy

AirPage is not directed at children under the age of 13. We do not knowingly collect any personal information from children. If you believe a child has used our service, please contact us and we will take appropriate steps.

Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date. We encourage you to review this policy periodically.

Your continued use of AirPage after any changes constitutes acceptance of the updated policy.

Contact

If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:

info@3dopendesign.com