Size caps and silent failures
Attachment limits, browser uploads that restart from zero after a hiccup, and links that expire before the other side has downloaded.
Send large files
Send large files to anyone, without splitting, zipping, or shipping drives.
Email stops at a few tens of megabytes and consumer sharing tools slow down or fail on multi-gigabyte files over long distances. RIPTON CLOUD sends the file as a package: you choose recipients, they get a scoped link, and the transfer uses a path built for large data.
Plan limits are those published on the pricing page. Benchmark figures come from RIPTON CLOUD's published EC2 test at roughly 150 ms latency and 3% packet loss; results on your route depend on your network and endpoints.
Evaluated transfer path
01
Your files
02
Browser or RIPTON Desktop
03
RIPTON node
04
Recipient download
Why sending big files is still hard
The file is not the problem. The path is.
A 40 GB file is ordinary for video, design, engineering, and research teams. The tools most people reach for were built for documents, and they show it the moment a file crosses a continent or a lossy Wi-Fi link.
Distance makes it slow
Ordinary TCP transfers lose most of the available bandwidth as latency and packet loss rise, so a fast link still delivers slowly.
No proof of delivery
You send, you wait, you ask. Nobody can see whether the recipient downloaded the right version, or when.
Workflows
Where the transfer path matters most.
Masters · deliverables · signed documents
Send to a client or partner
Create a package, add recipient emails, and send. Each recipient receives a scoped download link; they do not need an account or a paid seat.
Project trees · image sequences · exports
Send a whole folder
Select a folder in the browser or in RIPTON Desktop and send it as one package with its structure intact, however many files it holds.
Vendor deliveries · submissions · returns
Receive from outside your company
Give partners a Shared Inbox or a public upload link so they can send large files to you without an account and without email round trips.
RIPTON CLOUD in the workflow
What you get when you press send
The product earns its place by moving prepared data between endpoints—not by claiming ownership of every system around it.
No size gymnastics
Free plans allow files up to 10 GB, Starter up to 100 GB, and Professional and above have no file-size limit. Folders travel as a single package.
Encrypted on every packet
AES-256-GCM or ChaCha20-Poly1305 with a fresh key per session. There is no setting that sends in plaintext.
Two ways to send
A browser is enough. For the fastest path over long or lossy links, RIPTON Desktop moves the same package over the accelerated transfer protocol.
Delivery you can see
Progress while it sends, a record when each recipient downloads, and expiry you set rather than a default you discover later.
No generic speed promise
How fast a package arrives depends on your route, endpoints, and the other side's connection. The Free plan lets you find out on a real file before paying anything.
Product boundary
Built for sending, not for syncing.
RIPTON CLOUD sends packages between people and systems. It is not a shared drive, a backup tool, or a replacement for email itself.
What it covers
- Large files and folders sent as packages
- Recipient links without accounts or seats
- Inbound sending through Shared Inboxes and public links
- Delivery visibility and expiry
What stays with your stack
- Continuous folder synchronization
- Backup and restore scheduling
- Document editing or collaboration
- Media asset management
Evaluation path
Try it on the file you could not send last time
The Free plan is enough to send real files today. If the path is long, lossy, or the files are very large, a guided evaluation shows what RIPTON Desktop adds on your route.
- 01
Start a free workspace
Three named users, one Shared Inbox, 25 GB of transfer a month, and files up to 10 GB, at no cost.
- 02
Send one real package
Pick the file or folder that failed elsewhere. Add a recipient and watch the transfer and the download record.
- 03
Measure the difficult route
If a location or partner is consistently slow, run the same package with RIPTON Desktop and compare elapsed time on that path.
- 04
Pick the plan that fits
Published prices, published limits, and no charge for the people who only receive.
FAQ
Questions technical buyers ask.
How large a file can I send?
It depends on the plan: 10 GB per file on Free, 100 GB on Starter, and no file-size limit on Professional, Business, and Enterprise. Folder packages can contain any number of files within the plan's monthly transfer allowance.
Do recipients need an account?
No. Recipients receive a scoped link and download in a browser. They do not use a named seat, so there is no charge for the people you send to.
Is a browser enough, or do I need to install something?
A browser is enough to send and receive. RIPTON Desktop is optional and adds the accelerated transfer path for very large packages or long, lossy routes.
How is it different from emailing a link to a cloud drive?
A package is sent to named recipients with expiry and a delivery record, encrypted on every packet, over a path designed for large data. A drive link is a permission change on a shared folder, with whatever transfer speed the drive gives you.
Will it be faster than what I use now?
On short, clean links most tools are fine. The difference appears with distance, latency, and packet loss, where in our published EC2 tests a 1 GB file finished 7.5x faster than the TCP baseline. Your route is the real test, which is why evaluations run on it.
Technical evaluation
Send the file that would not go.
Start a free workspace, or bring the route that keeps failing and we will help you measure it.