What Is WarpSend? Direct Transfer, Share Links, and Sync
WarpSend is encrypted file-transfer software for direct endpoint delivery, browser share links and cross-site folder sync. See where each mode fits.
A team may need to collect footage from a freelancer, send it to an editor’s NAS, and deliver the finished cut to a client. Those handoffs have different requirements: the freelancer needs an upload link, the editor needs working files on a device, and the client needs a download that remains available later.
WarpSend is file-transfer software for these connected workflows. It runs on supported Windows, macOS, Linux, and Synology devices and provides direct transfer, browser sharing, file requests, and folder sync. You choose the destination and delivery method for each job from the same interface.
WarpSend’s three transfer modes
| Mode | What it does | Recipient setup | Best fit |
|---|---|---|---|
| WarpDirect | Sends files or folders between paired endpoints | WarpSend endpoint on both sides | Repeated team-to-team or NAS-to-NAS delivery |
| WarpShare | Uploads once and creates a browser download link | Browser only | Client delivery and external recipients |
| WarpSync | Keeps configured folders synchronized | WarpSend endpoint on both sides | Ongoing cross-site folder movement |
For incoming files, File Requests adds a browser upload link tied to a selected endpoint folder. The uploader needs no account or app; encrypted chunks can wait in managed staging while the destination is offline.
Choose WarpDirect when both devices can participate in a handoff. Choose WarpShare when the recipient should download later in a browser. Once a folder needs repeated updates, configure a WarpSync job with an explicit direction and conflict policy.
For deeper product details, see WarpSend features, direct endpoint transfer, browser share links, and folder sync.
The WarpShare guide walks through choosing a file source, setting link access and checking the recipient’s download.
How routing works
WarpSend attempts a direct endpoint-to-endpoint route for WarpDirect and WarpSync when connectivity permits. That path uses libp2p and QUIC. QUIC is a secure, multiplexed transport built over UDP; the IETF QUIC specification defines its streams, flow control, connections, and integrated security.
When a direct route is not practical, WarpSend can use a managed WarpFabric Shuttle route; Shuttle fallback on transfers requires a paid speed tier. Route choice affects where payloads travel and whether cloud staging is used. Automatic routing can switch to Shuttle after a direct-connectivity failure; an explicitly selected Tunnel fails instead of silently changing routes. Record the route when testing.
The guide to TCP vs UDP file transfer explains why “uses UDP” is not a complete performance claim. QUIC adds reliability, recovery, congestion control, and security above UDP; raw UDP alone does not provide dependable file delivery.
What “encrypted and verified” means
WarpSend uses route-specific protection. Direct endpoint transfers, File Requests, and password-protected WarpShare links apply application-layer encryption to file content; passwordless Share links use TLS with service-managed storage and access controls. Completed endpoint deliveries are verified with BLAKE3, and transfers are chunked and resumable so an interruption does not automatically require restarting the entire payload.
These properties solve different problems:
- Encryption protects file content on routes that use application-layer encryption; TLS and access controls protect service-managed passwordless links.
- Authentication and link controls determine who can initiate or access a workflow.
- Resume limits repeated work after an interruption.
- Whole-file verification confirms that the destination content matches the completed source file.
Security requirements can extend beyond transport. Regulated teams may also need SSO, retention policy, audit exports, data-location review, signed agreements, or a specific server protocol. Evaluate those requirements separately instead of treating encryption as the whole checklist. For a recipient-focused workflow, use the guide to sending large files securely.
Compare the transfer your team needs
Compare the current releases using the same files, route, storage, and security settings. Record transfer-phase throughput separately from the time until the recipient has a verified copy. The WarpSend vs FTP benchmark method explains how to run that comparison; an FTP result does not establish performance against SFTP or Aspera.
Who WarpSend is for
WarpSend is designed for teams whose file-transfer workflow is larger than an email attachment or occasional small browser upload:
- Video and post-production teams moving camera originals, project files, proxies, and review exports.
- Synology NAS users transferring or synchronizing file-level data between locations.
- Distributed teams delivering build artifacts, datasets, archives, and other large folder trees.
- External-delivery workflows where the recipient should receive a browser link instead of an account or server credential.
Where WarpSend does not fit
Choose another system when the requirement is:
- an FTP, FTPS, SFTP, SMB, NFS, or S3-compatible server interface;
- block-level SAN replication, array consistency groups, or automatic storage failover;
- collaborative document editing and long-term team drive storage;
- a guaranteed recovery-point objective that depends on application-consistent snapshots;
- a platform outside WarpSend’s supported Windows, macOS, Linux, and Synology endpoints.
If you need recovery points or application collaboration, keep the system that provides them and use file transfer for the handoff it can support.
Pricing and a practical evaluation
UDP endpoint transfers and WarpShare sharing and collection have independent billing models. Endpoint plans set speed and capacity; WarpShare bills upload volume, with no added charge for recipients or repeat downloads. Extended retention can add charges. Browser downloads have no plan speed cap and require no UDP subscription. See current pricing for the applicable allowances and terms.
Choose one handoff to try first. For a client delivery, create a share link and check the download experience. For a recurring NAS job, test a representative folder in both directions, including an interruption and destination verification. Record the total completion time and any steps the recipient needs to perform.
Start at app.warpsend.io with the same files you use in the existing workflow.
Frequently asked questions
What is WarpSend?
WarpSend is file-transfer software for moving large files and folders between supported endpoints, delivering files through browser share links, and synchronizing folders across locations. It supports Windows, macOS, Linux, and Synology NAS.
Does WarpSend require port forwarding?
No inbound port-forwarding workflow is required for users. WarpSend attempts a direct endpoint route when practical and can use a managed shuttle route when direct connectivity is not the practical path. Shuttle fallback on transfers requires a paid speed tier.
Is WarpSend a replacement for FTP or SFTP?
WarpSend is an alternative file-transfer workflow, not an FTP or SFTP server and not a drop-in protocol replacement. Keep FTP or SFTP when an existing server interface is mandatory; evaluate WarpSend when supported endpoints, share links, resume, verification, or folder sync better match the job.
Can a WarpSend share link work after the sender goes offline?
Yes. WarpShare stages file content so recipients can download after the sender goes offline. Password-protected links encrypt before upload; passwordless links use TLS and service-managed storage and access controls.
How much does WarpSend cost?
UDP endpoint speed plans and WarpShare upload billing are independent. WarpShare adds no fee for multiple recipients or repeat downloads, while extended retention can add charges. The pricing page lists current allowances and rates. Browser downloads have no plan speed cap and require no UDP subscription.