SharePoint Site Templates: Custom Design Guide

How Do You Create Custom SharePoint Site Templates in 2026?

SharePoint site templates in 2026 are created using site designs (JSON-based site scripts) for simple configurations and PnP Provisioning templates for complex enterprise deployments that include pages, web parts, navigation, content types, and branding. In our 25+ years managing enterprise SharePoint environments, we have found that organizations without standardized site templates waste an average of 40 hours per month on manual site configuration and suffer from inconsistent branding, missing governance controls, and user confusion from non-uniform site structures.

Site templates are the foundation of scalable SharePoint governance. When every project site, department hub, and community looks different, users waste time learning new layouts instead of getting work done. A well-designed template library ensures every new site launches with the right structure, permissions, navigation, and branding — ready for immediate use.

Understanding the Template Ecosystem

SharePoint Online offers multiple approaches to site templating, each suited to different complexity levels.

Built-In Templates

Microsoft provides a growing library of built-in templates accessible from the "New site" dialog. These cover common scenarios like team collaboration, project management, crisis communication, and event management. They are a good starting point but rarely meet enterprise-specific requirements without customization.

Site Designs and Site Scripts

Site designs are the native SharePoint Online mechanism for custom templates. A site design is a collection of site scripts — JSON files that define actions to execute when a site is created. Actions include creating lists, applying themes, setting navigation, adding site columns, and triggering Power Automate flows.

Site designs appear in the "New site" dialog alongside built-in templates, providing a seamless experience for end users. They can be scoped to the entire tenant or specific groups of users.

PnP Provisioning Templates

The PnP (Patterns and Practices) Provisioning framework is a community-driven, Microsoft-supported engine for comprehensive site provisioning. PnP templates can define everything a site design can, plus pages with web parts, managed metadata term sets, search configurations, content type hierarchies, and complex permission structures.

PnP templates are defined in XML or JSON and applied using PnP PowerShell or the PnP Provisioning Service. They are the standard for enterprise-grade site templating.

Custom Site Templates (Save Site as Template)

SharePoint Online allows users to save an existing site as a template. This captures the site structure, lists, content types, and pages (without content). The saved template appears in the template gallery for reuse. This is the simplest approach but has limitations — it does not capture all configurations and can create drift over time.

Designing Effective Site Templates

Start with Information Architecture

Before building templates, define your site architecture:

• What types of sites does your organization need? (Project sites, department hubs, community sites, client portals)
• What should every site include? (Standard navigation, required libraries, governance metadata)
• What should be customizable? (Logo, color accent, department-specific lists)
• What should be locked down? (Permission levels, sharing settings, retention policies)

Template Design Principles

Principle 1: Minimal viable structure. Include only what every site of that type needs. Adding too many lists, libraries, and pages to a template creates clutter that users immediately try to delete.

Principle 2: Consistent navigation. Every template should include a standard navigation structure that follows your organization's information architecture. Hub navigation for cross-site links, site navigation for within-site links.

Principle 3: Pre-configured governance. Apply sensitivity labels, sharing restrictions, and retention policies as part of the template. Do not rely on site owners to configure governance after creation.

Principle 4: Branded but flexible. Apply organizational branding (logo, colors, fonts) through the template but allow site owners to customize within brand guidelines (accent color selection from an approved palette).

Building Site Designs with Site Scripts

Creating Your First Site Script

Site scripts are JSON arrays of actions. Here is a foundational example that creates a project site with standard lists and a custom theme:

The script would create a Documents library with custom columns (Project Code, Document Type, Status), a Project Tasks list with columns for assignee, due date, and priority, apply the organization's custom theme, set the site logo, configure the navigation with links to key resources, and trigger a Power Automate flow that notifies the IT governance team of the new site creation.

Registering Site Designs

