How to Launch Edge-Drop at Login

A clipboard shelf that does not start with Windows is a clipboard shelf that is not there for the first copy of the day. Edge-Drop's launch-at-login behaviour is on by default in packaged builds, but the mechanism — a Windows registry Run key — has a few quirks worth knowing. This guide covers how the launch-at-login entry is written, how to toggle it in Edge-Drop and in Windows, why source builds behave differently from packaged builds, and how to verify the entry is working. For the on-disk layout see where Edge-Drop stores data on disk; for the install workflow see how to install Edge-Drop on Windows 10 and 11.

The mechanism: a registry Run key

Windows has supported per-user launch-at-login entries via the registry since at least Windows 2000. The canonical location is:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

An entry under this key consists of a name (e.g., Edge-Drop) and a value pointing to the executable (e.g., "C:\Users\<user>\AppData\Local\Programs\Edge-Drop\Edge-Drop.exe"). When the user logs in, Windows reads this key and launches every executable listed.

Microsoft documents this mechanism on Microsoft Learn under the Run and RunOnce registry keys reference. It is the standard, supported way for desktop apps to launch at login. It is also visible in Task Manager's Startup tab, which is the user-facing view of the same data.

Edge-Drop uses this mechanism for packaged builds. When the user enables launch-at-login in Edge-Drop's Behaviour tab, Edge-Drop writes (or updates) the Run key entry. When the user disables it, Edge-Drop deletes the entry.

How to toggle it in Edge-Drop

The toggle is in the Behaviour tab of the settings panel:

1. Open Edge-Drop settings (tray icon → Settings, or Alt+C then the gear icon).
2. Go to the Behaviour tab.
3. Find the "Launch at login" toggle.
4. Turn it on or off.

The change takes effect immediately for the registry key. No restart is required. The next time the user logs into Windows, Edge-Drop will (or will not) start automatically.

The default state is on for packaged builds. New installs typically launch at login from the first login after install. Users who do not want a clipboard shelf running all the time should turn this off.

How to toggle it in Windows

Alternatively, the launch-at-login entry can be toggled in Windows itself, without going through Edge-Drop's settings:

1. Open Task Manager (Ctrl+Shift+Esc).
2. Go to the Startup apps tab (Windows 11) or Startup tab (Windows 10).
3. Find Edge-Drop in the list.
4. Right-click → Enable or Disable.

Disabling via Task Manager does not delete the registry entry; it sets a "disabled" flag in a separate registry location that Windows checks at login. The practical effect is the same: Edge-Drop does not launch.

Re-enabling via Task Manager clears the disabled flag. The original Run key entry takes effect again.

If Edge-Drop's in-app toggle is out of sync with Task Manager's state (e.g., in-app says on, Task Manager says disabled), the Task Manager state wins. This is rare but can happen if the user toggles Task Manager while Edge-Drop is running.

Why source builds behave differently

When Edge-Drop is built from source — see how to build from source for the curious — the resulting binary does not have an installer. Without an installer, there is no automatic Run key write. The user has to:

• Manually create the Run key entry, pointing to the dev-built binary.
• Or use Task Manager's "Open file location" trick: create a shortcut to the binary in shell:startup (which is %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup).

Either approach works. The shortcut approach is simpler because it does not require editing the registry.

Source builds also do not auto-update, so even with launch-at-login enabled, the user is responsible for pulling new commits and rebuilding. For the differences between source and packaged builds, see how Edge-Drop updates on GitHub builds.

How to verify the entry is working

A 60-second test:

1. Ensure launch-at-login is enabled in Edge-Drop's Behaviour tab.
2. Open Task Manager → Startup apps.
3. Find Edge-Drop. The status column should read "Enabled."
4. Quit Edge-Drop (tray icon → Quit).
5. Sign out of Windows (Win+L → sign out, or Start → Power → Sign out).
6. Sign back in.
7. Edge-Drop should start automatically. The tray icon should appear within a few seconds.

If Edge-Drop does not start:

• Confirm the toggle is on in Behaviour.
• Confirm the entry is enabled in Task Manager → Startup apps.
• Check that the executable path in the Run key is correct. Open regedit, navigate to HKCU\Software\Microsoft\Windows\CurrentVersion\Run, find the Edge-Drop entry, and verify the path matches the actual binary location.
• If Edge-Drop was moved (e.g., the install directory was renamed), the Run key path may be stale. Reinstall or update the path manually.

Why launch-at-login matters

