Recommended Free Tools
For reliable browser automation, treat the browser process, browser context, and page as separate lifecycle objects. Give unrelated tasks fresh contexts, reuse state only when a workflow intentionally needs continuity, set bounded timeouts, and close contexts before the browser. In Playwright, a BrowserContext is the practical session boundary: it can own multiple pages while keeping its session isolated from other contexts.
What counts as a browser automation session?
“Session” can refer loosely to several objects. In Playwright, a browser process can host multiple BrowserContext objects, and each context can own one or more pages. A context is the useful boundary when you want a separate browser session: contexts are isolated from one another, including cookies and storage, and non-persistent contexts do not write browsing data to disk. A popup opened by a page remains in that page’s parent context. Playwright BrowserContext API
As an Amazon Associate I earn from qualifying purchases.
Puppeteer also provides BrowserContexts to isolate automation tasks. Its API describes non-default Chrome contexts as incognito; the default context may also be incognito when Chrome is launched with --incognito. Terminology and defaults are framework- and browser-specific, so check the API for the versions you have pinned. Puppeteer BrowserContext API
Choose the right isolation boundary
Use a fresh context for unrelated work
Use a separate context for each independent test, job, or simulated user when state must not leak between them. In Playwright’s test runner, a new context is created for each test by default. That makes isolation explicit and helps avoid order-dependent behavior caused by one test changing state another test inherits. Playwright isolation guide
#1 Best Overall
Use multiple pages in one context for one session
Pages within one context belong to the same session. This is appropriate when the task intentionally shares a user’s state across tabs or a popup and its opener. Opening a new page does not create an independent user session.
Use separate contexts for separate users
For a scenario such as an administrator working alongside a regular user, create two contexts in the same browser and give each user their own pages. This keeps their cookies and storage separate without requiring you to treat each page as a separate user. Playwright isolation guide
Build a predictable lifecycle
- Start the browser. Launch or connect to the browser using the API and configuration for your installed framework version.
- Create the context boundary. Create a fresh context for each unrelated task or test. Keep one context across steps that deliberately form a continuous user journey.
- Create pages inside the context. Open one or more pages for that session. Treat popups as part of their opener’s context unless you explicitly create a separate context for an independent user.
- Set only the required state. Use context-level cookie and permission APIs when needed. If the workflow reuses authenticated state, make that an explicit choice and protect stored credentials or state files according to your application’s security requirements. The available APIs do not establish one universal credential-storage policy. Playwright BrowserContext API
- Bound navigation and other waits. Configure context-level default and navigation timeouts, then check for page-level overrides if a wait does not use the timeout you expected.
- Handle failure at task boundaries. Make the orchestration layer account for navigation errors, timeouts, and unexpected context closure. Playwright exposes a context close event; closure can also follow a browser close or crash. Playwright BrowserContext API
- Close in order. Close explicitly created contexts, then close the browser. Closing a context closes its pages; orderly shutdown also gives artifacts such as HARs and videos an opportunity to be flushed and saved. Playwright Browser API
Fresh contexts or cleanup between tasks?
Prefer a fresh context when tasks should be independent
A new context makes the reset boundary clear and limits inherited cookies and storage. Playwright’s isolation guide describes fresh contexts as its test runner’s normal isolation model and notes that cleanup can be missed; some state, such as visited links, can be difficult to reset completely. Playwright isolation guide
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Clean up within a context when continuity is intentional
Keep a context when multiple steps belong to the same user journey—for example, when the user should remain logged in between steps. Use a distinct context for parallel or unrelated tasks that should behave independently. The choice is about the workflow’s state boundary, not a universal speed or resource rule; the official documentation cited here does not establish a measured performance comparison.
Timeouts, recovery, and shutdown
Timeout settings prevent a task from waiting indefinitely when navigation or another operation does not complete. Playwright supports context-level default timeouts and navigation timeouts, while page-level settings take precedence over context defaults. When a timeout appears ineffective, inspect the page for a local override before raising or removing the broader limit. Playwright BrowserContext API
Handle failed navigation, timeouts, and closed contexts where the task is orchestrated: record the failure, decide whether the operation is safe to retry, and avoid treating a browser crash as an ordinary successful completion. On cleanup, close contexts before the browser when graceful closure and artifact flushing matter. Playwright Browser API
Common session-management mistakes
- Sharing a context across unrelated tests: inherited cookies or storage can make a failure depend on which test ran first. Prefer a fresh context for independent tests. Playwright isolation guide
- Clearing only cookies and assuming the session is reset: browser state is broader than one selected category, and cleanup can miss state. Use a fresh context when a clean boundary is important. Playwright BrowserContext API Playwright isolation guide
- Closing the browser before its contexts: explicitly close contexts first when graceful artifact flushing matters. Playwright Browser API
- Disabling timeouts broadly: keep waits bounded and check whether a page-level override is taking precedence over a context default. Playwright BrowserContext API
- Assuming Puppeteer and Playwright have identical defaults: verify behavior against the pinned framework and browser versions rather than transferring assumptions between APIs. Puppeteer BrowserContext API
Or skip the browser setup
If the task is to capture a website screenshot rather than exercise a stateful browser workflow, ScreenshotNeo can return an image or PDF with one GET request. It removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed; and its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemscURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for API details, then sign up for 1,000 free screenshots a month with no card.
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.
