HAR Viewer opens HTTP Archive files in your browser and lists each request with method, URL, status, and time so you can triage captures without uploading them.
What HAR Viewer does
Parses HAR JSON client-side into a readable entry table.
- File picker for .har or JSON
- Method, URL, status, time columns
- Works with standard log.entries layout
- Escaped table output
- No server upload
Who HAR Viewer is for
- Front-end developers debugging waterfalls
- QA exporting Chrome HAR files
- Security reviewers inspecting captured traffic locally
- Support teams reading customer HAR attachments
How to use HAR Viewer
1. Export a HAR from DevTools.
2. Choose the file in HAR Viewer.
3. Click Parse.
4. Scan the table for failing statuses or slow times.
Features
- Client parse only
- Large list friendly table markup
- Rounded millisecond times when present
- Clear invalid JSON errors
Examples
- Chrome Save all as HAR with content triage.
- Find 500 responses quickly in a long capture.
- Compare request times after a performance tweak.
Tips and limits
- HAR files can contain cookies and tokens; handle them like secrets.
- Very large captures may freeze a tab briefly while parsing.
- Response bodies are not rendered in this list view.
- Time uses entry.time when available.
Related tools
- cURL Builder to rebuild a request string.
- WebSocket Tester for live socket checks.
FAQ
Is the HAR uploaded?
No. Parsing happens entirely in your browser.
Why are tokens visible?
HARs often include query secrets; the table shows URLs as stored in the file.
Does it show response bodies?
Not in this viewer; it focuses on method, URL, status, and time.
Extra notes
HAR Viewer runs entirely in your browser so drafts and secrets never need to leave your device for processing. Keep a backup of long outputs in your own notes if you rely on them for production servers or live events. Accessibility friendly labels come from the module UI strings, and the layout follows the shared BeeForge .bf-tool shell for consistent spacing and buttons.
Support for developers, marketers, and everyday users is the same client-side model: open the page, configure options, copy or download, then paste into your workflow. BeeForge related links on the tool page point to companion utilities so you can move between related generators without hunting the hub.
When you share results with a teammate, paste into a ticket or gist rather than screenshotting alone, so the text remains searchable. If a browser privacy mode blocks clipboard helpers, select the output manually. Local processing also means the tool works offline after the page and scripts have loaded once.
Validate generated configs or hashes in a staging environment before production use. Prefer regenerating secrets after any accidental paste into chat. For teaching sessions, walk through one sample input end to end so students see how live updates and copy buttons behave together.
Bookmark the tool page if you use it weekly. Small habit changes like consistent naming and clear file downloads save more time than hunting another converter. Prefer regenerating after you change inputs rather than editing outputs by hand when the source fields still exist.