Basic concepts of scroll snap

The properties in the CSS scroll snap module enable you to define how scrolling snaps to specific points as a user scrolls through a document.

The scroll snap feature lets you define the snap positions where a scroll container's scrollport may end or "snap to" after a scrolling operation has completed.

Key properties for CSS scroll snap

Before you can define scroll snapping, you need to enable scrolling on a scroll container. You can do this by ensuring that the scroll container has a defined size and that it has overflow enabled.

You can then define scroll snapping on the scroll container by using the following two key properties:

  • scroll-snap-type: Using this property, you can define whether or not the scrollable viewport can be snapped to, whether snapping is required or optional, and the axis on which the snapping should occur.
  • scroll-snap-align: This property is set on every child of the scroll container and you can use it to define each child's snap position or lack thereof.
  • scroll-snap-stop: This property ensures that a child is snapped to during scrolling and not passed over.
  • scroll-margin: This property can be set on child elements that are snapped to during scrolling to create an outset from the defined box.
  • scroll-padding: This property can be set on the scroll container to create a snapping offset.

The example below demonstrates scroll snapping along the vertical axis, which is defined by scroll-snap-type. Additionally, scroll-snap-align applies on all the children of the <section> element, dictating the point where the scrolling of each child should stop.

html
<article class="scroller">
  <section>
    <h2>Section one</h2>
  </section>
  <section>
    <h2>Section two</h2>
  </section>
  <section>
    <h2>Section three</h2>
  </section>
</article>
css
.scroller {
  height: 300px;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
}

.scroller section {
  scroll-snap-align: start;
}

Using scroll-snap-type

The scroll-snap-type property needs to know the axis along which scroll snapping happens. This can be x, y, or the logical mappings block or inline. You can also use the keyword both to have scroll snapping work along both axes.

You can also pass in the keywords mandatory or proximity. The mandatory keyword tells the browser whether the content has to snap to a certain point, no matter where the scroll is. The proximity keyword means that the content may snap to the point, but does not have to.

Using mandatory creates a very consistent scrolling experience — you know the browser will always snap to each defined point. This means that you can be confident that something you expect to be at the top of the screen will be there when scrolling finishes. However, it can cause problems if the content is larger than you expect — users may find themselves in the frustrating position of never being able to scroll and view a certain point in the content. Therefore, the use of mandatory should be carefully considered and only used in situations where you know how much content is on the screen or scrollable section at any time.

Note: Never use mandatory if the content inside one of your child elements will overflow the parent container because user will not be able to scroll the overflowing content into view.

The proximity value only snaps child elements to a position when it is close by, with the browsers determining the exact distance. Click "Play" to edit the example below in the MDN Playground. Alternate the scroll-snap-type value between mandatory and proximity to see the effect this has on the scroll experience.

html
<article class="scroller">
  <section>
    <h2>Section one</h2>
    <p>
      Turnip greens yarrow ricebean rutabaga endive cauliflower sea lettuce
      kohlrabi amaranth water spinach avocado daikon napa cabbage asparagus
      winter purslane kale. Celery potato scallion desert raisin horseradish
      spinach carrot soko.
    </p>
  </section>
  <section>
    <h2>Section two</h2>
    <p>
      Turnip greens yarrow ricebean rutabaga endive cauliflower sea lettuce
      kohlrabi amaranth water spinach avocado daikon napa cabbage asparagus
      winter purslane kale. Celery potato scallion desert raisin horseradish
      spinach carrot soko.
    </p>
  </section>
  <section>
    <h2>Section three</h2>
    <p>
      Turnip greens yarrow ricebean rutabaga endive cauliflower sea lettuce
      kohlrabi amaranth water spinach avocado daikon napa cabbage asparagus
      winter purslane kale. Celery potato scallion desert raisin horseradish
      spinach carrot soko.
    </p>
  </section>
</article>
css
.scroller {
  height: 300px;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
}

.scroller section {
  scroll-snap-align: start;
}

In the above example, both height: 300px; and overflow-y: scroll; are set on the scroll container. If the content doesn't overflow its container, there is nothing to scroll.

Using scroll-snap-align

The valid values for the scroll-snap-align property include start, end, center, and none. These values are used to indicate the point in the scroll container to which the content should snap. Click "Play" in the example below and change the value of scroll-snap-align to see how this changes the scroll behavior.

css
.scroller {
  height: 200px;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
}

.scroller section {
  scroll-snap-align: start;
}

If scroll-snap-type is mandatory and scroll-snap-align on a child is either set to none or not set (in which case, it defaults to none), the user will be unable to scroll that element into view.

Using scroll-padding

When using start or end, if you do not want the content to snap right to the edge of the scroll container, or if you want the snap position to be slightly offset from center when using center, use the scroll-padding property or its equivalent longhand values to add some padding.

In the example below, scroll-padding is set to 50px. When the content snaps to the start of the second and third sections, scrolling stops 50 pixels away from the start of the section. Try changing the scroll-padding value to see how this changes the distance.

html
<article class="scroller">
  <section>
    <h2>Section one</h2>
  </section>
  <section>
    <h2>Section two</h2>
  </section>
  <section>
    <h2>Section three</h2>
  </section>
</article>
css
.scroller {
  height: 300px;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
  scroll-padding: 50px;
}

.scroller section {
  scroll-snap-align: start;
}

This is potentially useful if you have a fixed element such as a navigation bar, which could end up overlapping scrolled content. By using scroll-padding, you can reserve space for the fixed element, as shown in the example below, where the <h1> element remains on screen as the content scrolls beneath it. Without padding, the heading would overlap some of the content when snapping happens.

css
.scroller h1 {
  position: sticky;
  top: 0;
  min-height: 40px;
  background-color: #000;
  color: #fff;
  margin: 0;
  padding: 0;
}

.scroller h2 {
  margin: 0;
  padding: 0;
}

.scroller {
  height: 300px;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
  scroll-padding: 50px;
}

.scroller section {
  scroll-snap-align: start;
}

Using scroll-margin

The scroll-margin property or the longhand scroll margin values can be set on child elements, defining an outset from the defined box. This allows for different amounts of space for different child elements and can be used in conjunction with scroll-padding on the parent.

css
.scroller {
  height: 300px;
  overflow-y: scroll;
  scroll-snap-type: y mandatory;
}

.scroller section {
  scroll-snap-align: start;
  scroll-margin: 40px;
}

Using scroll-snap-stop

Using the scroll-snap-stop property, you can specify whether the scrolling must snap to the defined snap points. In the above examples, this would mean that the scrolling would stop at the start of each section or be able to skip past sections.

With this property definition, you can ensure that users see each section of the scroller and don't accidentally scroll past them. However, this setting can also negatively affect user experience by preventing the user from quickly scrolling to their desired content.

See also