tracebrief.
RUNS IN YOUR BROWSER
How sharing works

HAR → A CLEARER HANDOFF

The useful part
of your network trace.

Find slow requests, HTTP errors, and repeated endpoints.
Share a small report without the original URLs or payloads.

[ 01 / LOCAL BY DESIGN ]

Your capture stays in this tab.
No upload. No account. No API key.

Drop a HAR file here

Or choose a capture from your device. Up to 50 MiB.

or
Processed locally. Nothing is uploaded.Where do I get a HAR?
LESS NOISE. MORE CONTEXT.THREE THINGS TO TAKE AWAY
01

See the shape of a load

A compact request waterfall with timing, response status, and repeated endpoints.

02

Leave the payloads behind

Exports are rebuilt from allowed metadata. Headers, bodies, and original endpoints stay out.

03

Give someone a useful brief

Download Markdown for an issue, HTML for a teammate, or an aliased HAR for inspection.

Before you share a trace.

How do I get a HAR capture?

In your browser’s DevTools, open Network, record the action you want to inspect, then use the HAR export option. Browser labels vary. HAR files can contain credentials and private content, even when the browser offers a sanitized export.

Import a capture you are allowed to inspect. Tracebrief can read HAR 1.2 captures with a log.entries array.

What is safe to share?

Tracebrief rebuilds each export from a limited set of numeric and categorized metadata. Original URLs, headers, cookies, query values, payloads, and unknown custom fields are excluded.

Metadata can still identify activity. Review the result and your organization’s sharing requirements before sending it to a teammate or AI service.

What does the report leave out?

Opaque origin and route aliases preserve grouping without revealing names. Dates are shifted to a fixed base. Exports cannot replay original requests.

It does not diagnose performance causes, inspect encrypted content, or promise universal removal of personal information. Incomplete HAR fields remain unknown.