PostHog vs Umami: what their users struggle with

Not a verdict and not a star rating: the problems users of PostHog and Umami describe in public, side by side, each one linked to its source (as of 2026-10-15).

Get started free with your email Open PostHog on Friction

Every count in this table is of open reports in the recent window (PostHog since 2023-10, Umami since 2023-10); older and fixed reports are not counted. The counts measure how much public discussion exists for each product, not which is better: a popular tool collects more reports.

Problems mostly raised about PostHog

• Marketing site does not make clear what PostHog actually does · Setup & onboarding · Annoyance
• PostHog configuration too fiddly to tune even with AI assistance · Customization · Blocks work
• Cannot remove test events, requiring manual SQL filters in every query · Data export & migration · Blocks work
• Session Replay search and filters feel unreliable · UI & usability · Annoyance
• S3 warehouse destinations fail with IAM-role authentication on Cloud US · Integrations · Blocks work

Problems mostly raised about Umami

• Session duration counts single long page views as bounces · Reporting & analytics · Annoyance
• Annotations appear one day before the selected date · Reporting & analytics · Blocks work
• Website listing omits team-owned websites · Integrations · Blocks work
• Team and user management is weaker than in Matomo · Collaboration · Annoyance
• v3 removed the all-sites dashboard overview · UI & usability · Annoyance

Go further

Open PostHog and Umami in the compare tool to filter by area and severity, PostHog alternatives, Umami alternatives, or the state of product analytics.

How the data is built. A theme is a group of reports about the same problem; unique means not matched to a theme on the other product.