Results for the 2026 MiniZinc Challenge have now been announced!

Downloads

Official binary packages are provided for Windows, macOS and Linux.
These contain MiniZinc 2.10.0, the MiniZinc IDE 2.10.0, as well as several state of the art solvers.
For detailed installation instructions, see the documentation.

Both the compiler tool chain and the IDE are available as free and open source software.
Have a look at our License Information page for the details.

The MiniZinc compiler and IDE

The compiler is the heart of the MiniZinc tool chain. It translates constraint models into FlatZinc, a language that is understood by a wide range of solvers.

MiniZinc comes with a simple Integrated Development Environment, the MiniZinc IDE, which makes it easy to develop and run constraint models.

Solvers

A number of solvers are included in the official binary packages:

MiniZinc can also interface with the following solvers if installed:

Additionally, many other compatible solvers can be installed, including:

Note that if you build MiniZinc from source, you will have to install any desired solvers yourself.

The MiniZinc IDE

Reporting issues

We are grateful for feedback on MiniZinc, including bug reports, feature requests and ideas for improvements.

For general discussions about MiniZinc, please use the discussion forum.

To report an issue, please use the following issue trackers:

Releases

The latest release of MiniZinc is version 2.10.0, released 23 July 2026.

  • Add support for named arguments. Function calls can now refer to arguments by name, in addition to the usual positional arguments. The parameter names of the global constraints in the standard library have been revised so that they read well as named arguments (now that named arguments make them part of the public interface). It is now a type error to declare two overloads of a function or predicate that a call supplying all of its arguments by name could not tell apart, i.e. two overloads that give the same name and type to every parameter that has to be supplied. Named arguments are available for user-defined and library operations. The low-level operations a solver supports natively (those declared without a body) remain positional-only for now, until solver libraries have converged on a common set of parameter names; calling one by name is an error. The new --warn-non-authoritative-names option helps solver implementers audit their libraries against the standard-library names ahead of that change.
  • Add support for default values for function and parameter arguments.
  • Add support for set cardinality declarations using the syntax set(e) of T: s;. When e has type int or var int, this desugars to an additional card(s) = e constraint; when e has type set of int or var set of int, it desugars to card(s) in e. The syntax works for tuple- and record-typed sets as well as arrays (and arrays of arrays) of sets.
  • Add support for index-dependent array declarations, where an index list entry of the form c in S binds the name c in the element type's domain expression — for example array[c in 1..n] of var 1..f(c): x;. The per-element domain is desugared into an additional constraint and works for tuple- and record-typed elements as well as arrays of arrays; it also composes with the set(e) of T cardinality syntax.
  • Make the list type behave like a real 1-based array type. It is now syntactic sugar for array [1..infinity] of T. Checks ensure that only 1-based arrays match the list type.
  • Allow par tuples and records to be optional. opt makes the tuple or record optional as a whole (it is either a complete value or <>); it does not distribute into the fields, so opt record(int: a) remains a different type from record(opt int: a). Accessing a field of an optional tuple or record yields an optional value. var opt tuples and records remain type errors, including when the var comes from a field, since a tuple or record with any var field is itself var.
  • And many more changes and bugfixes!

See the full changelog.

Development builds

Unstable development builds with upcoming bugfixes and features are available on GitHub.

Documentation for the latest development version of MiniZinc is available here.
For a list of bugfixes/changes please refer to the changelog.

Previous releases

View older releases.