Validate your PostHog setup
Check SDK status, destination, consent, identity, and capture settings at a glance.
Debug PostHog in Chrome and Firefox DevTools
PostHog Debugger is an unofficial browser extension that adds a PostHog panel to Chrome and Firefox DevTools. It inspects supported events, SDK configuration, identity, feature flags, replay, and network delivery locally while you test—without requiring a PostHog login.
Compare debugging workflows
Choose the right PostHog debugging view
Browser Network tools, the official PostHog Toolbar, and PostHog Debugger answer different questions. Use them together when a problem crosses the page, SDK, and delivery path.
| Compare | Browser Network toolsThe browser's general-purpose request and response inspector. | Official PostHog ToolbarPostHog's authenticated overlay for product data and workflows. | PostHog DebuggerAn unofficial, local DevTools panel focused on PostHog diagnostics. |
|---|---|---|---|
| Login required | No. | Yes. Launch it with access to a PostHog project and an authorized site. | No PostHog login. |
| Decoded payloads | Shows raw request bodies; decoding batches and encoded payloads is manual. | Its event debugger shows captured events, properties, and copyable event JSON. | Decodes supported JSON, batches, form data, base64, and gzip into an event view. |
| SDK configuration and identity | Limited to evidence visible in requests, browser storage, or console inspection. | Focused on actions, heatmaps, flags, and event debugging rather than a dedicated SDK-state view. | Dedicated Config and Identity views when the page exposes a compatible SDK, plus partial traffic-derived evidence. |
| Network diagnostics | The most complete general view of URLs, headers, timing, initiators, and responses. | Event-centric; it is not a request-delivery diagnostic view. | Correlates PostHog-shaped events and requests, highlighting status, size, timing, blocking, and non-2xx delivery. |
| Best use case | Low-level browser or transport diagnosis across any request. | Official actions, heatmaps, feature-flag overrides, and event inspection on an authorized site. | Local, no-login PostHog diagnosis across payloads, SDK state, identity, flags, replay, and delivery. |
Inspect every event as it fires
Review payloads, properties, and validation warnings in real time.
Find delivery issues faster
Match events to network requests, spot failures, and export JSON or HAR for support.
Debug flags and session replay
Check active flags, payloads, overrides, session IDs, and replay status.
Follow identity changes
See distinct and device IDs, groups, and identify, alias, or reset activity.
Preview autocapture safely
Inspect the predicted event and properties without sending an autocapture event.
Frequently asked questions
PostHog Debugger FAQ
Is PostHog Debugger an official PostHog product?
No. PostHog Debugger is an independent, unofficial project. It is not affiliated with, endorsed by, or sponsored by PostHog.
Do I need a PostHog login?
No. The extension observes the inspected page and its PostHog-shaped browser traffic without authenticating to PostHog. It cannot prove which private project owns a token or inspect private project settings. Read the detection limits.
Does inspected data leave my browser?
PostHog Debugger processes inspected event payloads, SDK state, identities, flags, and request evidence locally in memory. Separate cookieless usage analytics is limited to allowlisted product-interaction categories and excludes inspected URLs, event names, properties, payloads, identities, and flag keys. Read the privacy policy.
Which browsers are supported?
PostHog Debugger supports Chrome 111+ and compatible Chromium desktop browsers, plus Firefox 140+ on desktop. It is a DevTools extension, not a mobile browser extension. Chrome Web Store. Firefox Add-ons.
Does it work with reverse proxies and self-hosted PostHog?
It recognizes common PostHog endpoint shapes across Cloud, reverse-proxied, and self-hosted setups. A custom path rewrite can remain unclassified even when the request succeeds, and the extension cannot inspect proxy logs, server health, queues, or storage. Review supported endpoint shapes.
Why is PostHog data missing from the panel?
Open DevTools and the PostHog panel before reloading the page, then confirm capture is not paused and filters are clear. Missing data can also come from consent, blockers, restricted pages or frames, an unreadable SDK instance, unsupported encoding, or a custom endpoint shape. Follow the events-not-showing checklist.
Documentation and downloads
Explore PostHog Debugger
DocumentationInstall the extension, capture a clean session, and learn each DevTools panel.Open resourceEvents not showing checklistTrace missing browser events from SDK initialization through delivery and project-side checks.Open resourcePostHog debugging toolsCompare browser Network tools, the official PostHog Toolbar, and PostHog Debugger.Open resourcePanel referenceLearn what Config, Events, Network, Flags & Session, Identity, Autocapture, and Lint show.Open resourceDetection limitsUnderstand supported endpoint shapes, payload decoding, browser restrictions, and missing evidence.Open resourcePrivacy informationSee exactly what the extension inspects, keeps in memory, stores, and measures.Open resourceGitHub repositoryReview the source, report a sanitized issue, or follow development.Open resourceComplete changelogRead the canonical release history and shipped behavior for every version.Open resourceChrome Web StoreInstall the current Chrome and Chromium desktop build.Open resourceFirefox Add-onsInstall the signed Firefox desktop build.Open resource
Install PostHog Debugger
Inspect PostHog configuration, events, identities, and network delivery in DevTools while you test a flow