ScreenshotNeo

BlogHow-to

How to Take FireShot Screenshots of a Web App with Sticky Headers

Choose the right FireShot capture mode for a sticky header or scrolling panel, then check the result for repeated headers, clipping, and missing content.

By the ScreenshotNeo team4 October 20267 min read

To capture a web app with FireShot, choose Capture entire Page for the whole document, Capture visible Area for what is currently on screen, or Capture Selected area for a specific region. If the app scrolls inside a panel, try capturing that scrolling element if your FireShot edition supports it. FireShot reports improved handling of sticky and fixed elements, but the result can depend on the page structure, so inspect the saved capture for repeated headers, clipped content, or an incomplete panel.

Choose the capture mode

First decide what needs to be preserved. A sticky header is a positioning behavior; it does not by itself determine whether the target is the whole document, the current viewport, or a nested scrolling panel.

Your goal FireShot mode to try Check the result for
Document the complete page Capture entire Page Repeated or missing sticky header; content that loads only after scrolling
Record exactly what a visitor sees now Capture visible Area Whether the header and relevant content are both in frame
Record a particular part of the screen Capture Selected area Selection boundaries, clipped edges, fixed elements
Capture a table or feed that scrolls inside the app Try the scrolling element/area capture if available in your edition Whether the full inner panel was captured, rather than only its visible portion

FireShot’s instructions distinguish whole-page, visible-area, and selected-area capture. Its release notes describe handling for scrolling content inside page elements, while the Chrome listing describes capture of specific scrolling areas as an upgrade feature. Availability can depend on edition and distribution.

Capture the page in FireShot

  1. Open the web app and navigate to the page or panel you need.
  2. Open FireShot from its toolbar button, main menu, or the page context menu. The toolbar button uses the configured default capture method and action.
  3. For a full document, choose Capture entire Page and…. For the current viewport, choose Capture visible Area and…. To define a region yourself, choose Capture Selected area and… and draw the selection.
  4. If the target is an inner scrolling panel, look for the scrolling-area or page-element capture option in your installed version. Select the panel when possible; this behavior can vary across app layouts and FireShot editions.
  5. Choose an output action or format that suits the task, such as an image for a quick visual record or PDF for a document workflow.
  6. Open the saved result and inspect the entire capture before you share or archive it.

FireShot’s official instructions list PDF, PNG, GIF, JPEG, and BMP outputs. Its Chrome listing highlights PDF with links, PNG, and JPEG; advanced PDF and editing features may depend on the installed edition. Check the menu and listing for the version you use.

What to expect from sticky headers

FireShot release notes report “Better handling of sticky and fixed elements while page is scrolled.” They also describe selection capture as providing minimum handling of fixed and sticky elements to capture what is shown on the page. These statements describe product behavior, not a guarantee for every app.

A full-document capture may show a fixed header once, repeatedly, or in a way that is not useful for your documentation, depending on how the page is built and captured. For a record of the current on-screen appearance, visible-area or selected-area capture is a reasonable mode to try. For a long page, use full-page capture and inspect the output. There is no universal FireShot setting established by the available documentation that always removes, repeats, or preserves a header exactly as intended.

Capture a scrolling panel

Many web apps keep a table, message list, or results feed inside a fixed-height element with its own scrollbar. A whole-page capture may include only the portion of that panel currently visible because the document itself does not contain the panel’s off-screen content as ordinary page scrolling.

  1. Identify whether scrolling the pointer over the content moves the page or only the panel.
  2. Try FireShot’s scrolling-element or scrolling-area capture, if present in your build.
  3. If the panel is inside a frame or the app loads more rows dynamically, inspect whether the capture includes all expected content. Support for frames, infinite pages, and oversized page elements is described in FireShot release notes, but combinations vary.
  4. If the scrolling-area option is unavailable or incomplete, capture visible sections separately or use the app’s own export function when it provides one.

Pick an output and verify it

Use an image when the goal is to preserve appearance in a report or issue. Use PDF when the recipient needs a document; confirm whether the PDF is single-page or paginated and whether links or selectable text matter for your workflow. The available formats and advanced options vary by FireShot version and edition.

  • Check the top and bottom edges for clipped content.
  • Check that the sticky header does not obscure a title, table row, or other important content.
  • For a nested panel, compare its first and last expected rows with the capture.
  • For dynamic pages, wait for the content you need to appear before starting capture.
  • Retake with visible-area or selection capture when the goal is to document the current screen rather than the full document.

Or skip the browser setup

If you need a screenshot from code or an automated workflow, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF. This example requests a WebP screenshot of a page; see the ScreenshotNeo API documentation for the available 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}`);
const data = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', data));

Cookie and consent banners, newsletter popups, and chat widgets are removed before the shot. Bot checks, blank pages, timeouts, and failed loads are never billed; cache hits also cost nothing, and response headers identify the page verdict and billing status. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots.

Sign up free for ScreenshotNeo: 1,000 screenshots a month, no card required.

Performance, reliability, and cost

For FireShot, the capture is performed in the browser and the resulting file is saved through the chosen action. Large full-page captures and long scrolling panels contain more content than a viewport capture, so allow the capture to finish and check that it completed before closing the tab. Dynamic loading, frames, and nested scroll containers can affect completeness. The sources do not establish a universal capture-time benchmark.

FireShot’s official materials describe free and Pro versions, with advanced capabilities associated with Pro. Verify the feature set in the store or vendor distribution you installed; store metadata may not match every distribution. For ScreenshotNeo, pricing is Free for 1,000 shots/month, Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free. Every feature is available on every plan. Only clean shots are billed, according to the product facts above.

Troubleshooting

Symptom Likely cause What to try
The sticky header covers content or appears unexpectedly Fixed positioning is handled differently during full-page capture Inspect the output; try visible-area or selected-area capture for an on-screen record. FireShot documents improved handling, not a universal outcome.
Only the visible part of a panel appears The panel scrolls independently of the document Try scrolling-area capture if your edition offers it; otherwise capture sections or use the app’s export.
The capture ends before all rows or images appear Content loads dynamically or lazily Wait for the needed content to load, then capture; verify the final rows and images.
A command or output option is missing Feature availability differs by edition, browser store listing, or vendor distribution Check the installed build’s menu and current listing; confirm whether the feature requires Pro.
A selection does not preserve the expected sticky behavior FireShot describes selection as having only minimum sticky/fixed-element handling Try visible-area capture for the exact current appearance, or full-page capture if document coverage matters more.
PDF layout differs from the screen PDF is a document output and may paginate or handle links/text differently from an image Check the installed PDF options and inspect the saved document before sending it.

Frequently asked questions

How do I take a full-page screenshot with a sticky header?

Choose FireShot’s Capture entire Page mode, then inspect the saved file. If the header or content is unsuitable, try visible-area or selected-area capture based on what you need to show.

How do I screenshot a scrolling panel in a web app?

Try FireShot’s scrolling-element or scrolling-area capture if it is available in your edition. A normal whole-page capture may not include content hidden inside an independently scrolling panel.

Does FireShot always remove or repeat the sticky header?

No universal outcome is established by the cited FireShot materials. They report improved handling and describe a limitation for selection capture, so verify each result.

Which FireShot format should I use?

Choose an image for a visual record and PDF when you need a document. Confirm the available formats and PDF features in the FireShot build you use.

Sources