How many files can E-Pen send in one transfer?

The current E-Pen v2.3 receiver safety limit is 100,000 files per transfer. The encrypted manifest is also capped at 32 MiB, so unusually long file or folder paths can reach the metadata limit before the file-count limit.

Does E-Pen store transferred files in cloud storage?

Transferred files are not stored in E-Pen cloud file storage. Normal mode prefers a direct WebRTC path and can use an encrypted TURN relay fallback when direct connectivity is unavailable.

Which browsers does E-Pen support?

Core encrypted transfers target current Chrome, Edge, Firefox, and Safari-class WebKit browsers. Direct folder saving depends on File System Access API support; other compatible browsers fall back to normal browser downloads.

Ryzova E-Pen

About Ryzova E-Pen™

Q: Does Ryzova E-Pen have a fixed file-size limit?

E-Pen does not set a fixed application-level per-file or total-transfer size cap. Practical limits depend on the browser, operating system, available storage, device performance, background-tab behavior, network stability, and whether the WebRTC path is direct or relayed.

Ryzova E-Pen™ is developed and owned by Ryzova™. It is a no-account browser-to-browser sharing suite for encrypted file transfer, Clipboard sharing, Drop Rooms, multi-receiver Broadcast, Nearby same-Wi-Fi transfer, and trusted-device handoff.

Company: Ryzova — https://www.ryzova.com/

A Ryzova product

Ryzova E-Pen™ is a proprietary Ryzova™ product. The service is operated under the E-Pen brand at epen.ryzova.com and is not presented as an open-source project.

Direct Send & Receive

Send files and folders from one browser to another over WebRTC with AES-GCM 256-bit browser-side encryption, PBKDF2 key derivation, chunked streaming, selective receive, reconnect recovery, and SHA-256 verification. Files are not stored in E-Pen cloud storage.

Nearby / Same Wi-Fi

For devices on the same Wi-Fi or LAN, the sender can enable Nearby mode. File-data ICE gathering stays local with STUN and TURN disabled for that transfer; the shared link or QR carries the setting to the receiver. Public rendezvous signaling is still used, so internet access is required.

Broadcast & Drop Rooms

Broadcast sends one selected file set to multiple receivers with independent transfer state and smart concurrency. Drop Rooms reverse the workflow so multiple senders can push encrypted files to one host browser.

Encrypted Clipboard & My Devices

Clipboard shares encrypted text, links, phone numbers, Wi-Fi passwords, and code snippets between browsers. My Devices stores pairing records locally in each browser and enables encrypted quick handoff while the paired target is online.

Large transfers, resume, and verification

Power features include resume checkpoints, live reconnect recovery, Game / Huge Folder mode, adaptive compression support, receiver file selection, transfer history, and SHA-256 integrity reporting. E-Pen does not impose a fixed application-level per-file or total-transfer size cap; practical limits come from the browser, operating system, available storage, device performance, background behavior, and network path.

Current v2.3 capacity and safety limits

The receiver accepts up to 100,000 files per transfer, with an encrypted manifest safety ceiling of 32 MiB. A single binary protocol frame is capped at 1 MiB, while normal file payload chunks adapt between 16–64 KiB. Resume snapshots expire after 24 hours. This is the current v2.3 protocol and safety envelope; real-world transfer speed and practical maximum size vary with browser, device, storage, and network conditions.

Broadcast

Up to 5 receivers • 2 active transfers at once

Drop Room

Up to 5 senders • 2 active transfers at once

Clipboard

Up to 8 room members • 200,000 characters per shared text item

My Devices

Up to 50 saved pairings • 16,384 characters per chat message

Pre-launch performance and stress validation

E-Pen v2.3 has been exercised with synthetic extreme-scale tests that use the real transfer and protocol code without sending destructive traffic to shared public infrastructure. Verified cases include a 100 GB logical transfer lifecycle, exact 2 TiB transfer counters, a 100,000-file manifest carrying more than 1 TiB of logical payload metadata, reconnect and backpressure recovery, AES-GCM corruption rejection, oversized-frame rejection, and repeated crypto soak tests. The 100,001-file and 1,000,000-file cases correctly stop at the current safety envelope rather than being advertised as supported.

These tests validate protocol logic, counters, metadata handling, recovery paths, integrity checks, and bounded memory behavior in the test environment. Physical long-duration transfer performance is environment-dependent and is measured separately from logical scale validation.

Cross-browser validation

Automated browser checks covered Chrome, Microsoft Edge, Firefox, Chromium, and WebKit/Safari-engine compatibility. Cross-engine small-file WebRTC transfers completed with integrity confirmed for Chromium ↔ Firefox, Chromium ↔ WebKit, Firefox → WebKit, and Chrome ↔ Edge. Mobile-width checks were also used to catch and fix Receive-page hydration and horizontal-overflow issues on Android-like Chromium and iPhone-like WebKit profiles.

WebKit automation provides Safari-engine compatibility coverage. Physical iPhone, iPad, and Mac behavior can vary with browser version, power-saving rules, storage permissions, VPNs, firewalls, and network quality.

No account required

E-Pen currently works without a user account. Transfer passwords stay in the shared link hash, and account or subscription services are not used as the file-transfer signaling or payload channel.

How the connection works

PeerJS Cloud is used as a public rendezvous service to help browsers find each other. File payloads are sent over WebRTC DataChannels. Normal mode prefers a direct path and can use TURN as a fallback; Nearby mode disables STUN/TURN for the file-data path and relies on local ICE candidates.

Browser compatibility

Modern Chrome, Edge, Firefox, and Safari can use the core encrypted transfer flow. Direct folder saving depends on browser support for the File System Access API; unsupported browsers fall back to normal browser downloads. Very large transfers remain subject to browser memory, background-tab, and network limits.