3.50 Alpha (2026)
WinHTTrack has had no Windows build since 3.49-2, in May 2017. The engine kept moving on Linux and the BSDs the whole time; the Windows binary did not. These alpha builds close that gap: nine years of engine work, and an interface rebuilt with Visual Studio 2022 and OpenSSL 3.x.
The change you will notice first is HTTPS. The 2017 build links OpenSSL 1.0.1j, a library from 2014, and fails to negotiate with much of today's web. If HTTrack stopped working for you on modern sites, that is why, and it is fixed. The rest comes out of the same nine years: pages captured whole instead of losing half their images to lazy loading, accented and very long paths landing where you asked instead of in an unreadable directory next to it, files over 2 GB surviving, and an --update that no longer replaces a good local copy with an error page.
- HTTPS works again. OpenSSL 3.x replaces the 2014 library, so TLS 1.2 and 1.3 negotiate cleanly with the servers that had started refusing the old build. Secure downloads also go through a proxy properly.
- Pages come back whole. Every candidate in an srcset, data-src lazy loading, <source> and <track> media, and conditional CSS @import rules.
- Names and paths land where you asked. Accented and non-Latin project names, output paths, top index, log and cache no longer end up in an unreadable directory beside the real one, and Windows paths past the old 260-character limit work.
- Your mirror survives an update. --update keeps your good copy when the re-fetch returns an error page, a resume honors the server's byte range, a corrupt cache entry is skipped instead of aborting the mirror, and files over 2 GB no longer come out truncated.
|
Engine
- SOCKS5 proxies (-P socks5://host:port), and HTTPS through a CONNECT-only proxy
- brotli, zstd and deflate content decoding
- WARC/1.1 archive output (--warc), with a CDXJ index and WACZ packaging
- robots.txt Allow rules and path wildcards, per RFC 9309
- --why tells you which filter rule accepts or rejects a URL
- preload a cookies.txt (--cookies-file), pause randomly between files (--pause), drop query keys from names (--strip-query), name the fields of the page footer (-%F)
- --timeout and --max-time now cover a stalled TLS handshake and a name lookup that never comes back
- an honest User-Agent, and default ports read according to the scheme
- a rewritten command line guide, and a man page that matches the binary
- a long list of security fixes in the parsers that read hostile input
|
WinHTTrack (Windows interface)
- rebuilt with Visual Studio 2022 and OpenSSL 3.x, for Windows 7 SP1 and later
- the command line httrack.exe ships in the installer, next to the interface
- a "Write WARC archive" option, with the log, index and cache options regrouped on their own tab
- the engine options added since 3.49-2 are reachable from the interface
- fixed a crash when a mirror ended with the Options or View-transfers panel open
- fixed use-after-free crashes on the transfers dialog and after a language change
- the transfers window shows the whole URL instead of a 32-character stub, and the mirror panel follows the window size
- accented paths reach the engine as UTF-8, not the ANSI codepage
- fixed dial-up redialing, the directory tree, and a stale language index that blocked startup
|
These are alpha builds, not a release. They come out of the development branch automatically, on every change, so they have had none of the testing a release gets. They can crash, and they can ruin a mirror. Do not point one at work you cannot redo.
The installers are not signed. Windows SmartScreen will warn you and ask you to confirm before running them. Signed builds will return once the project's SignPath Foundation application is accepted; see the code signing policy.
They need Windows 7 SP1 or later. On Windows XP or Vista, keep the 3.49-2 release from the download page.
Installing an alpha replaces the release you have; reinstall 3.49-2 from the download page to go back. If you find a problem, please report it, that is what these builds are for: engine, Windows interface, Android.
|
Nothing is tagged 3.50 yet, so these builds still report the current engine version rather than a 3.50 one.
@
|
|
