HARScope — HAR Viewer, Analyzer & Sanitizer

Support asked you to "send a HAR file"? Before you do, open it here. HARScope is a free HAR file viewer and HAR analyzer for Chrome. A HAR file is a full recording of what your browser sent and received — and it routinely contains session cookies, Authorization headers, API keys and passwords typed into forms. Most online HAR viewers are websites you have to upload that file to. HARScope reads it right inside Chrome, on your own computer: it has no permissions, makes no network requests, and there is nothing to upload and nowhere for the file to go. OPEN AND READ ANY HAR FILE — OFFLINE • Open a HAR file by dropping it on the page (or "Open HAR file…") — HAR 1.2 exported from Chrome, Edge, Firefox or Safari • Request table with status, method, type, size and time — sort any column; virtualized, so thousands of requests stay fast • Waterfall that shows what loaded when, and what was slow • Filter by URL, domain, type, method and status code — or search inside headers and bodies too • Full detail for every request: headers, query string, payload, response body (JSON formatted, images previewed), timing bar • Copy a request as cURL, copy its URL or its response; ↑/↓ to walk the list HAR ANALYZER — FIND THE PROBLEM IN ONE CLICK (NEW IN 1.1) • Failed requests — 4xx, 5xx and requests that never got a status, worst first • Slow requests — everything that took a second or more, slowest first • Heavy responses — 1 MB and up, largest first • Redirects — the whole redirect chain, hop by hop (redirect loops are marked) Each insight is a filter: click it and the table shows exactly those requests. "Copy report" puts a short summary of the problems on your clipboard for a support ticket — with secrets already removed from the URLs. HAR SANITIZER — CLEAN A HAR BEFORE YOU SHARE IT (NEW IN 1.1) HARScope tells you what secrets the file contains — cookies, auth headers, tokens in URLs and bodies — and saves a sanitized copy with their values replaced by REDACTED: • Cookies (Cookie and Set-Cookie headers and cookie lists) • Authorization, token, session and API-key headers — and JWTs under any header name • Tokens, keys, codes and signatures in URLs: query strings, #fragments, redirect targets, Referer, page addresses • Request bodies and WebSocket messages — form fields, passwords, JSON • Response bodies (optional — keep them if support needs to see what the server returned) • Tokens inside the bodies you keep — access_token, refresh_token, JWTs, API keys Cookie, header and parameter names stay, so the person you send it to still sees what was sent. Your original file is never modified. PRIVATE BY DESIGN • No permissions at all — HARScope cannot read the websites you visit • No network requests: the viewer page's security policy (connect-src 'none', default-src 'none') blocks them • No account, no analytics, no tracking, no ads • The file is read in memory and forgotten when you close the tab WHAT IS A HAR FILE, AND HOW TO CREATE ONE HAR (HTTP Archive) is the JSON log of network requests that browser DevTools export. To capture one in Chrome or Edge: open DevTools (F12) → Network → reload the page and reproduce the problem → export the HAR. Then drop the file into HARScope. Step-by-step for Chrome, Edge, Firefox and Safari: bilingoplus.com/harscope/how-to-create-a-har-file GOOD TO KNOW • Sanitizing matches names (cookie, authorization, token, key, session, password, signature…) and unmistakable token shapes such as JWTs. A secret under an unusual name can slip through, so skim the file before you send it. • Very large bodies are shown up to 2 MB each in the detail panel. • No Chrome at hand? The same viewer runs on the web, nothing uploaded: bilingoplus.com/harscope/analyzer HARScope is free, from BiLingoPlus LLC, a small independent software studio. Questions: info@bilingoplus.com