Offline · mDNS (native only)
Native apps only: no sign-in; LAN discovery via mDNS — traffic stays local. Web does not support local discovery.
Device-to-device conversations
Cross-device file transfer, straight to your devices.
ShrimpSend is not a link-generator workflow. It puts phones, desktops, and browsers into one device conversation so text, clipboard, media, and large files arrive where you choose.
Available for macOS, Windows, Android, iOS, and Web.
Device session
LiveSend today’s assets to MacBook
Messages, images, and large files queue in one device conversation without manually creating share links.
MacBook Pro
LAN direct
iPhone 15
phone online
Web
browser waiting
IMG_2038.mov
1.25 GB · 68%
Syncing to selected devices
BYO S3 fallback
cross-network / large files
LAN
direct path first
Encrypted
protected transfer
All platforms
desktop, mobile, web
Messages + files
device conversation sync
Everything you need
Built for speed. Designed for every device.
Resume (native only)
If a large transfer drops midway, native clients can continue from the interrupted position instead of starting over; client ↔ web does not resume yet.
Web ↔ web on LAN
On the same LAN: browser-to-browser and app-to-web transfer directly without hitting the public internet.
S3 fallback transfer
When LAN direct transfer is unavailable or cross-network delivery fails, S3 acts as the fallback path so files can still be delivered reliably.
How it works
Send across devices in 3 steps
1. Choose a target device
Pick a phone, desktop, or browser endpoint; messages and files enter that device channel.
2. Use the best available path
Prefer LAN / WebRTC on the same network, especially for large files; use S3 only as a fallback when direct transfer is unavailable or devices are across networks.
3. Arrive in the device session
Content appears in the target device conversation, ideal for clipboard snippets, temporary files, and repeated large-file sends.
clipboard
2 KB
IMG_2038.mov
68%
MacBook
Sending
clipboard
2 KB
IMG_2038.mov
68%
Project.zip
queued
iPhone
Sending
clipboard
2 KB
IMG_2038.mov
68%
Web
Waiting
Direct on the same LAN
WebRTC / LAN
Syncing to selected devices
S3 fallback across networks
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.
Mainland pricing · CNY lifetime
Free
Free
Free to use after sign-up
- ✓Up to 3 devices
- ✓No purchase or subscription required
- ✓LAN direct transfer + S3 fallback
Mini
¥30lifetime
One-time purchase for lightweight personal use
- ✓Up to 6 devices
- ✓Lifetime purchase, no subscription
- ✓LAN direct transfer + S3 fallback
Pro
¥60lifetime
One-time purchase for more long-term devices
- ✓Up to 12 devices
- ✓Lifetime purchase, no subscription
- ✓Device add-on packs available later
FAQ
Frequently asked questions
Does offline mDNS work in the web app?
No. Offline mDNS discovery is native-client only; the web app depends on browser capabilities and signed-in sessions.
Why does LAN transfer sometimes ask me to sign in?
Native apps can discover and transfer on the same LAN without signing in. Signing in does not mean your LAN traffic must go through our servers; it unlocks two enhanced paths: server-assisted discovery for one-way firewall/NAT situations, and direct LAN transfer between the web app and your native clients inside the same device session.
Can the web app transfer with native clients?
Yes. On the same LAN, browser-to-browser and native-to-browser transfer can go direct; across networks, use server assistance or S3.
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.