New

50% off Shop Products & 50% off 1st Month of Retainer Packages. Terms apply*. Contact us to apply your discount.

How to Use One Parent Theme for Multiple WordPress Sites

Kahunam Newsletter

Get quality content to grow your website. Sign up today for fresh ideas and inspiration.

As a subscriber, you'll have access to regular competitions with valuable prizes.

Home » Articles » Wordpress » How to Use One Parent Theme for Multiple WordPress Sites

You have two WordPress sites and want to use the same parent theme on both. The goal is simple: update the theme once, and have it apply to all your sites automatically.

The problem: WordPress doesn’t allow this by default. Each WordPress installation requires its own copy of theme files in its wp-content/themes/ directory.

The solutions: You have three options:

  1. WordPress Multisite (best for most people)
  2. Git version control + deployment
  3. Symbolic links (has security risks)

This guide shows you how to implement each method in 2025.

How to Share a Parent Theme Across Multiple WordPress Sites

Best for: Sites you manage yourself, sites sharing similar purposes, or sites for different departments of one organization.

How it works: One WordPress installation hosts multiple sites that all share the same core files, plugins, and themes.

Steps:

  1. Back up your existing sites
  2. Add define('WP_ALLOW_MULTISITE', true); to wp-config.php
  3. Go to Tools → Network Setup, follow instructions (full Multisite setup guide)
  4. Upload parent theme in Network Admin → Themes
  5. Click “Network Enable”
  6. Create second site in Network Admin → Sites → Add New
  7. Activate the theme on each site under Appearance

Updates: Update once in Network Admin, applies to all sites instantly.

Pros: One update for all sites, saves server space, shared management

Cons: All sites share database, all go down together if one crashes

Method 2: Git Version Control + Deployment

Best for: Developers comfortable with command line, agencies, or sites on different hosts.

How it works: Store your theme in Git, deploy to multiple sites.

Steps:

  1. In your theme folder, run: git init git add . git commit -m "Initial commit"
  2. Create GitHub repository and push: git remote add origin your-repo-url git push -u origin main
  3. On each site, clone the theme: cd /wp-content/themes/ git clone your-repo-url your-theme-name
  4. To update all sites: cd /wp-content/themes/your-theme-name git pull

Alternative: Use GitHub Deployments for WordPress (WordPress.com Business/Commerce plans only).

Pros: Works across different hosts, full version history, sites stay independent

Cons: Requires Git knowledge, manual deployment to each site

Security warning: Hackers actively exploit symbolic links to perform cross-account attacks and access sensitive files like wp-config.php.

Only use if: You control the entire server and understand Linux security.

Steps:

  1. Install theme on first site
  2. Create symlink on second site: ln -s /var/www/site1/wp-content/themes/your-theme /var/www/site2/wp-content/themes/your-theme
  3. Set permissions: chmod 755 on theme folder

Limitations: Same server only, blocked on most shared hosting, high security risk

Quick Comparison

MethodDifficultySecurityBest For
MultisiteMediumGoodSites you control
GitMedium-HighBestDevelopers/agencies
SymlinksLowRiskyAdvanced users only

Conclusion

Best choice: WordPress Multisite.

Install the parent theme once, use it across all sites, and update in one place. It’s the official WordPress solution.

Use Git if: Sites are on different hosts or you need complete independence.

Avoid symlinks unless: You’re a Linux expert with full server control.

Learn more:

Want help to make your website better?

We will assist you by sending helpful material once a month. Join the newsletter to receive what you need for your website.

Data processed subject to the Kahunam privacy policy.

Just posted

Become an expert website owner

Join our community of website professionals and learn how to achieve website success through our helpful newsletter.