HAR file

#How a HAR file works

Each entry in a HAR holds one request and its response. The request part has the method, URL, headers and body. The response part has the status, headers, body and timing. Other tools read the file as plain JSON. Chrome exports HAR files from the Network panel in DevTools. The Chrome DevTools network reference describes the panel's options.

#Why it matters for AI agents

A HAR is raw material for understanding how a page talks to its backend. A developer can find the request that loads search results and rebuild it as a direct call. The same file can also expose secrets, so sanitize it before you share it.

#Wield and HAR file

Wield's recorder captures the network calls of one task in your own browser. On your device, it removes cookies, auth headers, tokens and body values before you review anything. A recipe builder then drafts a recipe from that sanitized trace, and your browser verifies the draft live. Recording and the builder are paid-plan features. See how Wield handles credentials.

#Related terms

• Internal API
• Chrome DevTools Protocol
• Cookies and sessions
• Bearer token

#FAQ

#Does a HAR file contain passwords?

It can. A HAR records request bodies, so a password typed into a login form may appear there. It also records cookies and auth headers, which prove that a session is logged in. Remove those values before you share a file.

#How do I export a HAR from Chrome?

Open DevTools, go to the Network tab, and reload the page or repeat the action you want to capture. Then use the Network panel's option to save the requests as a HAR file. The Chrome reference lists the options.