The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →If a Browserless screenshot looks unstyled, first check whether the capture happened before stylesheets loaded or the request filtered CSS out. Then verify the page reached its intended state: a target-site error or CAPTCHA can look like a rendering problem, and a successful API response does not prove the target page rendered successfully.
Start by checking what page was captured
Inspect the screenshot and, where available, the page content or response details. Confirm that the browser reached the intended URL and did not land on a redirect, consent wall, target-site error, CAPTCHA, or access-denied screen. Browserless notes that its API can return HTTP 200 even when the target site displayed a 403, 404, or 500; an API-level success is not proof of a successful target-page render. Browserless troubleshooting guidance also identifies blank or white images, CAPTCHA pages, and 403/access-denied screens as possible signs of automation blocking. If you see one of those, investigate blocking rather than repeatedly extending the CSS wait.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Search+ For Google | Buy on Amazon | |
| 2 |
|
Amazon Silk - Web Browser | Buy on Amazon | |
| 3 |
|
Web Browser Engineering | $50.00 | Buy on Amazon |
| 4 |
|
Web Browser Surfer 3rd Edition (Web Surfer Series Book 1) | $0.99 | Buy on Amazon |
| 5 |
|
Downloader for Fire, Browser... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Choose a navigation wait that includes stylesheets
domcontentloaded means the initial HTML has been parsed; it does not wait for stylesheets, images, or subframes. Browserless documents that the load event waits for dependent resources, including stylesheets. If the screenshot starts at domcontentloaded, try load first. Browserless navigation-wait documentation
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Wait condition | What it waits for | When to try it |
|---|---|---|
domcontentloaded |
Initial HTML parsing, not stylesheet completion. | Usually too early when the problem is missing CSS. |
load |
Dependent resources, including stylesheets. | A useful first change when styles have not arrived by capture time. |
networkidle0 |
Zero active network connections for at least 500 ms. | When the page’s resources settle and a network-quiet signal is appropriate. |
networkidle2 |
No more than two active network connections for at least 500 ms. | When a page keeps a small amount of background activity open. |
Network-idle waits are not a guarantee that a single-page application has finished updating its visible state. Browserless examples use Puppeteer’s networkidle2 and Playwright’s networkidle; use the spelling and behavior supported by the particular Browserless endpoint and client you call. Browserless screenshot guide
#1 Best Overall
- google search
- google map
- google plus
- youtube music
- youtube
Wait for the final application state
For client-rendered pages, use a selector that appears only after the content or layout you need is ready, or a page-side readiness condition if your Browserless surface supports one. Browserless REST configuration supports waitForSelector; its screenshot guide also describes waiting for events, functions, selectors, or a timeout. Browserless REST screenshot API · Browserless screenshot guide
Pick a marker tied to the desired final state. A selector already present in the initial HTML may appear before JavaScript has populated the page or applied its final state. A fixed delay can help confirm a timing race, but it is less dependable than an application-ready signal; retain it only when the page has a known timing behavior and no better signal is available.
Rank #2
- Easily control web videos and music with Alexa or your Fire TV remote
- Watch videos from any website on the best screen in your home
- Bookmark sites and save passwords to quickly access your favorite content
Check that CSS requests are not being filtered
Review request options such as rejectResourceTypes and rejectRequestPattern. Browserless documents both and shows a pattern that rejects CSS requests; if your request uses such a filter, the unstyled result may be expected. Remove or narrow the filter, then capture again. Browserless REST screenshot API
If you deliberately need to add or replace styles, Browserless Screenshot API supports addStyleTag with CSS content or a stylesheet URL. Treat that as an intentional styling change, not as a substitute for checking whether the original stylesheet was requested and delivered. Browserless screenshot guide
Rank #3
Verify viewport, capture area, and late-loading images
- Set the viewport explicitly. Responsive pages can use a different layout at a different width or height. Browserless’s BAP documentation recommends setting the viewport before capture when layout is responsive. Browserless BAP screenshot documentation
- Check the capture scope. A viewport screenshot, selector capture, clip, and full-page capture show different areas; confirm the request captures the area you expect. Browserless screenshot guide
- Separate missing images from missing CSS. BAP’s
waitForImagesdefaults tofalse. Enable it or wait for a relevant selector when images arrive late. Lazy-loaded content below the fold may require scrolling; the REST screenshot guide documentsscrollPage: true. Missing imagery can make a page look incomplete even when its CSS is working. Browserless BAP screenshot documentation · Browserless REST screenshot API
If only the PDF looks wrong, check print behavior
PDF generation follows Chrome’s print pipeline, so diagnose it separately from a PNG or JPEG screenshot. Browserless documents that PDFs honor print stylesheets and that printBackground defaults to false. If print CSS is producing the wrong layout, Browserless documents emulating the screen media type before generating the PDF. Use these checks only when the discrepancy is in PDF output. Browserless PDF documentation
A focused troubleshooting sequence
- Confirm the target URL and inspect for redirects, target-site errors, consent pages, CAPTCHA, or access denial.
- Remove or adjust any request filter that rejects CSS resources.
- Replace
domcontentloadedwithload, or try a supported network-idle wait if the page’s resources settle that way. - For JavaScript-rendered content, wait for a selector or readiness condition that identifies the final visible state.
- Set the viewport and capture region deliberately; for missing late images, enable image waits or scroll to trigger lazy loading.
- If the issue is limited to PDFs, inspect print backgrounds and print-versus-screen media behavior.
Or skip the browser setup
For a one-request alternative, ScreenshotNeo returns a screenshot or PDF from a URL. 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
Recommended Free Tools
- Cookie banners are accepted and removed before capture; the service also removes known consent platforms, newsletter popups, and chat widgets. Each of these steps can be turned off.
- Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers report the page verdict and billing status.
- An MCP server provides
take_screenshot,get_page_info, andcapture_pdftools for AI agents and MCP clients. - The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo’s free plan.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Does HTTP 200 from Browserless mean the target page loaded correctly?
No. Browserless documents that an API response can be HTTP 200 while the target page displays an error such as 403, 404, or 500. Inspect the captured page itself.
Best Value
- Directly enter the URL of the desired file
- Store frequently visited URLs in the favorites section for easy retrieval
- Open the downloaded files in the file manager
Should I use network idle or a selector wait?
Use a network-idle wait when the page’s resources settle in a meaningful way. Prefer an application-specific selector or readiness condition when you need proof that a particular rendered state is ready.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
