NEWSLAZER

NZB import is present and functional. An NZB is the index card for a Usenet post, listing every article fragment so a client can fetch and rebuild it, and it is the format the independent ecosystem runs on. Here it is the back door: the interface is built around the internal search, queue management is basic, and there is no meaningful watched folder or URL submission, so no other program can feed it. That is the difference between a client and a component, and this is a client.

Repair and extraction run automatically with nothing to configure, which is the right default. PAR2 files are the parity data that lets a client rebuild a post when articles have expired, and damaged sets healed without ceremony in ordinary use. As with every client in this style, the mechanics are hidden, so an unrecoverable set produces a failure rather than a diagnosis. With this product the shortage of documentation and community makes that opacity cost more than it does elsewhere: there is very little to read when you are stuck.

Preset for Eweka’s Dutch servers and perfectly quick from inside Europe, where an ordinary line fills without adjustment. From further away you inherit the distance to Amsterdam and there is little to tune. The structural limit is the same one every locked client has: it cannot hold a second provider, so it cannot pool connections across backbones to fill in missing articles. A standalone client with two cheap accounts beats this arrangement on completion, permanently.

Windows and macOS desktop builds are documented. Beyond that the public material runs out, and we could not confirm the rest of the matrix, so treat it as not verified rather than not offered. What is clearly absent is anything server-shaped: no NAS package, no Docker image, no headless daemon. This is the weakest platform story of any working client in the table, and the thinnest documentation behind it.

None. No API, no RSS, no scripting hooks, no Sonarr or Radarr support. Newslazer automates its own pipeline from search box to unpacked folder and treats the job as finished there. For the subscriber it ships to that scope is defensible. For anyone who wants downloads to happen without a human present, it is a wall, and both free alternatives above it in this table have a door.

Light enough on any modern desktop, and irrelevant on any machine that is not one. There is no headless mode, so a desktop session has to stay logged in for downloads to run. NZBGet does the same work in roughly 42 MB on a screenless Pi. The comparison is not about memory, it is about whether the software can live where a download client should live, and this cannot.

The built-in search is the reason the product exists and it does the job: query, results, one click, downloading on the account you already have. Depth is adequate for mainstream material and shallower than a dedicated indexer at the edges, which is the standard trade of the category. Unlike its Newshosting counterpart there is no verified preview capability, and as with every integrated index there is no way to add a second source when the first comes up empty.

Modern, uncluttered and free of the legacy clutter older clients carry. A first-time user gets from install to a finished download quickly, and this is the product’s best axis. The options surface is small, which reads as simplicity in week one and as a ceiling by month three, and there is no configuration file or scripting layer underneath to raise it.

Included with an Eweka subscription and inert without one, which makes the honest reading of this axis a lock-in charge rather than a price. SABnzbd and NZBGet cost nothing, work with every provider on this site and every provider that is not, and survive a change of mind. Newslazer costs one specific vendor relationship for as long as you want the software, and that vendor is no longer in our provider league table. Free with strings attached scores below free without them. Checked August 2026.