Skip to content
Go to file


Failed to load latest commit information.
Latest commit message
Commit time
May 23, 2020


Snoop is the open source WPF spying utility created by Pete Blois when he was employed at Microsoft.

It allows you to spy/browse the visual tree of a running application (without the need for a debugger) and change properties, view triggers, set breakpoints on property changes and many more things.

Build status for master branch Build status for develop branch chocolatey version chocolatey download count


  • Join the chat at
  • Twitter

Where can i download Snoop?/How can i install Snoop?

  • chocolatey for stable and some preview versions
  • github releases for stable versions
  • appveyor for the latest preview versions (built on every code change)
  • Please note that you need at least .NET Framework 4.0 to run Snoop


3.0.0 (preview)

You can read the changelog for details on what changed in this version. Please note that this version is not yet finished.


  • Support for .NET Core (3.0, 3.1 and 5.0) (including self contained and single file applications)
  • Rewritten injector code
  • You no longer have to have installed any Microsoft Visual C++ Redistributable(s)
  • Snooping disabled controls when holding CTRL + SHIFT works now
  • Snoop now filters uncommon properties by default
  • Snoop is now able to show MergedDictionaries from ResourceDictionary
  • Snoop now has two tracking modes.
    • Holding CTRL tries to skip template parts
    • Holding CTRL + SHIFT does not skip template parts
  • Drastically improved performance of AppChooser.Refresh() (thanks @mikel785)
  • Usability improvements for process dropdown (thanks @mikel785)
  • Support for displaying the logical tree and the tree of WPF automation peers
  • Ability to inspect Popup without opening it
  • Snoop.exe and the inject laucnher now support commandline args
  • Global hotkey support (just start snoop, focus a WPF application and hit CTRL + WIN + ALT + F12)

Known issues:

  • Trying to snoop a trimmed single file application might not work as trimming might have removed things Snoop relies on


You can read the changelog for details on what changed in this version.


  • Support for multiple app domains
  • Auto elevation to enable spying of elevated processes without running Snoop as administrator
  • Persistent settings for various settings
  • Improved error dialog and issue reporting
  • Rewritten window finder


Was released on September 19th, 2018. In this version we finally got rid of support for snooping WPF 3.5 applications. This allowed us to move the Snoop projects forward to Visual Studio 2017 which should make it much easier to work with Snoop's source code.


Was released on July 27th, 2018. The big addition in this version was the inclusion of the triggers tab which was a useful feature of another WPF spying utility called WPF Inspector (written by Christan Moser). It was ported to Snoop by Bastian Schmidt.

Documentation on how to use Snoop

Unfortunately there isn't any exhaustive documentation on how to use Snoop and there are plenty of hidden features. If someone is willing to work on this, please let me know. On the bright side, it is a pretty easy utility to use and learn. I have made three videos which should get most people quick started.

Here are the links to the current Snoop Tips & Tricks:

Why can't I snoop .NET 3.5 applications?

Well, you can! You will just need to use Snoop 2.9.0 and earlier, in order to do so. As part of the process of moving to Visual Studio 2019, we have dropped support for .NET 3.5 applications.

How do i build Snoop?

Just open Snoop.sln with Visual Studio 2019 (16.7 or later) and build it. Please note that you need the Visual Studio 2019 C++ payload and in case you are using a later version you also need the VC++ 142 payload.


  • Visual Studio 2019 16.7 (including C++ payload)
  • .NET Core SDK 3.1.400


Over time contributions have been added by several people, most notably:

You can’t perform that action at this time.