What are the important limits?

HAR files may contain secrets in their original source. Headers and bodies are not included in reports, but paths can still be sensitive. Query display is opt-in. Up to 20,000 requests; table shows the first 500 matches. Byte sizes are recorded estimates, not exact wire traffic.

Where is my information stored?

Processing happens in your browser. These workspaces do not upload your inputs or send reports to a server. Session data is not automatically saved; download a project or report before closing. Keep sensitive exports private.

HAR File Analyzer & Request Timeline

Inspect browser request timings, failed requests and byte sizes with a local waterfall and filtered reports.

Local Developer Workbench

HAR · Request Timeline

Files are processed in this browser. No requests are sent to your endpoints.

HAR files can contain credentials, cookies, personal URLs and response bodies. This view does not display headers or bodies; query strings are hidden by default. The original source below still contains the full file.

HAR Source

Requests

Failed

Recorded Bytes

179.7 KB

Timeline

0.38 s

Failures onlyInclude URL queries in view/export

Request	Status	Duration	Bytes	Timeline
GEThttps://example.com/	200	120.0 ms	24,000
GEThttps://example.com/app.js	200	300.0 ms	160,000

Table shows the first 500 matching requests; exports include all matching rows. Recorded byte sizes may omit overhead or use decoded size where transfer size was unavailable. No requests are replayed.

Loading Tool…

What Is the HAR File Analyzer & Request Timeline?

A local HTTP Archive inspection workspace. View request count, failure count, recorded bytes and overall timeline span; filter URLs, isolate failed requests, and sort by time, duration or size. This analyzes a recording rather than pinging a host or testing current network speed.

How It Works

Export a HAR from browser developer tools, open it here, then inspect the timeline. URL queries and fragments are hidden in results by default. Export matching request metadata as CSV or PDF. The included example contains two fictional requests to example.com.

When to Use It

Use when inspecting local developer data or preparing configuration that needs review before production.

Frequently Asked Questions

How do I get started?: Export a HAR from browser developer tools, open it here, then inspect the timeline. URL queries and fragments are hidden in results by default. Export matching request metadata as CSV or PDF. The included example contains two fictional requests to example.com.
What are the important limits?: HAR files may contain secrets in their original source. Headers and bodies are not included in reports, but paths can still be sensitive. Query display is opt-in. Up to 20,000 requests; table shows the first 500 matches. Byte sizes are recorded estimates, not exact wire traffic.
Where is my information stored?: Processing happens in your browser. These workspaces do not upload your inputs or send reports to a server. Session data is not automatically saved; download a project or report before closing. Keep sensitive exports private.

Found an issue? Send Feedback. See our data sources and update policy for tools that depend on changing information.