Install for your QA team
Varypilot QA is an unpacked extension for Chrome 120 or later. It is distributed directly; this download is not a Chrome Web Store listing.
- Download https://varypilot.com/downloads/varypilot-qa-devtools.zip and extract it to a permanent folder.
- Open chrome://extensions, enable Developer mode, choose Load unpacked and select the extracted folder containing manifest.json.
- Open your product in Chrome, then open DevTools and choose Varypilot QA. If DevTools was already open during installation, close and reopen it.
Connect your browser integration
The inspected page must initialize the current Varypilot browser SDK; no extra SDK option is required. The panel reads that page's configuration, environment, assignment and consent state. It does not need your Varypilot password, private server credential or an account connection.
Only variations in the page's available published configuration can be previewed. The extension does not publish drafts, edit experiment settings or change other visitors' assignments.
Preview without recording QA traffic
Choose Enable QA & reload before testing. Varypilot analytics are suppressed for this tab. Select a variation to apply a local override and reload the page. Overrides stay in this tab's session storage for the current site and are scoped to the project and environment.
Reset overrides returns to normal assignment while keeping QA suppression enabled. Use Exit QA & reload when finished: overrides are cleared, the page is rebuilt without QA state, and recording can resume only if the site's analytics consent is granted.
Closing DevTools alone does not exit QA. Requests already in flight before QA was enabled cannot be recalled. Other analytics tools on the website are unaffected.
Inspect the selected element
Use Chrome's element picker or select a node in Elements. The Varypilot sidebar and Selected element view show its CSS selector, tag and dimensions. Reveal selection in Elements returns you to the selected node.
Element inspection is read-only. It does not change the page or read text, form values or HTML. The extension inspects the top-level page; elements inside embedded frames may be unavailable.
Share a focused QA handoff
Diagnostics shows recent SDK request status observed while the panel is open. Export diagnostics saves configuration metadata, consent and QA state, plus request status and timing. It excludes visitor IDs, credentials, event payloads, page URLs and element selectors.
Check the exported file before sharing: environment and experiment keys can still identify internal work. Exporting downloads a local file; it does not send a support request.
Unavailable or empty states
If no SDK is detected, update the browser SDK and check that the inspected product initializes it. Server-only integrations cannot expose browser assignment through this panel. Use a normal website tab; Chrome's own restricted pages do not support inspection through the extension.
An empty experiment list means no published experiments are available to this SDK client. Check the project, environment, domain, subscription and delivery state. If session storage is blocked, enable it for this site before entering QA; do not assume an override was retained after reload.