Did you know ... Search Documentation:
Download SWI-Prolog development versions

linux.png We collect information about available packages and issues for building on specific distros here. We provide a PPA for Ubuntu

WIP.png Examine the ChangeLog.

Windows version (64-bits)12,103,894 bytesSWI-Prolog 8.1.0-1 for Microsoft Windows (64 bit)

Self-installing executable for Microsoft's 7/8/10 64-bit editions. See the reference manual for deciding on whether to use the 32- or 64-bits version.

Windows version (32-bits)11,807,436 bytesSWI-Prolog 8.1.0-1 for Microsoft Windows (32 bit)

Self-installing executable for MS-Windows. Installs swipl-win.exe and swipl.exe. Works on Windows 7/8/10.

Snow Leopard and later23,573,610 bytesSWI-Prolog 8.1.0-1 for MacOSX 10.6 (Snow Leopard) and later on intel

Mac OS X disk image with relocatable application bundle. Needs xquartz (X11) installed for running the development tools. The bundle also provides the commandline tools in the Contents/MacOS directory.

Source archive10,353,486 bytesSWI-Prolog source for 8.1.0

Sources in .tar.gz format, including packages and generated documentation files. See build instructions.

PDF file2,468,876 bytesSWI-Prolog 8.1.0 reference manual in PDF

SWI-Prolog reference manual as PDF file. This does not include the package documentation.

Show all files
Install scripts may download the SHA256 checksum by appending .sha256 to the file name. Scripts can download the latest version by replacing the version of the file with latest. This causes the server to reply with the location of the latest version using an HTTP 303 See Other message.

About the development releases

The development branches have their own GIT repository at the address below. See the general GIT instructions for details.

% git clone https://github.com/SWI-Prolog/swipl-devel.git

Should I use the development release or the stable one?

Many active SWI-Prolog users track the development releases or GIT versions for developing Prolog applications. Most of the time the development versions are fairly stable. Infrequent larger rewrites to the core infrastructure that may cause instability is typically announced on the mailinglist.

Tracking the latest version offers some advantages for you are user:

  • Bug fixes are quickly available.
  • When you are stuck on a missing feature you can use this quickly after it has been added.
  • Although you are a little more often confronted with incompatibilities and regressions, such issues can be discussed and resolved.