More streams only when they help
It starts with 8 connections, measures, and goes to 16 or 32 only if the speed really follows. When a server says no, it steps back and asks again a second later instead of hammering.
Download manager for Windows · free
Weft splits one file into many streams and sends them over every network your PC has: Ethernet, Wi-Fi, a phone hotspot. If the power or the connection drops, it carries on from where it stopped, and it always tells you what is holding the speed back.
powershell -c "irm https://weft.nhaajt.com/install.ps1 | iex"
Paste the command into PowerShell or Terminal. It downloads the installer, checks its SHA-256 and installs for your account only.
01 · How it works
It starts with 8 connections, measures, and goes to 16 or 32 only if the speed really follows. When a server says no, it steps back and asks again a second later instead of hammering.
Each connection is pinned to its own adapter, so Ethernet and Wi-Fi really carry the same file together. The faster one takes the larger share; if one drops, the others take over its part.
Twice a second Weft records which bytes are safely on disk. In testing the process was killed 11 times and the server taken away once during a 1 GB file: the result was still byte-exact.
The network path, a server that caps each connection, a server refusing connections, the disk, or your own limit: the app names the one cause instead of leaving you to guess.
02 · Numbers
Same PC, same local test server, against Plexo (an open-source multi-network downloader). Times are medians of 7 runs; lower is better.
| Scenario | Weft | Plexo | Difference |
|---|---|---|---|
| No limit, 1 GiB filethe software and the disk are the limit | 1.70 s | 6.36 s | 3.7× faster |
| Server caps each connection at 1 MiB/s200 MiB | 7.32 s | 7.48 s | 2% faster |
| Server accepts only 4 connections200 MiB, 2 MiB/s each | 25.54 s | 26.11 s | 2% faster |
| Server without resume support200 MiB, one connection | 5.18 s | 5.29 s | 2% faster |
| Server answers 150 ms late200 MiB, 4 MiB/s each | 3.72 s | 3.62 s | equal (both average 3.63 s) |
| One 20 MiB/s bottleneck200 MiB | 10.30 s | 10.16 s | 1.4% slower |
| Peak memory while downloadingthe app's whole process tree | 358–395 MiB | 596–700 MiB | about half |
| CPU time per downloaddepending on scenario | 2.0–3.5 s | 12.8–60.1 s | 6–26× less |
| Re-downloaded after a hard kill at 50%200 MiB file | 6–16 MiB | 112 MiB | 7–18× less |
| Installer | 2.3 MiB | 258 MiB | 110× smaller |
The test server runs on the same machine, so this compares software with software, not your internet speed. Two networks only add up when they reach the internet through two different lines.
03 · Browser
The companion extension hands downloads from Chrome, Edge or Firefox to Weft. It talks to exactly one address: 127.0.0.1 on your own PC.
04 · FAQ
Yes. No account, no ads, no paid tier. The source is under the MIT licence.
Only when they are two different internet lines, such as home fibre plus a phone's 4G. Ethernet and Wi-Fi on the same router are still one line; Weft notices that and tells you.
It can. The installer is not code-signed yet, so SmartScreen may ask you to confirm. The install command above checks the installer's SHA-256 before running it.
No. Weft downloads files over HTTP and HTTPS and tries to do that one thing well.
Not as an app yet. The engine is written for all three systems, but only the Windows build has been tested in full so far.
Settings, Apps, Weft, Uninstall. The program files and the Start Menu entry go; the files you downloaded stay.
Installer SHA-256: —