Guide

Stealth & fingerprinting

Most automation stacks are trivially detectable. Morrow leans on a coherent, persistent fingerprint instead of tricks.

Why stock automation gets caught

Stock headless Chromium leaks navigator.webdriver, a mismatched or missing fingerprint, and a brand-new cookie jar on every run. Detection vendors flag that in milliseconds — the result is CAPTCHAs, blocks, and dead sessions.

A coherent, spoofed fingerprint

Morrow is built on Camoufox, an anti-detection Firefox fork. Each profile is assigned a realistic fingerprint — user agent, platform, screen and viewport, hardware concurrency, canvas/WebGL, audio, font metrics, timezone, and locale — that is internally consistent, with no contradictions between layers. Camoufox applies these at the C++/engine level rather than via detectable JS patches, so navigator.webdriver and the usual automation giveaways are absent.

That fingerprint is persistent

Morrow generates the fingerprint once per profile and pins every value — including the canvas, audio, and font seeds that would otherwise re-randomize on each launch — so the identity is byte-identical across restarts. A returning profile looks like the same real machine coming back, not a new bot every time. Combined with persisted cookies and logins (see Profiles), that is what a genuine returning user looks like.

The practical effect

Profiles pass far more bot-detection checks and hit far fewer CAPTCHAs than stock headless browsers, especially on sites you've already logged into with that profile. Add a residential proxy per profile ("proxy" on create — see Profiles) and the network origin lines up with the identity too.

Timezone & geolocation follow the exit IP

Leave a profile's timezone and locale unset and Morrow derives the browser's timezone, locale, geolocation, and WebRTC IP from the egress IP — through the proxy if one is set — using Camoufox's bundled GeoLite2 database (no external service). A profile on a New York proxy reports America/New_York and US geolocation, with no clock/IP mismatch for detectors to catch. Set a timezone explicitly to override, which disables IP-based geolocation for that profile.

Honest scope

Morrow does not solve CAPTCHAs, and no anti-detection tool is a guarantee against a determined, well-resourced detector. What it does is remove the cheap, obvious tells and present a stable, human-shaped identity — enough to get through the overwhelming majority of routine fingerprint- and reputation-based walls. Use it responsibly and within the terms of the sites you automate.