How to Capture a Webpage Screenshot with Urlbox Without the Browser Toolbar

To capture a webpage with Urlbox without the browser toolbar, save or display Urlbox’s rendered image directly. The toolbar belongs to the browser application around a page; it is not part of the rendered webpage. Urlbox’s hide and CSS options can target elements inside the page, but cannot remove browser application chrome from a screenshot of a browser window. Urlbox’s screenshot documentation and render options describe those controls.

If the bar you want gone is actually a website navigation bar or sticky header, target that page element with a selector or CSS. First identify which kind of bar you are seeing, then choose the capture scope that fits your result.

What you see	Where it comes from	What to do
Address bar, tabs, browser buttons	Browser application chrome	Use Urlbox’s rendered image directly; do not screenshot the surrounding browser window.
Site navigation, announcement strip, sticky header	Page content	Use `hide` or custom CSS to target the page element.
URL or timestamp above the image	Urlbox render options	Check that `show_url` and `show_timestamp` are not enabled.

2. Capture the page with Urlbox

Send the page URL through Urlbox’s screenshot workflow and save the returned render. Choose the image format and viewport dimensions for your use. Urlbox documents a default viewport of 1280 by 1024 pixels.

For the currently visible viewport, leave full_page disabled.
For the entire scrollable page, set full_page to true.
For one region, set selector to a CSS selector for the element.

Urlbox documents stitch as its default full-page mode. It scrolls the page, triggers lazy-loaded content, captures sections, and stitches them together. Its native mode is faster but can be less accurate on some sites. See the Urlbox screenshots guide for mode details.

Full-page capture from the CLI

Urlbox’s documented CLI example captures a full page and writes the result to a file:

urlbox screenshot https://urlbox.com --full-page --output page.png

Replace the example URL and filename with the target page and desired output path. The CLI quickstart covers this command; the CLI rendering guide describes additional modes and flags.

3. Hide a bar that belongs to the webpage

If the unwanted bar is rendered as part of the site, use Urlbox’s hide option with a selector for that element, or inject CSS through its css option. The selector depends on the site’s markup; inspect the target page and confirm that it matches only the intended element.

For example, a site-specific CSS rule might look like this:

.site-header {
  display: none !important;
}

Use that rule as the CSS supplied to Urlbox’s documented css option. The example selector is illustrative: many sites use different class names, and hiding a header can also remove navigation or change page layout. Urlbox’s render options reference documents hide and css.

Capture one page element

When you need a specific card, article, or content region rather than the whole page, use selector to identify that element. Urlbox’s screenshots documentation explains how to find a CSS selector in browser developer tools. Verify that the selector is unique and that the element is present after the page finishes loading.

4. Choose full-page behavior carefully

Full-page capture has several edge cases that affect the final image:

Lazy-loaded images: Urlbox’s default stitch mode scrolls to trigger lazy content before stitching. The skip_scroll option disables the initial scroll; this may save time but can leave lazy content unloaded.
Fixed and sticky elements: A sticky header can recur across stitched sections. Urlbox says it uses heuristics to detect most fixed elements; freeze_fixed controls this behavior.
Infinite scrolling: Urlbox limits captured sections by default when it detects infinite scroll. allow_infinite can override that limit, so use it only when the longer capture is intended.
Very tall or wide pages: Consider max_height, full_width, and image-dimension constraints when the page exceeds the output size you need.

Use stitch when accuracy and lazy-loaded content matter. Consider native when speed is more important and the target page renders correctly in that mode. Check the result for repeated sticky elements and missing content before relying on it.

5. Troubleshooting

Symptom	Likely cause	Fix
Browser tabs or address bar appear in the image	You captured the browser window that displays the render.	Save or display Urlbox’s rendered image output directly.
The page’s own header remains visible	The bar is page content, and no matching page selector or CSS rule was applied.	Inspect the page markup, choose the correct selector, and use Urlbox’s `hide` or `css` option.
A URL or timestamp appears above the capture	`show_url` or `show_timestamp` is enabled.	Disable those options if the extra header is unwanted.
Images are missing in a full-page capture	Lazy content may not have loaded, or initial scrolling was skipped.	Use the default scroll-and-stitch behavior and check whether `skip_scroll` is enabled.
Sticky navigation appears several times	The page element was repeated while full-page sections were stitched.	Review `freeze_fixed` and test the full-page mode on the target page.
A selector capture is empty or wrong	The selector does not match, is not unique, or the element was not present when captured.	Recheck the selector in developer tools and confirm the page has loaded the element.
The full-page image is unexpectedly long or truncated	Infinite scrolling or output-dimension limits affect the capture.	Review `allow_infinite`, `max_height`, `full_width`, and the image-dimension constraints.

6. Performance, reliability, and cost considerations

Full-page stitching does more work than capturing the visible viewport because it scrolls and combines sections. Urlbox describes native as faster, while stitch is optimized for accuracy. Skipping the initial scroll can reduce work but risks missing lazy-loaded elements. The supplied Urlbox documentation does not establish a general render-time benchmark or pricing figure, so check Urlbox’s current product information for plan and cost details before estimating a workflow.

For repeatable results, keep the capture scope and viewport consistent, use a selector that matches the intended element, and inspect captures of pages with sticky headers, lazy content, or infinite scroll. A webpage can change its markup, so page-specific selectors may need maintenance.

Or skip the browser setup

ScreenshotNeo returns a webpage screenshot or PDF from one GET request. Cookie banners, newsletter popups, and chat widgets are removed before the shot; those cleanup steps can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers say which verdict applied and whether the shot was billed. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs.

Example with cURL:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

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)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

See the ScreenshotNeo API docs for request options. It includes full-page capture with lazy images loaded, CSS selector capture, viewport and device presets, custom CSS and JavaScript, waiting controls, request blocking, cookies and headers, caching, signed links, async jobs, and bulk capture. Plans include 1,000 shots per month free with no card; paid plans start at $5 for 3,000. Sign up free for 1,000 screenshots a month, with no card required.

FAQ

Can Urlbox hide the browser address bar with CSS?

No. CSS applies to the rendered webpage. The address bar belongs to the browser application outside the page.

How do I capture only the visible viewport?

Leave full_page disabled and use the viewport dimensions you need.

Will a page selector work on every website?

No. Selectors depend on each site’s markup and can change. Inspect the target page and confirm the selector identifies the intended element.