500
Server errors
The backend failed. The response body often holds the error message.
A HAR file holds the session cookies and tokens of whoever recorded it. Find the request that failed, then strip the secrets before you pass the file on. It never leaves your browser.
The file is read in your browser. Nothing is uploaded, and there’s no share link.
HAR analyzer & sanitizer · read in this browser tab only
No failed, slow or heavy requests in this file.
No requests match these filters.
A HAR file carries session cookies and tokens, and anyone holding it can use them until they expire. Stolen support HAR files were behind the Okta breach in 2023.
Everything ticked is replaced with [redacted] in the copy you download. Untick what you want to keep.
No cookies, tokens or passwords found.
The check looks for common names like token, password or session, and for JWTs. It can’t spot every secret, so skim the copy before you send it.
Your file stays in this browser tab. Ybug never sees it, and closing the tab clears it.
Record the problem with your browser’s developer tools, then export the Network tab. It takes about a minute.
Open the page where the problem happens.
Press F12 (⌘ Cmd+⌥ Option+I on a Mac) and open the Network tab.
Tick Preserve log, reload the page and repeat what went wrong.
Click the Export HAR icon (the down arrow) in the Network toolbar and save the file.
Chrome 130 and newer leave cookies and authorization headers out of this export by default.
Open the page where the problem happens.
Press F12 (⌘ Cmd+⌥ Option+I on a Mac) and open the Network tab.
Tick Persist Logs in the gear menu, reload the page and repeat what went wrong.
Right-click any request and choose Save All As HAR.
Turn on the developer tools: Safari → Settings → Advanced → Show features for web developers.
Open the page, press ⌘ Cmd+⌥ Option+I and open the Network tab.
Tick Preserve Log, reload the page and repeat what went wrong.
Click Export in the Network tab and save the file.
A HAR file holds everything the page sent, cookies and tokens included. Sanitize it above before you email it or attach it to a ticket.
Most “it doesn’t load” bugs show up as one of these.
500
The backend failed. The response body often holds the error message.
401 / 403
The request went out without a valid token or cookie.
(failed)
CORS, ad blockers, DNS and TLS problems end before any status code.
Waiting 4.2 s
A long Waiting (TTFB) time means the server took its time, not the network.
3.4 MB
Oversized images, scripts and JSON responses slow down every page view.
301 → 302 → 200
Every hop adds a round trip, and a loop never finishes loading.
Ybug’s feedback widget records network requests with every bug report, on STARTUP and higher plans. See what it captures.
Try Ybug free for 10 daysInstalls in seconds. No credit card required.