VolumeTouch: control system volume with the mouse (or hotkeys)


VolumeTouch gives quick control over your PC’s volume by using a combination of hotkeys and the mouse or arrow keys.

The first thing I will say about this program is that, aside from performing a very useful function, it scores high marks in terms of the user experience it provides. Once you start experimenting with the combination of hotkey/mouse controls for volume you will find that these are very intuitive and well conceived.

The program also uses a system tray icon to display volume levels as a bar gauge or a percentage numeric, which also turned out to be a much more useful that I would have initially thought. More notes on this program:


  • How it works: you can either control the volume with the mouse scroll wheel, through your mouse’s vertical or horizontal movements (but you’ll have to pick one method). Once you specify which method you like in the settings, you can press the default hotkey (CTRL+Shift) and move the scroll wheel up and down (or the mouse up and down, or left and right) in order to control the volume. If you prefer you can use the UP/DOWN arrow keys instead, and CTRL+Shift+0 will mute/unmute.
  • Skins: the VolumeTouch icon in the system tray functions as a volume gauge that displays the volume level. Five “skins” are included, including my favorite “percent” which displays the volume as a percentage (See screenshot). You might want to remove the Windows native volume icon from the system tray (right click on it, click adjust audio properties, then uncheck “place volume icon in the taskbar”).
  • Memory consumption: a rather large 12-15 megs. However, this is probably inflated because this program requires Microsoft .NET framework and, in my experience, real memory consumption for .NET framework apps is difficult to determine for sure.

VolumeTouch vs. Volumouse: I’d previously reviewed Volumouse, a very similar program that performs the same function. Below is a quick comparison of both programs.

  • Reasons to use VolumeTouch: it provides both mouse and arrow key volume control, and allows you to change the volume without needing a mouse wheel (perfect for a laptop, which is my primary computer). VolumeTouch also scores higher on both the simplicity and coolness scales, in my opinion, and the interactive volume gauge in the system tray is a neat feature.
  • Reasons to use Volumouse: offers up to five different user-defined hotkey-activated functions. Highly customizable: can control different channels and specific volume components rather than the general volume. Takes up only 3 megs of memory, and does not require .NET framework.

The verdict: overall this is a great program and very intuitive to use. If you are sensitive to .NET and/or memory consumption you might want to try Volumouse instead; however when it comes to simplicity of design and providing a good user experience VolumeTouch definitely delivers.

Version Tested: 1.1

Compatibility: Windows 2000, XP; no info on Vista. Requires Microsoft .NET Framework 2.0

The program page no longer exists, but you can download ver. 1.1 of the program here.

  • Jason

    btw, Volumouse can be configured to use only hotkeys to control volume, such as when you’re using a laptop. i use Ctrl+Up, Ctrl+Down. granted it’s a little more buried in the options, but can be done relatively easily.

  • Midas

    As I don’t do DotNet unless I absolutely have too, I use Pistaschio ( http://www.freewaregenius.com/pitaschio/ ) for this effect, among other purposes, and unlike what Samer states in his review, it works rather well — you just find a free area of you desktop, or minimize all windows with Winkey+M, move the mouse wheel and see a volume bar swiftly going up or down. And it has a mere 2MB memory footprint

  • Does not work with vista. I use ac’tivAid 1.3 instead. It provider many small auto hotkey scripts bundled into one nice GUI. Of them will provide hotkeys for volume control which does also work in visat.

    It even shows the fancy OS X style OSD whenever the volume has been changed via other sources. Let’s say you have a multimedia keyboard but did not install the keyboard drivers giving you the volume bar display whenever you change the volume. Together with ac’tivAid it will. Works even great with my Dell where i decided to get rid of the craplets by Dell (which were just not working relieable) – change the volume via the dedicated notebook keys – here goes your OSD.

    One can argue if the other extensions to ac’tivAid are useful or not. Personally I love the WndHop like MultiMonitor extension which also works on vista (unlike WndHop)

    Check it out, you might be digging it
    * http://www.heise.de/ct/activaid/default_en.shtml

  • bodinga

    please how can i use it on windows vista.please give me on guides.

  • Downloaded the software. It’s working great as well.
    But, i have a question. How can i make it start during the startup? I want VolumeTouch to start when my computer starts. How do i do it?

  • CT

    @Hasit –
    Go to the VolumeTouch directory, ‘Right-Click’ the VolumeTouch.exe File, ‘Create Shortcut’, move or copy the shortcut to your ‘Startup’ directory –
    C:\Documents and Settings\All Users\Start Menu\Programs\Startup\[shortcut to VolumeTouch] – you should be ‘Good-to-Go’!

  • @CT
    Thank you for your help.
    There is where the problem is. I have tried this for some 100 times (of course an exaggeration) but it doesn’t happen. Whenever I copy the icon in the startup folder, it just vanishes, disappears into thin windows explorer. HELP!!

  • Malih

    I never used this, I think Volumouse very much covers everything you need about manipulating sound volume with shortcut.
    Oh, and the latest version works with Vista too.

  • where can I download this application? It looks really useful!

  • Anonymous

    “There is where the problem is. I have tried this for some 100 times (of course an exaggeration) but it doesn’t happen. Whenever I copy the icon in the startup folder, it just vanishes, disappears into thin windows explorer. HELP!!”

    You might have a program (like Ad-Aware) that automatically protects the startup sequence!?