Manual:Installation requirements/en

In addition to the MediaWiki software itself, you need:


 * A web server software to serve MediaWiki pages to the web browser.
 * PHP to run MediaWiki.
 * A database server to store MediaWiki pages and data.

In addition, there are various optional dependencies which are required if you want to use certain advanced features (see below).

If your website is hosted (i.e. you don't have direct control over it) then contact your server administrator or hosting company to ensure these software packages are installed and available.

To run MediaWiki maintenance scripts, you will need command line access.

One-download installation
If you are using Linux, it's best to install the Apache web server, PHP, and the MariaDB database server using your package manager. On Debian and Ubuntu, do the following:

Software bundles
On other operating systems, use a software bundle like XAMPP from https://www.apachefriends.org to install and configure all of the important packages – Apache web server, PHP, and MariaDB – with only one download. It is available for Linux, Windows, Mac and Solaris. As of, the latest version of XAMPP includes PHP 8.0 (MediaWiki requires at least ).

Alternatively, if you run Mac OS, you can use MAMP, which is the equivalent to XAMPP. MAMP includes the ability to run the Apache web server and a MySQL database. It is available for both Windows and Mac, but is generally used on Mac instead of Windows.

Web server
In order to serve wiki pages to browsers, MediaWiki requires some web server software. Often you will not have a choice of which software to use – it will be the one provided by your hosting provider.

MediaWiki is broadly compatible with all major web servers that can invoke a compatible version of PHP. Most installations use the Apache HTTPD web server. nginx (configuration example) is a good choice as well.

PHP
PHP is the programming language in which MediaWiki is written, and is required in order to run the software.


 * For the latest stable version of MediaWiki, at least PHP is required. See the page on for further information.

If you need to compile PHP from source, then see for compilation options that affect MediaWiki.
 * The following extensions are required:
 * Perl Compatible Regular Expressions (PCRE)
 * sessions
 * spl
 * openssl
 * json (MediaWiki 1.22+)
 * mbstring (required since 1.27, recommended for earlier versions)
 * fileinfo (required since 1.30)
 * intl (required since 1.36)
 * calendar (required since 1.33)
 * xml
 * Note that all of these are enabled in PHP by default.
 * On most Debian/Ubuntu-based distros the php-mysql package is required if you want MediaWiki to use MySQL.
 * Some features of MediaWiki may require PHP functions that execute external processes, like image thumbnailing, that some cheap hosts usually disable. Please take this into consideration if you plan to install MediaWiki on a shared host.
 * MediaWiki extensions may require additional PHP features, e.g. VisualEditor requires libcurl support (php-curl on Debian/Ubuntu-based distros).

Database server
MediaWiki stores all the text and data (content pages, user details, system messages, etc.) in a database, which it is capable of sharing with other web-based applications (phpBB, etc.). You will need one of the following database servers to run the latest version of MediaWiki:


 * + or +
 * +

Hardware requirements
The recommended minimum requirements are 256MB of RAM for a single-computer website and 85MB of storage, although this will not suffice for a busy public site or a site with uploading enabled. Some users have reported running MediaWiki on computers with as little as 48MB of RAM.

The install size can be reduced to around 50MB for a developer install and to around 26MB for a non-developer, end-user install. See.

Optional dependencies

 * ImageMagick or GD is required for.
 * TeX is required for inline display of mathematical formulae. In most Debian/Ubuntu-based distros, this is in the  package.
 * Shell access is required to run ; upgrading MediaWiki may be more difficult without it.
 * via the server itself requires a message transfer agent (MTA).
 *  can be provided to automatically resolve conflicts.
 *  can be used for object caching.