Adobe Launch Audit Tool

Inspect which external libraries Adobe Launch injects into your application

HAR Analyzer Call Chain Graph Cookie Audit
Cookie headers require extra steps (Chrome / Edge 130+)
From Chromium version 130 onward, browsers exclude Set-Cookie and Cookie headers from HAR exports by default for security reasons. You must explicitly enable sensitive data capture before exporting, otherwise the Cookie Audit tab will show no results.
Step 1 Enable sensitive data in DevTools Settings
  1. Open DevTools — press F12 or right-click the page → Inspect
  2. Open Settings:
    • Chrome — click the gear icon (top-right of DevTools)
    • Edge — click the three-dots icon → Settings
  3. In the Preferences tab, scroll to the Network section
  4. Check "Allow to generate HAR with sensitive data"
  5. Close the Settings panel and return to the Network tab
Step 2 Record traffic & export
  1. Make sure the Record button is active (red). Click it if it's grey.
  2. Tick Preserve log so requests survive page navigation
  3. Click the Clear button to remove any existing logs
  4. Hard-reload the page: Ctrl+Shift+R / Cmd+Shift+R
  5. Wait for the page to fully load and all requests to complete
  6. Export — long-press (or right-click) the Export HAR button and select "Export HAR (with sensitive data)"
Step 3 Load into this tool
  1. Drop the exported .har file onto the upload zone below
  2. Or click Browse HAR File to pick it from disk
HAR files contain sensitive data including cookies, auth tokens and request payloads. This tool processes everything locally in your browser — nothing is uploaded to any server. Do not share HAR files with untrusted parties.

Drop your HAR file here

Or click to browse — exported from Chrome DevTools Network tab

The HAR file contains all network requests including initiator chain metadata — this is how we trace Adobe Launch injection.