No install required
Send files directly to browsers and temporary devices. Perfect when the other side cannot install software — client machines, guest devices, or one-off shares.
Reliable device-to-device transfer
File transfer that works across any network.
LAN when possible. Relay when needed. Resume when interrupted. ShrimpSend keeps your own devices connected when ordinary tools give up on unstable or restrictive networks.
Available for macOS, Windows, Android, iOS, and Web.
Transfer session
Resuming8 GB video — reconnect and continue
Network dropped at 68%. Pick up the transfer from where it stopped instead of starting over from 0%.
MacBook Pro
LAN direct
iPhone 15
phone online
Web
browser receive
project-build.apk
68% · resumed
Resuming from 68%
BYO S3 fallback
cross-network / large files
LAN first
direct when possible
Resume
after disconnects
Browser
receive without install
Any network
even restrictive ones
Why ShrimpSend
Reliable transfer, still built for maximum speed
Resume after disconnects
Large transfers survive unstable networks. Reconnect and continue from the interrupted position instead of restarting from 0%. Native client ↔ client today; client ↔ web not yet.
Works on restrictive networks
Transfers still work behind NAT, campus Wi-Fi, and carrier networks — even when devices cannot directly reach each other.
Breaks through one-way networks
Firewalls and NAT often allow traffic in only one direction — e.g. your phone can push to a Windows PC on the same LAN, but the PC cannot push back. After sign-in, the server coordinates reachability probes; if direct HTTP push fails, ShrimpSend automatically reverse-pulls from the reachable side, or falls back to WebRTC / S3 relay.
The difference
Three scenarios, side by side
Go as fast as your LAN allows on direct paths. When networks turn unstable or restrictive, stay reliable without losing progress or starting over.
Large file over unstable Wi-Fi
Typical tools
Connection drops → restart from 0%
ShrimpSend
Reconnect → resume from where it stopped
Send to a device you cannot install on
Typical tools
Both sides need the same app installed
ShrimpSend
Open a browser and receive — no install needed
Hotel, campus, or carrier NAT
Typical tools
Direct connection fails; LAN-only tools stop working
ShrimpSend
Automatic relay keeps the transfer path alive
How it works
Built for difficult networks
1. Pick sender and receiver
Choose your phone, desktop, or a browser endpoint for temporary receiving — even when the other side cannot install anything.
2. Let ShrimpSend pick the path
Prefer LAN on the same network, use relay across restrictive networks, and fall back to S3 when you need a stable wide-area path for large files.
3. Deliver reliably — even big files
Transfers finish on difficult networks. If something drops, native clients resume from the interrupted position instead of forcing you to start over.
browser
no install
project-build.apk
68%
MacBook
Sending
browser
no install
project-build.apk
68%
release.zip
queued
iPhone
Sending
browser
no install
project-build.apk
68%
Web
Waiting
Same network — direct first
WebRTC / LAN
Resuming from 68%
Cross-network — relay when needed
S3 fallback
Pricing
Start free. Upgrade when you need more.
Pricing follows the current mainland or overseas cluster automatically and is visible without signing in. When you choose to buy, signed-out users go to sign-in first and return to the purchase page automatically.
Overseas pricing · USD subscription
Free
Free
1GB hosted upload per UTC calendar month
- ✓Up to 3 devices
- ✓1GB hosted upload capacity
- ✓LAN direct transfer + S3 fallback
Plus
$5.99/mo
$59.69/yr, about 10 months of monthly pricing
- ✓Up to 10 devices
- ✓80GB hosted upload capacity
- ✓LAN direct transfer + S3 fallback
Pro
$11.99/mo
$119.39/yr, about 10 months of monthly pricing
- ✓Up to 20 devices
- ✓250GB hosted upload capacity
- ✓LAN direct transfer + S3 fallback
Ultra
$24.99/mo
$248.90/yr, about 10 months of monthly pricing
- ✓Up to 50 devices
- ✓800GB hosted upload capacity
- ✓LAN direct transfer + S3 fallback
FAQ
Frequently asked questions
Does the recipient need to install an app?
Not always. Recipients can receive in a browser without installing ShrimpSend — ideal for guest devices, restricted work machines, or one-off shares. Native apps unlock LAN discovery, resume, and server-assisted paths across restrictive networks.
Does it work on hotel Wi-Fi, campus networks, or carrier NAT?
Yes — that is a core use case. When direct device-to-device paths are blocked, ShrimpSend can use server-assisted relay to keep transfers working. Native apps can still discover each other on the same LAN without signing in; signing in unlocks cross-network relay and web participation in your device session.
What happens if my network drops during a large transfer?
On native clients, large transfers can resume from the interrupted position after reconnecting — no need to restart from 0%. Client ↔ web resume is not supported yet; use native endpoints on both sides for largest files on unstable networks.
When should I configure S3?
Use S3-compatible storage when you often send large files across cities or networks, or want file staging in your own object storage.