All The Validators logoAll The Validators

format validator

HAR Validator & Network Log Checker

Validate HAR files from Chrome, Edge, Firefox, Safari, and proxy tools locally before you share network captures.

Results

Paste input and validate locally.
Status
Ready when you validate.
Details
Ready when you validate.
Entries
Ready when you validate.
Pages
Ready when you validate.

Rules & checks

Requires a top-level log object with a non-empty entries array.

Each entry must include request.url as an absolute http(s) URL and response.status as a number.

Counts HAR entries and pages so you can spot empty, truncated, or wrong-tab exports.

Runs fully client-side; the HAR content stays in your browser session.

When to use it

  • Preflight Chrome, Edge, Firefox, or Safari DevTools HAR exports before attaching them to bug reports.
  • Check API debugging captures for absolute URLs and numeric response statuses before sharing with engineers.
  • Validate customer-provided HAR uploads in support workflows without sending sensitive traces to a server.
  • Confirm performance-audit captures are not empty or truncated before importing them into analysis tools.
  • Review proxy and test-run HAR files generated by Playwright, Cypress, Charles, Fiddler, or browser automation.

Common errors

  • Missing top-level log object after pasting only the entries array.
  • No entries found because the wrong tab/window was captured or the export was truncated.
  • Entries without request.url from custom proxy output or redacted captures.
  • Relative URLs instead of absolute https:// or http:// request URLs.
  • Response status stored as a string instead of a number.

Tips

  • Redact cookies, authorization headers, session IDs, query tokens, and POST bodies before sharing a HAR externally.
  • Capture the exact browser tab and reproduce the issue before exporting so the entries array includes the failed requests.
  • If the HAR fails JSON parsing, run it through JSON Validator or JSON Formatter before checking HAR-specific structure.
  • Use JSON Diff to compare two captures when one environment works and another fails.
  • Pair HAR validation with JSON Schema Validator when a downstream tool requires a stricter internal HAR contract.

Examples

Valid browser HAR export

  • { "log": { "version": "1.2", "entries": [ { "request": { "url": "https://example.com/api/orders" }, "response": { "status": 200 } } ] } }
  • Returns Valid HAR with one entry and zero pages if the optional pages array is not present.

Missing request URL

  • An entry with request but no request.url is flagged before the file reaches a support ticket or debugging workflow.

Relative URL from a custom exporter

  • request.url = /api/users is flagged because HAR analysis tools and replay/debugging workflows need absolute URLs.

Broken JSON around a copied capture

  • If copying from DevTools or a ticket mangles braces or quotes, the validator surfaces the JSON parse error first. Use JSON Formatter next to inspect the structure.

FAQs

Is my HAR file uploaded?
No. The HAR is parsed locally in your browser. The app does not upload, store, or log your network capture.
What does this HAR validator check?
It checks that the file is valid JSON, has a top-level log object, includes at least one entry, and that every entry has an absolute request URL plus a numeric response status.
Does it inspect cookies, headers, request bodies, or timing data?
No. This page focuses on safe structural validation. Always redact sensitive headers, cookies, tokens, and payloads before sending a HAR to another person or system.
Why does my browser-exported HAR fail?
Common causes are copying only part of the file, exporting the wrong tab, truncating a large capture, redacting request.url entirely, or converting numeric response statuses into strings.
Can I validate HAR files from automated tests?
Yes. HAR files generated by Playwright, Cypress plugins, proxies, and browser automation can be pasted here as long as they follow the expected HTTP Archive JSON shape.

Related validators

format

JSON Validator & Syntax Checker

Check JSON syntax, catch trailing commas and quote errors, and keep every payload local to your browser.

format

JSON Formatter & Prettifier

Format minified JSON into readable two-space indentation for API debugging, reviews, and docs—without uploading it.

format

JSON Minifier

Minify JSON locally into compact, whitespace-free output for curl commands, environment variables, webhooks, signed requests, and config values.

format

JSON Diff Checker

Compare two JSON payloads locally to spot added, removed, or changed fields before API, webhook, or config changes ship.

format

JSON Schema Validator

Validate JSON Schema contracts with AJV, then test sample request or response JSON locally before you ship an API change.

format

JSONL Validator & NDJSON Checker

Validate JSON Lines and NDJSON records locally with line-precise parsing errors and basic key consistency checks.

web

URL Validator & HTTP Link Parser

Validate HTTP and HTTPS URLs locally, parse host/path, and catch malformed links before publishing, importing, or sending them to APIs.

Structure validation only; this does not run a performance audit, replay requests, verify response bodies, or judge whether the network behavior is correct.