---
title: "How to Inspect HAR Files Safely - Blobster Guide"
description: "Review HAR requests, headers, cookies, bodies and timing locally. Learn how to minimise and redact a HAR before sharing it for support."
canonical: "https://www.mochavi.com/blobster/guides/inspect-har-files-safely"
markdown_mirror: "https://www.mochavi.com/blobster/guides/inspect-har-files-safely.md"
language: "en"
generated_from: "prerendered HTML"
---

> Canonical HTML: [https://www.mochavi.com/blobster/guides/inspect-har-files-safely](https://www.mochavi.com/blobster/guides/inspect-har-files-safely)
>
> This machine-readable Markdown mirror is generated from the canonical page during the Mochavi production build.

[Blobster](https://www.mochavi.com/blobster) / [Guides](https://www.mochavi.com/blobster/guides)

HAR guide

# Inspect a HAR before you send it.

HAR captures are excellent debugging evidence, but they can also carry headers, cookies, URLs, request bodies and customer context. Review and reduce them locally first.

Published 28 July 2026 7 minute read By Mochavi

[Install Blobster](https://chromewebstore.google.com/detail/blobster/epddolhfilamhbnmgglenceabjbbeeho) [Read as Markdown](https://www.mochavi.com/blobster/guides/inspect-har-files-safely.md)

Short answer

Capture the smallest useful window, inspect the HAR locally, remove unrelated requests and copy a redacted request or excerpt whenever the full archive is unnecessary.

## Key points

-   A HAR may contain sensitive data even when it was created only for performance debugging.
-   Browser export options reduce some fields, but they do not replace a review.
-   Most support questions need one request or a short sequence, not the whole session.

## What a HAR can contain

The HTTP Archive format records network activity. Depending on the browser, export option and application, it can include request and response headers, cookies, query parameters, post data, response bodies, internal URLs and timing information.

Chrome DevTools distinguishes a sanitised export from an export that includes sensitive data. That is useful, but “sanitised” is not the same as “safe for every recipient”. Application identifiers, URL paths and response bodies may still reveal more than the support case requires.

## Capture less before redacting more

Start a fresh capture immediately before reproducing the problem and stop it as soon as the relevant request completes. A smaller archive is easier to understand and creates less accidental exposure.

If the issue can be demonstrated with one failed request and its preceding authentication or redirect step, share that sequence instead of several minutes of unrelated browsing.

-   Close unrelated tabs and clear the network log.
-   Reproduce one scenario with test data where possible.
-   Stop recording immediately after the failure.
-   Inspect domains, request paths, headers, cookies and bodies.
-   Remove requests that do not contribute to the explanation.

## Review the evidence locally

A request-list view makes the archive easier to scan than raw JSON. Filter by method, domain, status or a recognisable path, then inspect the selected entry in detail.

Look for authorization values, session cookies, signed URLs, personal data, request payloads, response bodies and internal infrastructure names. Query parameters deserve the same attention as headers.

## Prefer an excerpt when it answers the question

A support engineer may need the method, URL shape, status, timing and a few response fields. They often do not need the full cookie jar or every response body in the session.

Blobster opens HAR files locally, keeps the tree and raw document available, and can copy a redacted HAR, request JSON, response excerpt or cURL representation. Automatic redaction is a starting point; review the copied output before sending it.

## Sources

-   [Chrome DevTools network reference: save all requests as HAR](https://developer.chrome.com/docs/devtools/network/reference#save-as-har)
-   [Blobster local HAR viewer](https://www.mochavi.com/blobster/local-har-viewer)

Related

[Local HAR viewer→](https://www.mochavi.com/blobster/local-har-viewer)[Keep production JSON local→](https://www.mochavi.com/blobster/guides/keep-production-json-local)

Machine-readable

[Markdown version→](https://www.mochavi.com/blobster/guides/inspect-har-files-safely.md) [Blobster RSS feed→](https://www.mochavi.com/blobster/feed.xml)

Local-first workbench

## Inspect the data. Keep the document local.

Open JSON, logs, tokens, configs and tables in Blobster without adding an account, telemetry or a public paste URL.

[Install from Chrome Web Store](https://chromewebstore.google.com/detail/blobster/epddolhfilamhbnmgglenceabjbbeeho)