Shayan
← Home

Picking files is not sending them

Nothing uploads when a sender drops files in. The transfer stays a draft until they press send, because a 2.7 GB upload is expensive to start and worse to restart, and people change the title, the message, or the expiry after they have already chosen the files. That left the client managing three states rather than one, and it is the reason an abandoned draft never becomes a live public link with somebody’s files behind it.

RushUploads transfer creation screen showing selected files, transfer settings, and a send button before upload begins.
Transfer creationFour files, 2.72 GB, nothing uploaded yet. Expiry and a 3,000-visit download cap are still editable, and the upload goes up in 10 MB chunks, three at a time.

The link appears last

A sender only gets a shareable URL once every file has finished uploading, so a half-uploaded transfer cannot be handed to anyone. From there they can copy the link themselves or have the product email a list of recipients, and the transfer starts counting visits against its cap.

RushUploads transfer-ready screen showing the share link, recipient notification field, and completed file uploads.
Upload completionAll four files confirmed, and now there is a link. Emailing eight recipients is optional; the link works on its own.

Recipients never sign up

Whoever receives the link can see the title, who sent it, the message, every filename and size, and when it expires, without an account and without an ad. Asking a stranger to register before they can tell whether the link is legitimate is how these products lose people.

RushUploads public transfer page showing sender, expiry, remaining visits, and a download button for each file.
Public recipient transferNo account, no countdown, no ad: just what is in the transfer and how long it lasts. 500 of 3,000 permitted visits remain.

Looking is free, downloading pays

The ad and its countdown live on a separate route from the transfer page, one file at a time. Recipients can therefore inspect a transfer as often as they like without generating revenue, and I keyed earnings to a finished countdown rather than a page view, since a page view is trivially inflated and advertisers are paying for attention. It costs the recipient one extra navigation on the way to each file, which is the honest price of the thing being free.

RushUploads download interstitial showing a three-second countdown, a disabled download button, and an advertisement.
Download interstitialThree seconds against one 24 MB file, with the download button disabled until the counter clears. The sender earns from this page, not the one before it.

Senders can see what they earned

The dashboard answers two questions at once: what is happening to my transfers, and what am I owed. Per transfer it shows visits against the cap, download and recipient counts, and expiry. Above that sits the balance, lifetime earnings, the rate being paid per visit, and the payout button once the threshold is met.

RushUploads sender dashboard showing earnings summary, CPM rate, payout threshold, and active transfer activity.
Sender dashboard$0.004 per recipient visit at a $4 CPM, $10 minimum before cashing out. 2,500 of 3,000 visits used on the one active transfer.

Anonymous uploads need a kill switch

Letting people publish files without an account means somebody has to be able to take them down. Admins can force-expire a transfer — deleting the stored objects rather than just hiding the page — disable users, and approve or reject payout requests with a written reason. They also set the CPM the whole earnings model runs on. What the console will not show them is recipient email addresses or credentials.

RushUploads admin console showing platform totals, transfer moderation, a pending payout request, and ad management.
Admin operations12,480 users, 3,216 live transfers, 8.4 TB stored. A pending $10 payout waits on approval, and the $4 CPM is editable in place.