Browser-local capture presets
Save capture settings in the current browser or share them in a URL.
Save and load
Use the save button beside “Load preset” in the capture workspace. A browser can hold at most 12 named presets; names are capped at 40 characters, and saving the same name replaces it. Presets use the versioned local-storage key vipercapture:capture-presets:v1. They do not sync between browsers, accounts, private windows, or cleared site data.
Included settings
Presets include output format, viewport and density, full-page behavior, lazy-load mode, image encoding, non-content waits, extraction mode, cleanup choices, environment profile, locale, timezone, crop coordinates, failure-status policy, and responsive-pack state.
Excluded settings
ViperCapture never puts the source URL/document, base URL, custom headers, custom CSS, element selector, wait selector, or wait text into local presets or share links. Those fields can contain credentials, customer data, internal selectors, or private URLs. Re-enter them for each request.
Share links
The copy button creates a URL-safe, base64url-encoded JSON preset in the preset query parameter. Opening the link applies only the safe fields listed above. It does not run a capture automatically. The decoder rejects oversized values and ignores malformed data. Base64 is encoding, not encryption; inspect a link before sharing it publicly.
API clients
Browser presets are a UI convenience and are not an API resource. For API automation, keep request templates in your own configuration, omit secrets from source control, inject API keys and authorized target headers at runtime, and validate templates against the live OpenAPI schema.