How to Silence a Clipboard App's Sound Effects

A clipboard app that plays a sound on every copy is a shared-office hazard. The first beep is informative; the twentieth is annoying; the hundredth, in an open-plan office or on a video call, is the moment a colleague asks you to mute your machine. Sounds and haptics on a clipboard app should be off by default, and the app should respect Windows Focus Assist so that any sounds that are enabled are suppressed during meetings and quiet hours. This guide covers why clipboard sounds are a problem, how to disable them, and what a well-behaved app does with Focus Assist.

For neighbouring topics, see vertical monitor in portrait: hot zones change and reduce motion settings and spring UIs.

Why clipboard sounds are different

Sounds on user actions are common in many apps — a "ding" on a successful save, a "whoosh" on a sent email, a "pop" on a notification. These sounds are typically tied to infrequent actions (a save happens once every few minutes; an email is sent a few times per hour) and they serve as confirmation that the action completed.

Clipboard copies are different. A knowledge worker may copy 50–100 times per hour during active work — copying URLs, file paths, code snippets, text excerpts, and image regions. A sound on every copy is constant noise, not confirmation. The same "ding" that was helpful at one copy becomes a metronome of distraction at 60 copies per hour.

The problem is worse in three specific contexts:

• Open-plan offices — neighbours hear every copy.
• Video calls — the microphone picks up the system sound, even with noise suppression.
• Libraries and quiet public spaces — the sound carries.

The right default is no sound. The right secondary behaviour is to respect Focus Assist so that even a user who has enabled a sound for some reason (perhaps a screen-recording workflow where the sound serves as a marker) gets the sound suppressed during meetings.

How to disable clipboard app sounds

Most clipboard apps that play sounds expose a setting to disable them. The setting is usually under a "Sounds" or "Notifications" or "Behaviour" section of the app's settings.

The Windows clipboard history (Win+V) does not play sounds on copy. It plays a brief sound only when an item is pinned or deleted, and that sound is part of the Windows system sound scheme, not a per-app sound. Disabling the Windows default sound scheme silences these.

For third-party clipboard apps, the steps vary:

• Ditto — Options → Sounds → uncheck "Play sound on copy."
• CopyQ — Configuration → Notifications → uncheck sound options.
• ArsClip — Configure → Sounds → set to None.

If the app does not expose a sound setting, the fallback is to mute the app's process via the Windows Volume Mixer. Right-click the speaker icon in the system tray, open Volume Mixer, and mute the app's process. This works for apps that play sounds through the system audio API; it does not work for apps that play sounds through a custom audio path.

Haptics

Haptics — the vibration or tactile feedback on a copy event — are a separate concern. Haptics are only relevant on devices with a haptic actuator, which on Windows means primarily touchscreen laptops and some trackpads. Haptics are not audible, so they do not have the shared-office problem that sounds do.

Haptics should still be off by default, for two reasons:

• Battery life on laptops — haptic actuators draw current, and frequent haptic events during heavy clipboard use add up.
• User surprise — a haptic event the user did not expect is jarring, especially on a trackpad that the user is actively using for cursor control.

The right pattern is to expose haptics as an opt-in setting, off by default, with a brief explanation of when it might be useful (accessibility workflows, noisy environments where sounds are not enough).

Focus Assist

Windows Focus Assist (formerly Quiet Hours) is the OS-level feature that suppresses notifications during specified times or activities. Focus Assist has three modes: Off (all notifications shown), Priority only (only notifications from apps on the priority list are shown), and Alarms only (only alarms are shown).

A well-behaved clipboard app respects Focus Assist by suppressing its sounds and haptics when Focus Assist is active. The app does not need to query Focus Assist directly; it can register its sounds as notifications through the Windows notification API, and the OS will suppress them automatically based on the Focus Assist mode.

If the app plays sounds through a custom audio path rather than through the notification API, the app must query Focus Assist itself via the SHQueryUserNotificationState API and suppress sounds when the state is QUNS_BUSY or QUNS_RUNNING Presentation_MODE. This is the same API an overlay uses to detect fullscreen mode; see click-through edges that do not steal focus for the related discussion.

