System Requirements & Platform Availability

Adopting 64-Bit Windows

MathWorks provides the following information to help MATLAB users and administrators make the transition to 64-bit Windows.

Note: References to MATLAB also apply to all products in the MATLAB and Simulink product families.

MATLAB Administrators

MATLAB Users


MATLAB Administrators

How long will 32-bit versions of MATLAB continue to be produced?

R2015b is the last release of the 32-bit version of MATLAB for Windows. MathWorks releases subsequent to R2015b will not be available for the 32-bit Windows operating system. To use releases after R2015b, impacted users are advised to migrate to 64-bit Windows at this time. They can continue to use releases up through R2015b.

What hardware and software do I need to run the 64-bit version of MATLAB?

To run 64-bit applications, you need a 64-bit-capable computer and a 64-bit operating system.

Most PCs produced in the last decade are equipped with a CPU capable of executing 64-bit operating systems and applications. For more information on how to tell if a computer is 64-bit capable, see 32-Bit and 64-Bit Windows: Frequently Asked Questions from Microsoft.

In addition to a 64-bit-capable processor, you need a 64-bit version of Windows. Windows 7, Windows 8, and Windows 10 have 64-bit versions.

What versions of 64-bit Windows does MathWorks support?

MathWorks supports the 64-bit versions of Windows 7, Windows 8, and Windows 10 with current service packs. Refer to the system requirements page for more detailed information.

MATLAB Users

What are the benefits of running the 64-bit version of MATLAB?

Access to larger amounts of memory is the most immediate benefit to a MATLAB user. A 32-bit application has theoretical access to 2^32 bytes (4 gigabytes) of addressable memory. However, Windows claims at least a quarter of this, leaving MATLAB with, at best, 3 gigabytes of addressable memory. A 64-bit application has access to all of the memory installed on the computer, and much more if you consider virtual memory. MATLAB users who work with large data sets or who receive out-of-memory errors are likely to have an improved experience when using the 64-bit version of MATLAB.

Will switching to the 64-bit version of MATLAB impact the numeric results of my MATLAB applications?

Possibly. All MATLAB numeric types in the 32-bit and 64-bit versions of MATLAB are the same size, providing broad consistency between the two. At the lowest level of operation, however, a 32-bit and 64-bit application may use CPU registers of differing widths, which can result in slightly different answers due to round-off effects. This effect can be more pronounced when working with data of type single. The differences are unimportant in many applications, but re-examine any application with a high sensitivity to numerical results when transitioning to the 64-bit version of MATLAB.

How can I determine if I am running a 32-bit or 64-bit version of MATLAB?

In the MATLAB Desktop, select Help > About. The About MATLAB dialog box indicates which version you are running.

For programmatic options, refer to How can I determine if I am running a 32-bit version of MATLAB or a 64-bit version of MATLAB?

How do I get my MEX files to run in the 64-bit version of MATLAB?

MEX source files and anything they call must be recompiled for 64-bit Windows. Since 32-bit and 64-bit MEX-files use different file name extensions (.mexw32 and .mexw64 respectively), it is possible to have both 32-bit and 64-bit MEX binaries in the same folder.

Changes in the MEX API to support large data sets may require some accommodation. See How do I update MEX-files to use the large array handling API for further discussion.

Updating Fortran MEX files for 64-bit versions of MATLAB may require additional work, described in the following resources:

Are MAT-files compatible between the 32-bit and 64-bit versions of MATLAB?

MAT-files created with 32-bit versions and 64-bit versions of MATLAB are compatible with each other.

Note: With large data sets that use the -7.3 MAT-file format, it is possible for the 64-bit version of MATLAB to produce a MAT-file that is too large for the 32-bit version of MATLAB.

I use other software applications that interoperate with MATLAB.  Do all of these applications need to be 64-bit as well?

While 64-bit Windows can run both 32-bit and 64-bit applications and software components, interoperability between two applications may require that both programs be either 32-bit or 64-bit.

In-process communication between 64-bit versions of MATLAB and other applications and software components requires that the other software also be 64-bit. Some examples include, but are not limited to:

  • Calling a MEX binary
  • Using a COM object or Active-X control
  • Loading a library through LoadLibrary
  • Connecting Database Toolbox to a database via an ODBC interface
  • Connecting to hardware using a vendor-supplied driver

Using external software with a 64-bit version of MATLAB in the following situations does not require a 64-bit version of the external software:

  • Exchanging data through files
  • Invoking another application using the ! or system command
  • Communicating via an out-of-process mechanism such as the MATLAB Engine, Automation (with MATLAB as either a client or server), SOAP, or sockets (TCP/IP)
  • Using .NET assemblies, unless they are built for a specific platform

Are there any other functional differences between the 32-bit and 64-bit versions of MATLAB?

There are a small number of functional differences between the 32-bit and 64-bit versions of MATLAB. The following table summarizes the differences:

Product 32-bit version 64-bit version

MATLAB Compiler

Supports 32-bit Excel

Supports 64-bit Excel, and as of R2015b, also supports 32-bit Excel

Data Acquisition Toolbox

Supports a broad range of CompactDAQ, M-Series, and other legacy devices from National Instruments and others

Supports a broad range of M-series, X-series, CompactDAQ, and other devices from National Instruments. Support for certain audio devices, Digilent devices, and Analog Devices devices is also available

 

Supports  daq.createSession and the legacy ANALOGINPUT and ANALOGOUTPUT device interfaces

Supports daq.createSession interface

 

Supports Simulink connectivity to DAQ devices from National Instruments and other vendors

 

Instrument Control Toolbox

Supports a broad range of 32-bit VXIplug&play, IVI-C, IVI-COM, and MATLAB high-level drivers

Supports a broad range of 64-bit VXIplug&play, IVI-C, and MATLAB instrument drivers

 

Supports GPIB adaptors from a number of vendors including Keysight (Agilent) and National Instruments. Also supports 32-bit VISA implementations from Keysight (Agilent) National Instruments and Tektronix

Supports Keysight (Agilent) and National Instruments GPIB adaptors and 64-bit implementations of VISA libraries from Keysight (Agilent) and National Instruments

Vehicle Network Toolbox

Supports CAN hardware from a number of vendors including Vector, Kvaser, PEAK-Systems, and National Instruments NI-CAN devices

Supports CAN hardware from a number of vendors including Vector, Kvaser, PEAK-Systems, and National Instruments NI-XNET devices

Simulink Coder

External mode requires all 32-bit systems

External mode requires all 64-bit systems