Does Statamic handle multisite?

Statamic has built-in multi-site support, but it works quite differently from WordPress Multisite, so it’s worth understanding the distinction before assuming the concepts map directly.

WordPress Multisite is a network architecture where multiple distinct sites share a single WordPress installation and database, each with their own admin area, users, plugins, and themes. It’s primarily a hosting efficiency feature — it lets you run many sites from one installation.

Statamic’s multi-site feature is designed around localization and content variations. You can have multiple "sites" in a single Statamic installation, each with its own locale, URL, and optionally its own content. A common use case is a single brand with an English site at example.com and a French version at fr.example.com — both pulling from shared content, with translated or localized versions of entries where needed. You can also use it to run multiple distinct sites, including with different domains.

Where Statamic multi-site is strong: internationalization with content inheritance (translate only what needs translating), regional subdomains or subdirectories, and sites that share some content and structure but vary in locale or language.

Statamic does have per-site permissions, so you can restrict which users have access to which sites within a single installation. This is useful for giving translators access only to the sites they’re responsible for, for example. But it’s worth understanding that this is permission scoping within one shared installation — it’s not the same as WordPress Multisite’s model where users are on completely separate sites with separate admin areas. If you need truly independent sites for different clients or business units with strict separation, you’d more likely run separate Statamic installations. That’s a different operational model, but it’s also simpler to reason about — each site has its own codebase and content.

If you’re migrating from WordPress Multisite, the first question is what you’re actually using the multisite for. If it’s multilingual content for one brand, Statamic’s multi-site fits well. If it’s a network of independent sites, separate installs with shared infrastructure on the hosting side is often the better path. The right answer depends on your specific setup.

We’ve worked through a range of multisite migration scenarios. If you’re dealing with a complex WordPress Multisite network and aren’t sure how it would translate, get in touch and we can talk through the options before you commit to an approach.