What can go wrong

• The app plays a sound on every copy and does not expose a setting to disable it. Symptom: the user cannot silence the app without muting the entire system or the app's process. Fix: use the Volume Mixer fallback, or replace the app.
• The app respects Focus Assist but only for the "Priority only" mode, not for "Alarms only." Symptom: the app is silent during "Priority only" but not during "Alarms only." Fix: the app should suppress in both modes, since "Alarms only" is the more restrictive mode.
• The app's haptic feedback fires during a video call's microphone pickup. Symptom: the haptic actuator's noise is picked up by the laptop microphone. Fix: disable haptics, or use an external microphone that does not pick up the laptop chassis.
• The app's sound is played through a custom audio path that ignores system mute. Symptom: muting the system does not silence the app. Fix: use the Volume Mixer to mute the app's process specifically, or replace the app.

Shared-office etiquette

Beyond the technical configuration, there is a social expectation. In a shared office, the default for any app should be no sound. A user who wants sound for a specific reason (accessibility, screen recording) should use headphones, and the sound should not be audible to neighbours. A clipboard app that does not respect this default is a social liability, regardless of how good its other features are.

The same applies to video calls. The host's machine should be silent during the call; any system sounds are picked up by the microphone and broadcast to all participants. Focus Assist should be enabled during calls — Windows 11 has a "When I'm playing a game" or "When I'm in a meeting" automatic rule that handles this, but it requires the calendar to be configured correctly.

Accessibility and screen-reader users

A small minority of users genuinely benefit from sound on copy — primarily screen-reader users who already navigate by audio cue. For these workflows, a brief, distinct sound confirms that a copy landed, in the same way the screen reader confirms a focus change. The trade is the same: useful at low copy rates, noisy at high rates. The recommended pattern is to allow the sound but tie it to the screen-reader session, not to the app — so that when the screen reader is off, the sound is off too.

For the specific Edge-Drop case, see how to turn sound effects off in Edge-Drop. The shelf ships silent by default; enabling a sound for accessibility is a deliberate choice and should be paired with Focus Assist so that the sound does not bleed into meetings.

Honest positioning

Edge-Drop, the Windows hover-activated clipboard shelf, does not play sounds on copy by default and does not currently ship a haptic feedback feature. The shelf's open animation has no associated sound. The shelf respects Focus Assist through the SHQueryUserNotificationState API, which it uses for fullscreen detection; the same query suppresses any future sound or haptic feedback the shelf might add. The shelf's recommendation is that clipboard apps should be silent by default, and that any sound or haptic feature should be opt-in and suppressed during Focus Assist. This is the pattern the shelf follows and the pattern it recommends to other tool authors.

What to check

If your clipboard app is making noise in a shared space, work through these:

1. Does the app expose a "Sounds" or "Notifications" setting? (Check the app's settings.)
2. If yes, disable sounds on copy.
3. If no, open Volume Mixer (right-click the speaker icon) and mute the app's process.
4. Enable Focus Assist during meetings. (Settings → System → Focus Assist, or use the "When I'm in a meeting" automatic rule.)
5. Test by copying something during a Focus Assist session; the app should be silent.

For apps that do not respect Focus Assist, the workaround is to quit the app during meetings. The fix is to use an app that does respect Focus Assist, which is the standard for any well-behaved Windows utility in 2026.

Related reading

• Reduce Motion Settings and Spring UIs
• Always-On-Top Apps That Fight Each Other
• Clipboard Tools on Multi-Monitor Windows Setups
• Win+V Not Working on Windows 11: 9 Fixes

Sources

• Microsoft Support — Focus Assist in Windows — official user-facing guide to Focus Assist, including automatic rules for meetings and games
• Microsoft Learn — SHQueryUserNotificationState — Win32 reference for the API applications use to query Focus Assist state
• Microsoft Learn — Windows notification API — Win32 reference for the message beep API, which is automatically suppressed by Focus Assist
• Microsoft Support — Change system sounds — official steps for changing or disabling the Windows system sound scheme
• Microsoft Learn — Volume Mixer API — Win32 reference for the API that backs the Volume Mixer, including per-process muting

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support