A clipboard shelf that is not running captures nothing. The first copy of the day — the URL you grab from email before your coffee, the password from your password manager, the file path from a teammate's chat — happens before you remember to start Edge-Drop. With launch-at-login on, the shelf is there from the first login.

There is a cost: Edge-Drop uses ~130-160 MB of RAM when idle (typical Electron footprint), plus the periodic clipboard poll. For most users this is fine; for users on low-RAM machines, see best clipboard manager for low-RAM PCs for lighter alternatives.

When to disable launch-at-login

A few patterns argue for disabling:

• Low-RAM machine — the ~130-160 MB is a real cost on a 4 GB machine. Disable launch-at-login and start Edge-Drop manually when needed. Or switch to a lighter tool like Ditto.
• Server or kiosk — a machine that should not have a clipboard shelf running by default. Disable launch-at-login and do not start Edge-Drop.
• Shared workstation with multiple users — each Windows user gets their own Run key entry. If only one user wants Edge-Drop, that user enables it; others disable it in their own accounts.
• Trial period — users evaluating Edge-Drop may want to start it manually for a week before committing to launch-at-login. See how to trial a clipboard app for seven days.
• Battery-sensitive laptop — the idle cost is small but non-zero. For users on a tight battery budget, see laptop battery and always-on clipboard polling.

What Edge-Drop does not claim

• Launch-at-login is per-user. Each Windows user account has its own Run key entry. There is no machine-wide "all users" launch.
• Launch-at-login does not start Edge-Drop before login. The shelf is not available on the lock screen.
• Launch-at-login does not bypass UAC. If Edge-Drop was installed for All Users and the Run key is in HKLM rather than HKCU, UAC may prompt at login.
• Launch-at-login does not survive a Windows reset. Reinstalling Edge-Drop after a Windows reset re-creates the Run key.
• Launch-at-login does not start Edge-Drop on Windows Safe Mode. Safe Mode loads only minimal drivers and services.

For the broader topic of startup-cost considerations, see startup cost: login-item clipboard apps.

Slow-logon machines

On machines where the user profile is roaming or where logon scripts run synchronously, an extra startup entry adds measurable seconds to the logon time. Edge-Drop's footprint is small at launch — the Electron main process boots in roughly a second on a modern SSD — but on a remote-profile machine over a slow WAN link, that second can become three or four as the profile syncs the new Run-key entry and the local Electron cache is initialised.

The diagnostic is to disable Edge-Drop's launch-at-login, log out and back in, and time the logon. If logon drops by a meaningful amount, Edge-Drop was contributing to the slow logon. The fix is to keep launch-at-login off and start Edge-Drop manually after the desktop has settled, which is the same workaround recommended for low-RAM laptops.

How to remove the entry completely

If you want to remove the launch-at-login entry completely — not just disable it, but delete it — use regedit:

1. Press Win+R, type regedit, press Enter. Accept the UAC prompt.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run.
3. Find the Edge-Drop entry on the right side.
4. Right-click → Delete.

The entry is gone immediately. To re-create it, toggle the Behaviour setting off and on again in Edge-Drop.

For the full clean-uninstall workflow including this step, see how to uninstall Edge-Drop cleanly.

Summary

Packaged Edge-Drop builds write a per-user Run key entry under HKCU\Software\Microsoft\Windows\CurrentVersion\Run to launch at login. The toggle is in the Behaviour tab; the same entry is visible in Task Manager's Startup apps tab. Source builds do not write the entry automatically and need a manual shortcut in shell:startup or a manual Run key. The default is on for packaged builds; users on low-RAM machines, shared workstations, or battery-sensitive laptops may want to disable it. The entry can be deleted via regedit for a complete removal.

Related reading

• How to Use the Preview Flyout
• How to Open Links From Edge-Drop in Your Browser
• How to Install Edge-Drop on Windows 10 and 11
• What Local-First Software Means for Clipboard Apps

Sources

• Microsoft Learn — Run and RunOnce registry keys — official documentation for the launch-at-login mechanism Edge-Drop uses
• Microsoft Support — Startup apps in Task Manager — the user-facing view of the same Run key data
• Microsoft Learn — HKCU registry hive — documents the per-user registry hive that holds the Run key
• Electron — app.setLoginItemSettings API — the Electron API Edge-Drop uses to write and remove the Run key entry
• Microsoft Learn — shell:startup known folder — the alternative shortcut-based launch-at-login path used by source builds

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