Frequently Asked Questions
Everything you need to know about AtlasX mobile profiles, hardware isolation, team sharing, and automation.
How is AtlasX different from browsers that use JavaScript extensions? +
Standard antidetect extensions hook JavaScript getters via
Object.defineProperty, which anti-bot scanners like CreepJS and Pixelscan immediately flag as prototype tampering. AtlasX isolates hardware identity directly inside the browser engine core so every property is 100% authentic across both the Main Thread and WebWorkers.
Can I emulate iOS 18 and Android 15 mobile profiles on a Windows PC? +
Yes. AtlasX includes 87+ calibrated iOS 18 (iPhone 16/15 Pro Max) and Android 15 (Galaxy S24 Ultra, Pixel 9 Pro XL, Xiaomi 14 Ultra) hardware profiles. Each profile configures the exact Retina viewport, mobile GPU renderer, touch event capabilities, and mobile TLS/HTTP2 handshake.
How does the Desktop App sign-in work? +
Clicking Sign in with Browser inside the AtlasX Desktop App opens your default system browser, verifies your session (via Email/Password or Google OAuth), and securely passes an encrypted token back to the desktop app in one click.
Where are my browser profiles and cookies stored? +
Profile hardware specifications and encrypted session cookies are stored in the AtlasX Cloud Cookie Vault so you can resume your work on any machine or share profiles with team members. Heavy browser cache remains in your local isolated profile directory for instant startup.
Does AtlasX support Playwright, Puppeteer, and Selenium? +
Yes. You can connect Playwright, Puppeteer, or Selenium directly via Chrome DevTools Protocol (`connect_over_cdp`) while maintaining 100% hardware fingerprint isolation and zero automation flags.
How do browser engine updates work? +
Whenever a new stealth engine release is published, the AtlasX Desktop App automatically downloads, verifies the SHA-256 checksum, and updates your local browser engine without requiring you to reinstall the app.