BotBrowser Knowledge Hub — Page 5

Browse page 5 of BotBrowser articles on browser fingerprint protection, privacy signals, proxy consistency, and deployment.

  1. network

    Scraping Cookies: Keep State Across Browser Runs

    Separate scraping cookies, localStorage, IndexedDB and sessionStorage across runs. Check restored client state without confusing it with a valid server session.

    Read article →

  2. comparison

    What Does an Anti-Detect Browser Change?

    See what an anti-detect browser can configure, what remains tied to the host or network, and how to verify a profile before purchase.

    Read article →

  3. fingerprint

    CreepJS WebRTC Report: Trace the Fields

    Trace CreepJS WebRTC report fields to pinned APIs, SDP transforms and partial-result branches without treating them as identity.

    Read article →

  4. getting-started

    Headless Browser for AI Agents: Launch and Tool Boundaries

    Compare agent and MCP browser launch ownership, what tools expose, what operators must verify, and how headless differs from runtime limits.

    Read article →

  5. getting-started

    Headless Browser Scraping: What Actually Changes

    Compare headed Chrome, unified headless, and headless shell for scraping. Track renderer, viewport, and webdriver signals without claiming a site verdict.

    Read article →

  6. fingerprint

    Native Override Lies and What a toString Whitelist Sees

    One probe on patched APIs: which overrides a toString whitelist catches, which descriptors still leak, and why a Proxy or a bound function passes as native.

    Read article →

  7. getting-started

    Scraping with Playwright: Browser and Profile Setup

    Configure Playwright for an authorized list-to-detail scraping run. Separate browser profiles, cookies and extraction errors, then save a useful JSON result.

    Read article →

  8. getting-started

    Scraping with Puppeteer: Options and Observable Differences

    Map Puppeteer launch, viewport, storage, and headless options to page-visible observations in an owned scraping fixture.

    Read article →

  9. getting-started

    Selenium Browser Profile Integration and Session Ownership

    A practical approach to launching browser profiles with Selenium, keeping storage isolated, and closing sessions cleanly in authorized tests.

    Read article →

  10. getting-started

    Selenium Scraping: Capabilities and Records

    Build a bounded Selenium scraping run with an explicit Chromium binary, a capability receipt, a readiness condition, and validated catalogue records.

    Read article →

  11. getting-started

    Selenium WebDriver Waits for Stable Tests

    Choose Selenium waits from observable browser contracts so authorized tests remain readable, diagnosable, and stable across ordinary timing changes.

    Read article →

  12. getting-started

    Undetected Chromedriver: Browser-Layer Alternatives

    Compare undetected-chromedriver with browser-layer configuration by ownership, update surface, and the evidence an authorized fixture can record.

    Read article →