Frequently Asked Questions

uvCopy is a high-performance file transfer tool designed for environments with high network latency, where traditional copy methods often underutilize available bandwidth. It helps move large files quickly and reliably across long-distance connections.

uvCopy includes multi-threaded transfers, automatic retry logic, packet-level integrity checks, and network optimization designed to keep large transfers moving efficiently even under high-latency conditions. It is tuned to use available bandwidth without requiring manual tuning such as jumbo frames.

When transferring large datasets across geographically separated systems, standard file copy tools often become limited by latency and can fail to fully use the available network capacity. uvCopy is built to reduce that bottleneck, improve transfer speed, and maintain reliability for large-scale data movement.

Unlike traditional transfer methods such as FTP or SCP or RoboCopy, uvCopy is designed specifically for high-latency environments. It avoids many of the bottlenecks associated with conventional TCP-based transfers and is better suited for large file movement across long-distance links. It is also distinct from SMB or NFS-based workflows, which can perform poorly over extended WAN connections.

Performance depends on your network conditions and machine resources, but uvCopy is designed to drive transfers close to full available bandwidth when the environment supports it. In some high-latency deployments, this can reach very high sustained throughput. If needed, transfer throttling can be used to avoid impacting other systems using the same network path.

uvCopy is best suited for large backups, database snapshots, archives, media files, and other large datasets that must be transferred quickly and reliably over long-distance networks.

No. uvCopy is distributed as a portable executable and does not require a system installation. It can be run directly from a local folder, a removable drive, or a shared network location.

uvCopy is primarily designed for command-line usage. It offers a simple interface for specifying source and destination paths, transfer options, and other runtime parameters, but it is not built around a desktop GUI.

Yes. Because it is a portable executable, uvCopy can be integrated into shell scripts, orchestration workflows, and custom automation pipelines for repeatable transfers and scheduled operations.

uvCopy is cross-platform and supports Windows 10/11, Windows Server 2012 and later, Linux, and macOS. Transfers can be performed between mixed operating systems and environments.

uvCopy requires a 64-bit operating system, a modern CPU, and at least 8 GB of RAM for typical large-file use cases. It is intended for current-generation Windows, Linux, and macOS environments, with compatibility depending on the host architecture and network conditions.

uvCopy requires access to a UDP port selected by the customer for data transfer, and TCP port 445 may also be needed depending on the environment and deployment model. Firewalls and security policies should allow the required traffic for successful transfers.

uvCopy uses a subscription-based licensing model. Users must purchase a valid license to activate the software, with a minimum subscription period of 30 days. Each license is tied to a specific machine or activation key and is managed within the applicable billing scope. Unused or unclaimed licenses from the same invoice may be used to extend the current machine license duration, as long as they remain within the same invoice.

The software binaries can be copied to another machine, but the license must be reactivated for that system. A valid activation is required before the application can function on a new host.

No. uvCopy licenses are not transferable between machines. Each license is bound to a specific machine or activation key and cannot be shared or reassigned without authorization. Unused or unclaimed license units from the same invoice may extend the current machine activation, but they cannot be reassigned to a different machine or invoice.

The application, activation key, and license file should be kept in the same folder. If any required component is missing or stored in a different location, the software may not run correctly.

The minimum subscription term is 30 days for a 4-license package. If a license is not activated or used, it may expire after 360 days. Unused or unclaimed allocations from the same invoice may be applied to extend the current machine license duration. Continued use requires a valid renewal or new purchase.

uvCopy is optimized for high-latency and long-distance file transfers. It is not intended as a general-purpose tool for low-latency LAN transfers, where traditional solutions may be simpler and equally adequate.

By default, uvCopy can consume a large share of available CPU, memory, and network capacity to maximize throughput. This is intentional, though users may choose to limit usage if other services share the same machine or network path. In testing over a 1 Gbps link with 1Gbps source NIC and a 10 Gbps destination NIC, a 40 GB transfer across a 20,000+ km route sustained roughly 98 MB/s, with peaks near 120 MB/s, while using only a fraction of the host’s total compute resources. For comparison, a standard RoboCopy transfer in the same scenario was measured at 1.7 MB/s.

Tampering with the software, activation key, or license data may result in access denial and enforcement of anti-piracy protections. Using an invalid, expired, or modified license can prevent the application from operating correctly.

uvCopy is built to minimize transfer overhead and keep large data transfers moving efficiently across high-latency links. It tracks packet and transfer progress to support retries, completion checks, and overall transfer visibility.

uvCopy performs packet-level integrity verification and automatically retries failed or corrupted packets to ensure that transferred data is complete and accurate.

uvCopy does not apply encryption or compression at the transfer layer. Users are responsible for ensuring data security, compliance, and storage-level safeguards appropriate for their environment.

The software validates transfer integrity at the packet level, but it does not perform a separate file-level integrity check after the transfer completes. Users should ensure that the source data is valid before transfer and verify destination files as needed.

Yes. Storage-level encryption or write filters may interfere with received files or change the final output on disk. If such controls are in place, they may need to be allowed or disabled for uvCopy to operate correctly.

The trial version is limited to files up to 1 GB and remains valid for 6 hours. Larger transfers and longer usage require a paid license. Email us to request a trial or additional information.

By using uvCopy, you agree to the applicable terms and conditions, including the End User License Agreement (EULA) and Privacy Policy published on the official website. Users must also comply with all relevant local laws and organizational policies when using the software.