WordPress Multisite lets you run a network of sites inside a single WordPress install. All sites share the core, plugins and themes, while each has its own content, users and settings. It suits organizations that run many similar sites: updates happen in one place and a new site is ready in minutes. Multisite does ask more of your hosting than a normal WordPress site, and knowing the requirements early saves painful migrations later.
When Multisite is the right choice
Multisite pays off when sites are alike and managed by one team, such as branches, schools, faculties or language versions of one brand. If sites need very different plugins, belong to different owners or one gets far more traffic than the rest, separate installs may be better. Remember that all network sites share one database and one file system, so a flaw in a single plugin affects the whole network.
Example: a network of private schools
Say a private school network in Tashkent wants sites for its twelve branches. Each branch needs its own news, timetable and teacher pages, while design, logo and main sections stay the same. With Multisite the head office manages one theme and plugin set, and each branch admin edits only their own site, on subdomains like chilonzor.example.uz or subfolders like example.uz/chilonzor/.
Subdomains or subfolders: the hosting impact
This is the key decision, made once. In subfolder mode every site lives under the main domain with no extra DNS or certificates, the easiest path on standard hosting. Subdomain mode needs a wildcard record such as *.example.uz at the DNS and web server level, or you add every subdomain by hand. When converting an existing site with content, WordPress may not offer subfolder mode because of possible clashes with old links.
example.uz. A 203.0.113.10
*.example.uz. A 203.0.113.10
Two DNS records like these are enough; the asterisk sends every subdomain to the same server. If your domain is with sayt.uz, add them in the cabinet's DNS section, and make sure the hosting accepts all subdomains of the domain, which you can confirm with support.
SSL certificates
In subfolder mode the main domain certificate covers the whole network. Subdomain mode needs a certificate per subdomain or a wildcard certificate, and Let's Encrypt issues wildcards only through DNS-01 validation, which requires a setup that can update DNS records automatically. With a small, fixed number of sites, separate free certificates work fine. You can also map a branch to its own domain such as misol.uz from the network site editor, but that domain then needs a certificate as well.
Enabling the network
Add the line that allows Multisite to wp-config.php, then open the network setup page that appears under Tools.
/* above the 'That's all, stop editing!' line */
define( 'WP_ALLOW_MULTISITE', true );
The setup page gives exact lines for wp-config.php and .htaccess; copy them unchanged. For subdomain mode they look roughly like this, with the last line raising the memory limit.
define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', true );
define( 'DOMAIN_CURRENT_SITE', 'example.uz' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );
define( 'WP_MEMORY_LIMIT', '256M' );
With terminal access you can do the same with WP-CLI and create sites from the command line.
wp core multisite-convert --subdomains
wp site create --slug=maktab5 --title="5-maktab" --email=admin@example.uz
wp site list --fields=blog_id,url
Memory, cache and disk
The default memory limit for Multisite is set a little higher than for a single site, but a plugin-heavy network may need more, so the hosting PHP memory_limit must not be lower than the WordPress limit. Every site gets its own set of tables in the shared database, so table count grows with the number of sites, affecting database speed and backup size. Uploads go to per-site folders under wp-content/uploads/sites/, so watch disk space and file count limits. Page caching and OPcache speed things up, and a Redis object cache helps with many active sites.
Backups and security
A Multisite backup covers the whole network: the database and wp-content must be saved together. Restoring a single branch is harder than restoring a normal site, so test your restore plan in advance. Only the network admin installs plugins, which helps security, but each new plugin affects every site. Test updates on a staging copy first to avoid breaking twelve sites at once.