Knowledge Base

Excel Templates for SharePoint: Create .xltx, .xltm, or legacy .xlt and add to the New menu

Standardize spreadsheets across your team by shipping a reusable Excel template and surfacing it directly in SharePoint.

Applies to: Microsoft 365 / Excel 2010+, SharePoint Online (modern)

This guide covers building an Excel template, choosing the right file extension, and wiring it into SharePoint so users create the right workbook with one click.

1) Choose the right template format

.xltx

Modern template (no macros). Recommended default.

.xltm

Macro-enabled template. Use when distributing VBA or legacy macro logic.

.xlt

Excel 97–2003 template. Keep only for very old clients.

Why not .xlsx? Workbooks (.xlsx) are single-use files. Templates (.xltx/.xltm/.xlt) create new workbooks pre-loaded with your styles, validation, and logic.

2) Build the Excel template

  1. Design your sheet (branding, styles, and structure)
    • Apply theme colors and cell styles.
    • Use Data → Data Validation for dropdowns.
    • Define named ranges (Formulas → Name Manager) like InputArea.
    • Protect cells/sheets if needed (Review → Protect Sheet).
    • (Optional) Add VBA if you plan on .xltm.
  2. Save as a template
    • File → Save As → Excel Template (*.xltx) for macro-free.
    • File → Save As → Excel Macro-Enabled Template (*.xltm) for VBA.
    • If supporting very old Excel: Excel 97–2003 Template (*.xlt).
Naming tip: Use a clear name—e.g., Matter Intake – Excel.xltx. This is what users will see in SharePoint’s New menu.

3) Add the template to SharePoint’s New menu (recommended)

Goal: make your template the obvious, one-click path for creating the correct workbook.

  1. Open the target SharePoint document library.
  2. Click the Settings gear → Library settings (or library command bar).
  3. Choose New → Add template (or “Create/Upload template” depending on tenant rollout).
  4. Upload your .xltx or .xltm and give it a friendly display name.
  5. Click New to confirm your template appears as a menu item.
Heads up: If your tenant has the modern “Manage templates” experience, you can replace/update the file here later; new documents will use the updated version automatically.

4) Alternative: attach the template via a Content Type (for governance)

Use this when different templates require different metadata, retention, or default values.

  1. At the site: Settings → Site settings → Site content typesCreate a new Document content type.
  2. Open the content type → Advanced settingsUpload a new document template (.xltx or .xltm).
  3. In the library: Library settings → Advanced settings → enable Manage content types.
  4. Add from existing site content types and select your new type; optionally reorder the New button.
Legal tech tip: Bind required fields like Matter ID, Client, and Practice Area; pair with Power Automate to validate and route files.

5) How users will use it

  1. Go to the SharePoint library.
  2. Click New → select the template (e.g., Matter Intake – Excel).
  3. A new workbook opens based on the template; complete fields and Save back to the library.
New → Matter Intake – Excel → Edit → Save → Done

6) Pro tips & versioning

  • Version your template: keep a master source; replace in the library or content type when updating.
  • Macros? Ship .xltm if you include VBA; new files will be .xlsm.
  • Legacy clients: Only use .xlt for Excel 2003-era compatibility.
  • Governance: Content Types + required columns + retention = consistent compliance.

FAQ

Can I just upload the template file into the library?
You can, but users may ignore it. Adding it to New (or via a Content Type) drives adoption and consistency.
Which extension should I pick?
.xltx for most cases, .xltm if you have VBA, and .xlt only for legacy.
Will updating the template change old files?
No. Existing workbooks remain as-is. Only new documents use the updated template.
Quick Reference
Save AsExcel Template (*.xltx) or Excel Macro-Enabled Template (*.xltm)
SharePointLibraryNewAdd template
Governance → Consider a Content Type with required metadata.