How to Capture a Webpage with Sticky Headers in FireShot
Choose the right FireShot capture mode for a sticky header, and troubleshoot full-page captures that stop at the visible area.
Short answer: In FireShot, use Capture Selection when you want the screenshot to reflect what is currently visible, including how the sticky or fixed header appears on screen. FireShot describes this mode as providing minimal handling of fixed and sticky elements. It does not guarantee that every full-page capture will handle a sticky header correctly. If you need all off-screen page content, try full-page capture; if that stops at the first viewport, check whether the content scrolls inside a separate element.
1. Choose the capture scope first
“Capture a webpage” can mean several different things. Pick the mode based on what the image needs to show:
| What you need | FireShot mode to try | What to expect |
|---|---|---|
| The screen as it looks now | Capture Selection | FireShot says this mode minimally handles fixed and sticky elements to capture what is shown. It is intended to reflect the current view, not necessarily to collect every off-screen section. |
| Only the visible browser area | Capture visible area | Captures the current viewport. Content below or above it is not included. |
| The whole document | Capture entire page | Attempts to include off-screen content. A fixed header, nested scrolling region, or page-specific layout can affect the result. |
| One region, including content outside the viewport | Capture Selection | FireShot’s Firefox listing describes selecting off-screen regions with auto-scrolling. This is a reasonable option to try for a scrollable panel, but it is not a guarantee for every nested-scroll layout. |
FireShot documents exports to PDF, PNG, GIF, JPEG, and BMP, along with editing and annotation. Choose the output format after capture based on how you plan to use the result; the format itself does not change how sticky elements are captured. See the FireShot product page and its Firefox listing for product details.
2. Capture the current view with the sticky header
- Open the page and scroll to the position you want to document.
- Wait for any content that should appear in the screenshot to finish loading.
- Open FireShot’s capture commands and choose Capture Selection.
- Select the visible region you want. Keep the sticky header inside the selected area if it should appear in the result.
- Review the capture, then save or export it in the format you need.
This is the documented choice when the goal is to capture what is shown with minimal fixed or sticky handling. It does not mean FireShot removes the header, and it does not promise identical results across websites. If you need content beyond the current viewport, use a whole-page or region capture instead.
3. Capture the whole page or a scrolling panel
Use FireShot’s full-page option when the output must include content above or below the current viewport. Before capturing, identify which part of the page actually scrolls:
- The document scrolls: the browser’s main page scrollbar moves the content. Try full-page capture.
- A panel scrolls inside the page: a table, feed, menu, or results area may have its own scrollbar while the rest of the document stays still. Select that region and try FireShot’s selection capture, including its auto-scrolling behavior where available.
- Both scroll: the page and an inner panel move independently. Decide which one contains the needed off-screen content, and capture that scope first.
A fixed header can remain anchored while the main document moves. A separately scrolling, non-iframe element below a fixed header can present a different problem: FireShot may capture only the initially visible content instead of the full scrolling area. An individual support report describes that result in Chrome 129.0.6668.100 (64-bit), FireShot 2.1.2, and Windows 10, posted October 9, 2025. It documents one configuration, not how often the issue occurs.
4. Troubleshoot a capture that stops at the viewport
| Symptom | Likely explanation | What to try |
|---|---|---|
| Full-page output contains only the first screen | The page may contain a separately scrolling element below a fixed header, rather than one document that scrolls as a whole. | Check which scrollbar moves the missing content. Try selecting the scrolling region. If it persists, report the page structure and versions to FireShot support. |
| The sticky header appears differently than expected | Full-page capture and a screenshot of the current viewport have different goals; fixed positioning can affect how a long capture is assembled. | For the current on-screen appearance, try Capture Selection and include the header in the selection. |
| Off-screen panel content is missing | The content may live in a nested scroll container, which is distinct from the main document. | Try region selection with auto-scrolling if your FireShot version and browser listing provide it. Treat this as an attempt, not a universal fix. |
| Some content is absent even in the selected area | The content may not have loaded yet or may be outside the selected region. | Wait for the page to settle, scroll the relevant panel to the needed position, and reselect the area. |
| You cannot reproduce or describe the failure clearly | Browser version, extension version, operating system, and page structure can matter. | When safe, include a reproducible public example and state whether the content is an iframe or a separate scroll container in a post to the FireShot support forum. |
For a useful support report, include the browser and version, FireShot version, operating system, whether the content is in an iframe or separate scroll container, the capture mode, and a public reproduction page if it is safe to share.
5. Save in the format the result needs
After reviewing the capture, choose PDF when you need a document-style deliverable or an image format when you need a raster screenshot. FireShot lists PDF, PNG, GIF, JPEG, and BMP, and also describes editing and annotation. These choices affect how you store or share the result; they do not correct a capture that omitted part of a scrolling page.
6. Or skip the browser setup
If you need a clean screenshot through an API instead of configuring a browser extension, ScreenshotNeo accepts one GET request with a URL and returns PNG, JPEG, WebP, or PDF. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);
ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Create a free ScreenshotNeo account and get 1,000 screenshots a month with no card.
7. FAQ
Does Capture Selection remove a sticky header?
No. FireShot describes minimal handling intended to capture what is shown. It does not say that the header is removed.
Why can a full-page screenshot miss a panel that scrolls?
The panel may scroll independently from the document. The reported FireShot case involved a scrolling non-iframe element below a fixed header.
Does exporting to PDF fix a missing section?
No. Choose PDF or an image format after capture; output format does not change which page content the capture included.
Where can I report a page-specific failure?
Use the FireShot support forum and include the browser, extension, and operating system versions plus details about the scrolling element.


