--storage-chrome-profile

CLI: --storage-chrome-profile
REST: CLI only

ValuePATH

Seeds the render with the cookies and localStorage of a signed-in Chrome profile, which ZShot never writes.

Bare --storage-chrome-profile uses the OS default profile and continues if none is found. --storage-chrome-profile=PATH reads that profile directory and fails if it is absent or unreadable. Merges under --storage: the profile is the base, the file wins.

Only the target URL’s registrable domain is seeded, plus the origins --navigator-credential-origin allows. On localhost or an IP address, each port is its own app, so localStorage is seeded only for the exact origin, scheme and port included; cookies, which a browser sends to every port, are seeded for the host.

PATH may be any Chromium-based profile: Chrome, Chromium, Brave, Edge, Arc, Vivaldi or Opera. On macOS the cookie key comes from that browser’s keychain item, such as “Brave Safe Storage”, which prompts once; --storage-chrome-profile-key supplies it instead.

Example

CLI Run locally

zshot -f pipeline.png \
  --storage-chrome-profile \
  https://zshot-cli.com/example_assets/zrm/