EO.Products are distributed in a set of 100% managed DLLs. These managed DLLs can always run in both 32 bit mode and 64 bit mode. However at runtime these DLLs may start child process to run native code (for example, EO.Pdf uses a built-in Chromium browser engine to render HTML). These child processes can be either 32 bit or 64 bit. The x86 build would start child processes in 32 bit mode, while x64 build would start child processes in 64 bit mode. Below are several considerations to keep in mind when choosing between x84 and x84 builds:

• Bitness does not matter for your .NET application. Regardless which version you use, your .NET application (that uses EO product) can always run in either 32 bit mode or 64 bit mode. In another word, even if you use x86 build of EO product, your application can still run in 64 bit mode;
• Use x86 build for compatibility with old systems. x86 build can run on both 32 bit Windows and 64 bit Windows. So if you need to support old 32 bit system, then you should use x86 build;
• Use x64 build for superior performance. x64 build offers significant advantage on performance and scale (for example, it can handle much larger/more complex web pages due to vastly increased memory limit). So if supporting old 32 bit system is not required, you can use x64 build. x64 build can only run on 64 bit Windows, it can not run on 32 bit Windows;

If you do use x86 build, please consider transiting to x64 build over the long run. Microsoft has stopped offering 32 bit Windows to manufacturer since May, 2020. As such all new systems onwards will be 64 bit. Additionally, Windows 11 will only be available in 64 bit version.