---
title: "Handle sticky headers and repeating overlays | FullPageShot"
description: "Capture pages with fixed navigation, banners and chat overlays and review Freeze repeating elements at the actual section joins."
url: https://fullpageshot.impulse-apps.de/guides/fixed-and-sticky-elements/
language: en
website: FullPageShot
publisher: Impulse Apps
---

Capture the right view

# Handle sticky headers and repeating overlays

Repeating navigation can cover content at every scroll position. Decide what needs to appear once and what should be closed before capture.

By Impulse Apps · Content reviewed on 7 October 2026

## Identify the overlay before starting

A fixed header, cookie banner or floating chat control can cover content without being part of the main document flow. Close overlays you do not need. Keep a header if it gives useful page context, then check its first appearance in the result.

Freeze repeating elements can suppress recognised fixed or sticky elements after their first appearance during full-page capture. This is a capture aid rather than a guarantee that every unusual overlay will be handled. Visible-area capture records the current view.

## Compare the option deliberately

1. Prepare a finite page and close irrelevant overlays.
2. Capture with Freeze repeating elements enabled.
3. Inspect the top, later joins and the area previously hidden by the overlay.
4. If important content is omitted, compare a smaller capture or test the option on the same page.

## Look for obscured content, not only repetition

A clean-looking image may still omit content behind a floating panel. Read the surrounding lines at joins and check them against the page. If the overlay is the issue you want to document, capture its visible state separately so its presence is not hidden by an option intended for cleaner full-page images.

## Choose the next step from the actual result

Take a smaller control capture before changing options when the page behaviour is unfamiliar. Compare the original page at the same scroll position with the saved image. Look at text immediately above and below the overlay, not only its outline. A banner can be irrelevant to one purpose and essential to another. Keep its visibility deliberate rather than accepting the cleanest-looking result automatically.

Do not hide an overlay manually during a running capture. Prepare that state before starting and leave the tab stable. If you need both a clean layout and evidence of the overlay, make two separate reviewed captures. Name each by its state so a later reader understands why the images differ. Check any source or date badge separately from the actual page content.

## A worked example

A support case concerns a chat bubble covering a checkout button. A full-page image that suppresses the bubble would lose the relevant evidence. Take a visible-area capture of the actual blocked state first. Use a separate full-page capture for surrounding layout if needed. Label the two files by purpose rather than describing either as a perfect copy of all page behaviour.

Add your observations. This template processes no files and sends no report.

### Check the result

### If something is wrong

**Observation and next step**

| Observation | Next step |
| --- | --- |
| Header repeats | Check the freeze option and actual overlay; compare a smaller scope if the page uses an unusual implementation. |
| Important overlay disappears | Capture its visible state separately; do not suppress the evidence you need. |
| Lines hidden at a join | Compare with the original page and choose a smaller stable capture. |

## Common questions

**Will every floating element be removed?**

No. The option handles recognised repeating elements; inspect the actual result.

**Should I close cookie banners?**

Close them when they are irrelevant to the purpose. Keep them deliberately when documenting their behaviour.

Review the actual saved file before sharing. Local history can retain the original capture separately from an edited or redacted export.

[Get help with this workflow](https://fullpageshot.impulse-apps.de/support/)

## Continue here

[Capture the right view](https://fullpageshot.impulse-apps.de/guides/full-page-captures/)

### Capture a long page from top to bottom

Use full-page capture, review stitched sections and understand why nested panels and growing pages need attention.

**Read the guide**

[Capture the right view](https://fullpageshot.impulse-apps.de/guides/visible-area-and-crop/)

### Choose a visible-area capture or crop

Select the right capture scope and crop screenshots using the editor while retaining the original in local history.

**Read the guide**

[Edit and keep your work](https://fullpageshot.impulse-apps.de/guides/website-bug-reports/)

### Prepare a screenshot for a useful website bug report

Capture a reproducible website state, annotate the actual issue and write expected versus observed behaviour without exposing private data.

**Read the guide**