Use PowerShell to register your site script and associate it with a site design. Specify whether the design applies to Team sites (GROUP#0) or Communication sites (SITEPAGEPUBLISHING#0). Add a preview image and description that appear in the site creation dialog to help users choose the right template.

Advanced Site Script Actions

Site scripts support over 30 actions in 2026, including:

• createSPList / addSPList: Create lists and libraries with custom columns and views
• applyTheme: Apply a custom color theme
• setSiteLogo: Set the site logo URL
• addNavLink: Add navigation links
• setRegionalSettings: Configure language, time zone, and locale
• triggerFlow: Launch a Power Automate flow for post-provisioning tasks
• associateHubSite: Associate the new site with a hub site
• installSolution: Install an SPFx solution package
• setSiteExternalSharingCapability: Configure sharing settings

PnP Provisioning for Enterprise Templates

For templates that exceed site script capabilities — which is most enterprise scenarios — PnP Provisioning is the standard.

Creating a PnP Template from an Existing Site

The fastest way to create a PnP template is to configure a "golden" site manually, then extract its configuration using PnP PowerShell. The extraction captures site structure, content types, fields, lists, views, pages, web parts, navigation, themes, and more.

After extraction, clean up the template to remove site-specific details (URLs, GUIDs) and parameterize values that should change per instance (site name, owner, department).

Applying PnP Templates

Apply templates using PnP PowerShell during or after site creation. For self-service scenarios, combine a basic site design (for the creation dialog) with a Power Automate flow that applies the full PnP template after creation. This gives users a familiar template selection experience while delivering enterprise-grade provisioning behind the scenes.

Template Versioning and Maintenance

Treat templates like code — store them in a Git repository, version them, and test changes before deploying to production. We recommend maintaining a template development site where changes are tested before updating the production template.

Create a template maintenance schedule: review and update templates quarterly to incorporate new SharePoint features, updated branding, and refined governance controls.

Custom Look Book and Template Gallery

Building an Internal Look Book

Create a SharePoint Communication site that serves as your organization's template gallery. Include screenshots, descriptions, and use cases for each available template. This helps site requestors choose the right template and reduces the number of misconfigured sites.

Template Request and Approval Workflow

Not every user should be able to create sites directly. Implement a Power Automate approval workflow where users request a new site by filling out a form (site name, purpose, template type, owner, expected membership). An approver reviews the request, and upon approval, the site is automatically provisioned using the selected template.

This workflow ensures governance without creating a bottleneck — approvals should target a 4-hour SLA to avoid frustrating users into shadow IT.

Branding and Theming

SharePoint Theme Generator

Use the SharePoint Theme Generator tool (fabricweb.z5.web.core.windows.net/pr-deploy-site/refs/heads/7.0/theming-designer) to create custom color themes that match your organizational branding. Export the theme JSON and deploy it using PowerShell.

Custom Headers and Footers

SharePoint Online supports custom headers, footers, and navigation through the SharePoint admin center and SPFx Application Customizers. Use these to add consistent elements across all sites — company logo, footer links, support contact information, and legal disclaimers.

Responsive Design Considerations

All SharePoint templates must work on mobile devices. Test your templates on phones and tablets, ensure web parts are responsive, and verify that custom elements do not break the mobile layout. SharePoint's modern experience is responsive by default, but custom CSS and SPFx extensions can introduce layout issues.

Migration Considerations

When migrating to SharePoint Online, design your target templates before migration. Map source sites to target templates to ensure consistent structure post-migration. Our [migration services](/services/sharepoint-migration) include template design as a standard deliverable.

Enterprise Governance Integration

Templates should enforce governance automatically. Configure sensitivity labels, DLP policies, retention policies, and sharing restrictions as part of every template. Our [SharePoint consulting services](/services/sharepoint-consulting) help organizations design template libraries that embed governance into every site from creation.

For ongoing template management and updates, our [support plans](/services/sharepoint-support) include quarterly template reviews and updates. [Contact us](/contact) to discuss your template standardization needs.

Frequently Asked Questions

What is the difference between a site design and a site template?

A site design is a collection of site scripts (JSON actions) that run when a site is created. A site template is a broader term that includes site designs, PnP provisioning templates, and saved-site templates. Site designs are limited to about 30 predefined actions, while PnP templates can configure virtually every aspect of a site.

Can I update a template after sites have been created from it?

Site designs can be re-applied to existing sites to apply new actions. However, they do not remove or modify existing configurations — they only add. PnP templates can be applied incrementally with more granular control over updates. For major template changes, plan a phased rollout and communicate changes to site owners.

How many templates should an organization have?

Most enterprises need 5 to 10 templates: a general team site, a project site, a department hub, a community site, a client portal, and a few industry or function-specific templates. Resist the urge to create a template for every minor variation — use a base template with optional customization instead.

Can I restrict which templates users can see?

Yes. Site designs can be scoped to specific security groups using PowerShell. Users outside the group will not see the template in the site creation dialog. This allows you to offer specialized templates to specific departments while keeping the general template gallery clean.

How do I handle template changes across hundreds of existing sites?

For site designs, use PowerShell to re-apply the updated design to existing sites in batch. For PnP templates, use PnP PowerShell scripting to apply incremental changes. Always test changes on a pilot group of sites before tenant-wide deployment.

What is the PnP provisioning engine and is it supported by Microsoft?

PnP (Patterns and Practices) is a community-driven initiative with strong Microsoft involvement. While not an official Microsoft product, it is widely used and recommended by Microsoft for enterprise provisioning scenarios that exceed native site design capabilities. Microsoft employees actively contribute to the PnP project.

Can templates include pre-built pages with web parts?

Site designs cannot create pages with web parts. PnP provisioning templates can, and this is one of the primary reasons enterprises choose PnP over native site designs. A PnP template can include fully designed home pages, document center pages, and dashboard pages with configured web parts.

How do I manage templates across multiple tenants?

Store templates in a shared repository (Azure DevOps, GitHub) and deploy to each tenant using CI/CD pipelines. Parameterize tenant-specific values (URLs, admin accounts, theme colors) so the same template source can be deployed to development, staging, and production tenants.