Download
Latest release
Most computers can extract a zip file without additional software.
Users of 7-Zip: Note that prior to 2021, 7-Zip was unable to extract .tar.gz files correctly (T257102). It is recommended to update to the latest version first.
Users of macOS: Note that The Unarchiver is unable to extract .tar.gz files correctly (T258716). Archive Utility can be used instead.
- MediaWiki 1.42.1 (download .zip, download .tar.gz) - stable
- MediaWiki 1.41.2 (download .zip, download .tar.gz) - legacy
- MediaWiki 1.39.8 (download .zip, download .tar.gz) - long-term support (LTS)
To users of MediaWiki versions 1.40 and 1.38 and earlier: These versions are no longer supported. Please update to a newer version of MediaWiki.
MediaWiki is free software licensed under version 2 (or later version) of the GNU General Public License. Because MediaWiki is licensed free of charge, there is no warranty, to the extent permitted by applicable law. Read the full text of the GNU GPL version 2 for details.
System Requirements
MediaWiki requires PHP 7.4.3+, a webserver software, and either MariaDB 10.3.0+, MySQL 5.7.0+, SQLite 3.8.0+ or PostgreSQL 10.0+. Using MariaDB or MySQL is recommended as Wikipedia uses MariaDB. Any other database servers are less tested and you may likely run into some bugs.
For more information, please read the pages on system requirements and compatibility.
Download via command line
To download MediaWiki 1.42.1 in a terminal on a Linux machine using wget, use one of the following commands:
wget https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.1.tar.gz
Alternatively, using cURL:
curl -O https://releases.wikimedia.org/mediawiki/1.42/mediawiki-1.42.1.tar.gz
Download from Git (for developers)
Active MediaWiki developers should instead download from Git to get the latest version of the MediaWiki software. The git repository has earlier versions of the software, so it is possible to switch to ("check out") a particular release. Developers downloading from Git will also need to manually install dependencies via Composer .
Developers wanting to install MediaWiki locally to have an environment for development of MediaWiki core or extensions should also read How to become a MediaWiki hacker for further instructions.
Signature downloads
- GPG security signatures to verify your download with GNU Privacy Guard:
- MediaWiki 1.42.1 - stable
- MediaWiki 1.39.8 - current long-term support (LTS)
- GPG keys
- MediaWiki 1.42.1 changes including i18n (unified diff)
Alternatives to manual installation
Some users may prefer to skip manual installation by using a pre-integrated MediaWiki software appliance or hosting services. Repositories of some Linux distributions also increasingly offer packages for MediaWiki, with different degrees of frequency and extensions coverage e.g. Debian (including derivatives like Ubuntu), Fedora, Gentoo.
What next?
Subscribe to our release announcements mailing list. Stay up to date with releases, and keep your server secure!
Legacy releases
If your MediaWiki installation is heavily modified, it may be difficult to incorporate the latest official changes/updates to MediaWiki. To support such users, we maintain old branches of our code for up to a year for the legacy release and up to three years for the legacy long term support release.
Development releases
If you want to run on the latest development (i.e. alpha) version, you can either download it as mediawiki-master.tar.gz, or download from Git.
From Git you can either download the complete repository (about 528 MiB)
git clone https://gerrit.wikimedia.org/r/mediawiki/core.git
or the latest revision only (about 85 MiB; this is often called a shallow clone: less time and smaller downloads).[1]
git clone --depth 1 https://gerrit.wikimedia.org/r/mediawiki/core.git
You can also view the latest source code in your browser.
Old releases
You can find tarballs (with extension *.tar.gz
) of old versions of MediaWiki in the MediaWiki download archives.
Footnotes
- ↑ This could cause reference problems when you later use "git pull" to upgrade your shallow clone and the newer revision refers to older revisions which are not yet downloaded to your system. In such a case you can simply download more - increase the depth value - or all revisions later, or make a fresh shallow clone.