Debug Capture

Every Glitch report automatically includes a full set of debug data collected from the page. No configuration needed.

What’s captured

Console

All console output — log, warn, error, info, debug — with stack traces and timestamps. Circular references and BigInt values are handled safely.

Network

Every fetch and XMLHttpRequest request, including URL, method, status, request/response headers, and body (up to 1 MB for text-based content types). WebSocket connections and messages are also captured (up to 2 KB per message).

User actions

Clicks, form inputs (passwords automatically masked), scrolls, and navigation events (pushState, replaceState, popstate).

Core Web Vitals

• LCP — Largest Contentful Paint
• CLS — Cumulative Layout Shift
• INP — Interaction to Next Paint
• FCP — First Contentful Paint
• TTFB — Time to First Byte + navigation timing breakdown

Long tasks

Any JavaScript task longer than 50ms, with attribution.

Storage snapshot

localStorage, sessionStorage, and cookies — captured on demand at report time (up to 50 keys, 500 characters per value).

Environment

Browser version, OS, viewport dimensions, device pixel ratio, available memory, CPU cores, connection type, timezone, locale, and more.

Privacy and redaction

Glitch automatically scrubs the following from all captured data before it appears in any report:

• Authorization headers (Bearer, Basic, etc.)
• JWT tokens
• API keys (AWS, common patterns)
• PEM certificate data

Redacted values are replaced with [glitch-redacted].

Passwords in form fields are masked as [password] in the user actions log.