PostHog Debugger panel reference

Use this reference after getting started with a clean capture. If a view is empty or evidence is missing, follow the PostHog events not showing checklist and review the extension's detection limits.

Config

Config summarizes the PostHog SDK state the inspected page exposes: loaded state, SDK version, token and host information, capture settings, consent or opt-out state, identity, and configuration warnings. It is the fastest way to verify that the page initialized PostHog as expected. If you connect a PostHog Cloud account, Config also matches observed public tokens to accessible projects and lets you choose a project when an exact match is ambiguous or unavailable.

Events

Events is the live decoded event stream. Search and filter by event type, frame, delivery status, or validation issues; then select an event to inspect its properties, $ properties, person updates, groups, warnings, and raw payload. For a connected, selected project, read-only event and property definitions and exact-event-UUID-correlated ingestion warnings add project context. Capture controls, clear, and export are available from the shared toolbar.

Network

Network lists observed PostHog-shaped HTTP requests with their URL, status, size, and timing. Use it to distinguish an event that was created from a request that was delivered. Blocked, failed, and non-2xx requests are surfaced so ad blockers, bad tokens, and endpoint problems are easier to isolate.

Flags & Session

Flags & Session shows the current posthog-js snapshot when the page exposes it, including feature flags and payloads, identity and session details, replay state, and relevant configuration. A connected, selected project adds bounded read-only flag and experiment context for observed keys, plus a replay-existence check for a valid observed session UUID. It never downloads replay contents. Use Refresh to read the state again; the panel also refreshes periodically. Flag responses observed on the network can provide limited fallback information when a live SDK snapshot is unavailable.

Web Scripts

Web Scripts shows loaded, loading, failed, delivered, or unavailable status for scripts in each observed frame, with a compact list of sanitized runtime IDs. When a selected project is connected, matching scripts can also show safe names, descriptions, enabled state, filter and template summaries, update time, and a PostHog link. The extension does not read script source or arbitrary configuration bodies.

Identity

Identity shows the current distinct ID, device ID, session ID, groups, and identified state. Its timeline records observed identify, alias, group, and reset activity so you can spot unexpected identity changes while reproducing a flow.

Autocapture

Autocapture is a page-level preview for checking what the SDK would produce for an interaction. It is available only while the extension can communicate with the inspected page, and it stops when you leave the view or DevTools context becomes unavailable.

Lint

Lint compares captured events with a local tracking plan, reporting naming-style drift and missing required properties. Definitions from a connected, selected project can also reveal declared property type mismatches; the local plan remains available without a connection. This view is controlled by the first-party analytics-linting-engine feature flag. When the flag is unavailable or disabled, normal capture and inspection continue but linting is not shown.

Compare these dedicated views with browser Network tools and the official PostHog Toolbar in the PostHog debugging tools guide. For installation, source, privacy, and release-history links, return to the PostHog Debugger product page.