KitWharfFREEFast & Private Web Apps

How to Analyze & Redact HAR Files Safely (Network Waterfall Guide)

November 16, 20267 min readKitWharf Team
Interactive Online Tool Available

HAR File Analyzer, Network Waterfall & Secret Redactor

Inspect HTTP Archive (.har) network waterfalls, slow TTFB requests, and headers locally—plus 1-click redaction of cookies and Bearer tokens.

Launch Free Tool

When a web app fails intermittently—throwing a 502 Bad Gateway, stalling on an API call, or dropping a CORS preflight—support engineers almost always ask for a HAR (HTTP Archive) file.

Yet most developers and IT teams overlook a critical security risk: a raw .har capture contains your live session cookies, Bearer JWTs, and API keys in plain text.


1. Why You Should Never Upload Raw HAR Files to Cloud Viewers

Every GET and POST recorded in Chrome or Firefox DevTools stores full request and response headers. That routinely includes:

  • Authorization: Bearer ... JWT access tokens
  • Cookie and Set-Cookie session identifiers
  • X-API-Key, X-CSRF-Token, and OAuth access_token query parameters
  • Form payloads containing emails or credentials

Uploading a raw .har to a remote server hands over active authenticated sessions. Using a zero-knowledge, in-browser analyzer keeps every byte inside your local browser RAM.


2. How to Export a HAR File from Browser DevTools

  1. Open DevTools (F12 or Ctrl+Shift+I / Cmd+Option+I) and select the Network tab.
  2. Check Preserve log so redirects and page reloads are captured.
  3. Reproduce the bug or slow page load.
  4. Click the Export HAR download icon in the Network toolbar (or right-click any row and select Save all as HAR with content).

3. Reading the Network Waterfall & Timing Phases

Inside the KitWharf HAR File Analyzer, each request renders a color-coded waterfall bar broken down into HAR 1.2 timing phases:

  • Blocked / DNS / TCP Connect / SSL (Amber): Network handshake overhead. High DNS or SSL times point to cold connections or missing HTTP/2 reuse.
  • Waiting / TTFB (Green): Server think time. A 400ms+ TTFB bar means your backend, database, or upstream microservice is the bottleneck.
  • Content Download (Indigo): Payload transfer duration. Large unminified JS bundles or uncompressed images show up here.

You can filter instantly by XHR/Fetch, 4xx/5xx errors, or sort by Slowest First to pinpoint failing endpoints in seconds.


4. Export a Sanitized -redacted.har Before Sharing

Before attaching a HAR capture to Jira, GitHub Issues, or vendor support:

  1. Drop your .har file into the KitWharf HAR File Analyzer.
  2. Check the Secrets Detected KPI card to see how many entries contain credentials.
  3. Click Export Redacted .har to download a sanitized copy with all sensitive headers, cookies, and token query parameters replaced by [REDACTED].

Need to replay a failing endpoint locally? Click any request and hit cURL to copy a reproducible command—with secrets masked or unmasked at your discretion.

Found this guide helpful? Share it with your team:

Ready to put this into practice?

Launch our free HAR File Analyzer, Network Waterfall & Secret Redactor — instant client-side execution in your browser with zero registration required.

Open Tool