Skip to main content

Site Assets Library

Common Use Cases

  • Images for pages and news: stores images used in pages, news posts, and Hero web parts
  • Branding assets: logos, icons, banners, and design elements reused across pages
  • Embedded content: assets used in embeds, callouts, or custom layouts

Benefits

  • Automatically created: every modern SharePoint site includes a Site Assets library by default
  • Centralized asset storage: keeps images and supporting files in a predictable location
  • Permission inheritance: assets follow site-level permissions by default
  • Clean page management: separates content (pages) from supporting media (assets)
  • Easy reuse: assets can be reused across multiple pages without duplication

Key Considerations

  • Not for document collaboration: Site Assets is not intended for working documents
  • Permissions matter: users must have access to view assets referenced on pages
  • Used automatically by web parts: many web parts save files here without user awareness
  • Can grow quickly: image-heavy sites may accumulate large numbers of assets
  • Deletion impact: removing assets may break images or web parts on pages where they are used