Hero web part

The Hero web part is the large visual banner at the top of most SharePoint intranet homepages. It presents up to five items, each with a background image, a headline, an optional description and a link, and it comes pre-loaded on the communication site template so most people meet it as the thing already sitting on a new site. It has three layouts — Tiles, Layers and Carousel — and it is used primarily as a visual navigation block rather than for holding content.

Part of the SharePoint web parts reference · Verified against Microsoft documentation · Last reviewed 1 September 2026

The three layouts

All three cap at five items. The choice between them is really a choice about what the banner is for.

The three Hero web part layouts compared
Tiles Layers Carousel
Arrangement Mosaic grid, one large tile plus smallerFull-width horizontal bands, stackedRotating slides in one space
Variants 3, 4 or 5-part1–5 layers1–5 slides, 3 styles
Call to action Largest tile onlyEvery layerPer slide
Vertical space CompactGrows with each layerFixed
Best for Navigation hubsShowcases, equal prominenceTimely promotions

Carousel is the newest of the three and has three slide styles — image overlay, text block and diagonal split — which can be set per slide, plus an autoplay toggle. Layers is the one to watch for page length: each band is full width, so five layers pushes everything else a long way down.

Image sizing

There is no single correct pixel dimension, and looking for one is the most common source of frustration with this web part. The Hero crops responsively for each layout, screen width and tile position, so one source image is displayed as several different rectangles depending on context.

Hero web part specifications Verified 1 September 2026
Hero web part specifications
Capacity
Layouts available 3 — Tiles, Layers, Carousel
Maximum items, any layout 5
Can the five-item cap be raised? No
Carousel slide styles 3
Image proportions
Tiles — overall web part shape 8:3
Tiles — image scaling ~4:3
Layers — each band 8:3
Layers — image scaling ~9:16
Recommended source file size 1 MB or larger
Minimum width for full-width sections 1920 px
Capabilities
Focal point control per image Yes
Inline video playback Yes, via Stream
Colour block instead of image Yes — one theme colour
Secondary call to action Yes
Audience targeting No
Full-width section support Communication sites only

Sources: Microsoft Support, Use the Hero web part; Microsoft Learn, Image sizing and scaling in SharePoint modern pages; Microsoft Tech Community guidance on Hero dimensions. Aspect ratios are approximate because rendering is responsive. Verified 1 September 2026. See the full SharePoint limits table for platform-wide figures.

Practical image advice

  • Leave room around the subject. The same image is cropped differently per layout and per breakpoint, so a tightly framed face will lose its head somewhere.
  • Set the focal point on every image. It is the only control you have over what survives the crop, and it takes seconds.
  • Do not bake text into the photograph. Use the Hero’s own headline and call-to-action fields. Flattened text gets cropped, scales badly, and is invisible to screen readers.
  • Darken the lower portion. Titles overlay the image in Tiles, so reducing contrast at the bottom of the artwork keeps them legible.
  • Start from a large original. A 900-pixel-wide source cannot fill a 1920-pixel column sharply. Re-exporting the small file will not fix it.

The audience targeting gap

The Hero web part does not support audience targeting. Every visitor sees the same five items, and there is no way to show one tile to the frontline and another to head office.

This matters more than it first appears. On a homepage serving several populations, the most prominent block on the page — the one above the fold, the one everybody sees first — is the only one that cannot be personalised. News, Quick links, Highlighted content and Events all support targeting. The banner does not.

The usual consequence Teams that need a targeted banner end up either removing the Hero entirely and rebuilding the top of the page from targetable web parts, or accepting a lowest-common-denominator banner that speaks to nobody in particular. Both are compromises worth knowing about before you design the homepage rather than after.

Full width, and where it is not available

A Hero spanning the whole browser width, with no side margins, requires a full-width section — and full-width sections exist only on communication site pages. They are not available on team sites.

On a communication site: edit the page, add a section, and choose full-width from the section layout control, then place the Hero inside it. If the full-width option is not in the list, the page is on a team site. That is a page layout boundary, not an image problem or a permissions problem, and no image size will work around it.

Key takeaways

  • 3 layouts Three layouts, not five Tiles, Layers and Carousel. Carousel is the newest and offers three slide styles plus autoplay.
  • 5 items max Five is the ceiling in every layout Five tiles, five layers or five slides. No setting raises it — pair the Hero with Quick links if you need more destinations.
  • None targeting The Hero cannot be audience targeted The most prominent block on the page is the only one that cannot be personalised. News, Quick links and Highlighted content all can.
  • 8:3 web part There is no single correct image size The web part crops responsively per layout and breakpoint. Tiles scales images near 4:3, Layers near 9:16, inside an overall 8:3 frame.
  • 1920 px min Start from a large original for full-width sections Microsoft recommends source files of 1 MB or more and at least 1920 px wide. Re-exporting a small file will not fix softness.
  • Comms sites only Full width is a communication site feature Team site pages have no full-width section, so a Hero there cannot stretch edge to edge. A missing option means a team site, not a config error.

When five tiles and no targeting isn't enough

ShortPoint replaces the banner rather than the platform. Its hero and carousel elements run on the same SharePoint pages, with no SPFx build, and remove the two constraints that most often force teams to abandon the native Hero.

  • Audience-targeted banners, so different populations see different content above the fold
  • No five-item ceiling, and layouts that are not fixed mosaics
  • Full control of typography, overlay treatment and cropping — including on team sites
  • Edited by your comms team in the same page editor

Used on 350,000+ SharePoint sites by 12M+ people · Microsoft Solutions Partner · No credit card required

Common questions about the Hero web part

What is the SharePoint Hero web part?

How many tiles can the Hero web part have?

What is the difference between the Tiles, Layers and Carousel layouts?

What image size should you use for the Hero web part?

Does the Hero web part support audience targeting?

Can you make the Hero web part full width?

Can you add a video to the Hero web part?

Can you remove or replace the Hero web part?

Sources

Related reference

Nearby in the reference