x265 binaries for Windows (VS 2015/GCC 7.3)

x265 binaries for Win64/32 — default branch
VersionMinimum CPU arch
VS 2015VS 2017GCC 7.3GCC 8.0
2.6+49-7219376noneAVXAVX2nonenoneAVX2
2.6+42-52782aenoneAVXAVX2noneAVXAVX2nonenoneAVX2
2.6+40-36ab263noneAVXAVX2nonenoneAVX2
2.6+37-1949157noneAVXAVX2noneAVXAVX2noneAVX2
2.6+34-79c5e3bnoneAVXAVX2noneAVX2
2.6+33-193c2b2noneAVXAVX2noneAVXAVX2noneAVX2
x265 binaries for Win64/32 — stable branch
VersionMinimum CPU arch
VS 2015GCC 7.3
2.7+1-2aa737anoneAVXAVX2noneAVX2
2.6+8-68b17aanoneAVXAVX2noneAVX2
2.5+5-0b3ba15noneAVXAVX2noneSSSE3SSE4.1
2.4+13-26963e9noneAVXAVX2noneSSSE3SSE4.1
2.3+1-7e225aenoneAVXAVX2noneSSSE3SSE4.1
2.2+2-bbb13fcnoneAVXAVX2noneSSSE3SSE4.1

From version 2.6+17 there are no VS 2017 builds – update 15.5 of VS 2017 is so wrong (and it is not possible to install VS 2017 15.4) that I switched to VS 2015.2.

From version 2.5+54 there are no GCC SSE4.1 builds – 32-bit SSE4.1 binaries are in GCC SSSE3 package marked as _SSE4_32.exe.

Minimum CPU arch: none, SSSE3, AVX and AVX2 is for C++ compile option – x265 source code is divided into C++ and asm parts. Asm code determine CPU type at runtime, C++ code needs information about CPU type at compile time. It means that if you have CPU with AVX extension, you can use all binaries except AVX2 (which hangs at encoding on AVX-CPU). You can determine your CPU arch by executing x265 with option -V, for example:
x265 -V
x265 [info]: HEVC encoder version 2.2+2-bbb13fcb4c45
x265 [info]: build info [Windows][MSVC 1910][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX

All binaries do the same, so it is only about encoding speed. My recomendations are: for AVX2-CPU the fastest should be VS 2017 AVX2 version, for AVX-CPU – VS 2017 AVX version, for SSE4-CPU – VS 2017 none or GCC none version, for SSSE3-CPU – GCC SSSE3 version, for CPU without even SSSE3 – GCC none version. You can determine fastest version by comparing encoding time on the same short sample.

Binaries for Win32 are marked by '_32.exe' extension. In VS 2017 binaries there is only 8-bit x265-8b_32.exe – it is not mistake: 10-bit, 12-bit and multilib versions (for Win32) are only in GCC binaries.

Win32 binaries for CPU up to SSSE3 are compatible with Windows XP. Win64 binaries for CPU up to SSSE3 runs on Windows 7 or newer. AVX and AVX2 versions (for Win32 or Win64) runs on Windows 7 SP1 or newer.


x264 binaries for Windows (VS 2015/GCC 7.3)

x264 Stable tree
Commit
Date
CommitWin64Win32
VS 2015GCC 7.3GCC 7.3
2018-01-187d0ff22155.2901155.2901155.2901
2017-12-24b00bcaf155.2893155.2893155.2893
2017-06-26ba24899152.2851152.2851
2017-05-23df79067150.2833150.2833
2017-05-21d1fe6fd150.2829150.2829
2017-01-2390a61ec148.2762148.2762148.2762

These builds of x264 are compiled with lavf (from ffmpeg) and l-smash libraries. ffmpeg is configured to use postprocessing support.


Mingw-w64/GCC toolchain for Windows (threads-win32)

mingw-w64 [2070e8] 2018-02-08, binutils 2.30 20180210:
mingw-gcc73-20180210.7z (GCC 7.3, 50.8 MiB)
mingw-gcc64-20180210.7z (GCC 6.4, 49.7 MiB)
mingw-gcc55-20180210.7z (GCC 5.5, 47.2 MiB)
mingw-gcc494-20180114.7z (GCC 4.9.4, 39.3 MiB)
mingw-gcc485-20180114.7z (GCC 4.8.5, 37.8 MiB)

mingw-gcc801-20180217.7z (GCC 8.0.1 20180217 (experimental), 61.3 MiB)
mingw-gcc731-20180222.7z (GCC 7.3.1 20180222, 50.8 MiB)
mingw-gcc641-20180221.7z (GCC 6.4.1 20180221, 48.9 MiB)