Angular Monitor
A Chrome DevTools panel that profiles Angular applications the way Angular actually works: which component was checked, which signal wrote, which subscription is still open, and which click caused all three. Seventeen tabs covering change detection, signals, RxJS, rendering, network, memory and the supply chain — plus an Overhead tab that reports what the profiler itself costs. No account, no telemetry, and no backend.
Everything, free
Angular Monitor is free to use. There is no premium tier, no licence key and nothing to buy — the whole surface below is yours.
- Causal chain for every click and keystroke
- Per-component change detection, renders and total time
- Change-detection mode, cycles and durations
- Signal, computed and effect graphs with write counts
- RxJS subscriptions grouped by call site, with leak detection
- Pick a component on the page and read its state
- Router config, lazy routes and the active URL
- Change detection, long tasks, network and events on one track
- HTTP calls with status, size, initiator and timing
- Web Vitals — FPS, LCP, INP, CLS, FCP, TTFB and long tasks
- Heap size and trend estimates
- Loaded package versions with opt-in advisory lookups
- Automated findings — jank, duplicate requests, leaks
- What the profiler itself is costing you
- Four monitoring levels, from idle to sampling profiler
- No account, no telemetry, no backend
Questions
- Is Angular Monitor free?
- Yes — free to use, with no account, no telemetry and no backend. The source is not currently published.
- Which Angular versions can it profile?
- Angular 17 through 22. The panel reads Angular’s own debug APIs, which is what bounds the supported range.
- Does it send my application data anywhere?
- No. Everything is measured and displayed locally in the DevTools panel; nothing leaves the browser.
- Does the profiler distort what it measures?
- Profiling always costs something, so the panel includes an Overhead tab that reports what the profiler itself is costing — measured, not assumed.