For senders · about 15 min

Send a very large package with RIPTON Desktop

Use RIPTON Desktop for the largest workloads and the longest routes: install it, let the browser hand the package to it, pick local files with the native picker, and follow throughput and recovery from the app.

You end up with
A package moved over the accelerated RIPT protocol from your workstation, with measured throughput and automatic recovery from interruptions.
Plan
All plans. RIPTON Desktop runs on macOS, Windows and Linux.
Updated

Before you start

  • RIPTON Desktop installed on the workstation that holds the files. Your administrator provides the installer for your platform.
  • Network access from that workstation to the transfer node on UDP ports 33001 to 33008. Your administrator confirms this; it is the usual reason Desktop transfers do not start.
  • A workspace account that can send packages.

Steps

  1. Open RIPTON Desktop

    Start RIPTON Desktop and leave it running. It has no files to show yet; the browser will hand it a package to move.

  2. Open Send in the browser

    Workspace · Send

    Sign in to your workspace on the same workstation and open Send. The page detects Desktop and says so under Files: 'Choose files or folders here. RIPT Desktop opens the native picker and keeps local paths private.' If it does not, see troubleshooting before continuing.

  3. Add recipients and a title

    Add recipient emails in Recipients and enter a Title. Set an Expiration date or Release date under More options if the delivery needs one.

  4. Pick the files in the native picker

    Select Add files or Add folder. RIPTON Desktop opens your operating system's file dialog. Choose the folder or files; the browser shows the count and total size but never sees local paths.

  5. Send

    Select Send package. The browser creates the package and authorizes Desktop to move the bytes. The message 'Package created, uploads continue in the background' confirms the handoff.

  6. Watch it in Desktop

    RIPTON Desktop · Transfers

    Switch to RIPTON Desktop. The transfer shows measured throughput, progress, and state. If the network drops, the transfer resumes from the last confirmed block when the link returns; you do not need to restart it.

  7. Confirm completion in the workspace

    Open Sent and select the package. Its status becomes complete when every file has arrived on the node and been verified.

How you know it worked

  • RIPTON Desktop lists the transfer as complete with the expected byte count.
  • The package in Sent shows all files present, and the Activity tab records the completion.
  • The recipient downloads and the SHA-256 of a sample file matches the original.

If something is off

What you seeWhat to do
The Send page does not detect DesktopMake sure RIPTON Desktop is open on the same machine as the browser, then reload the Send page and accept any connection prompt. If detection still fails, ask your administrator to check browser-to-Desktop connectivity for your platform.
Desktop shows the transfer waiting or failing to connectThe workstation cannot reach the node's UDP ports. Ask your administrator to check the node's firewall or security group for UDP 33001 to 33008 and to run Check connectivity on the node.
Throughput is lower than expectedDesktop reports the rate it achieves on your route. Compare it with a plain HTTPS upload of the same file to see the difference on that path, and share both numbers with your administrator if the node looks underprovisioned.